Track different resume versions, maintain master resume, manage tailored versions

Resume Version Manager When to Use This Skill Use this skill when the user: Has multiple resume versions to manage Needs to track tailored resumes Wants to maintain a master resume Is applying to many different roles Mentions: "resume versions", "master resume", "different versions", "track resumes", "which resume" Core Capabilities Create and maintain master resume document Track tailored resume versions Organize resume versions by role/industry Maintain consistent source of truth Streamline resume updates Prevent version confusion The Version Management Problem Common Pain Points: "Which version did I send to Company X?" "Where's my most recent resume?" "I have 15 resume files and don't know which is best" "I forgot to update my resume after that project" "I keep tailoring from different base versions" The Solution: A systematic approach with: 1. One master resume (source of truth) 2. Organized tailored versions 3. Clear naming conventions 4. Update workflow Master Resume Concept What is a Master Resume? A comprehensive document containing: ALL your experiences (not just recent) ALL bullet points you've ever written Every achievement, project, skill Full details (even if they won't fit on one page) Purpose: Source of truth to pull from when tailoring Master Resume Structure File Organization System Folder Structure File Naming Convention Pattern: [LastName] [Role/Type] [Company] [Date].pdf Examples: Smith ProductManager Google Jan2024.pdf Smith SWE Stripe Feb2024.pdf Smith DataScience General 2024.pdf Smith Master Resume v3.docx Version Categories By Target Role Product Management: Emphasizes: Strategy, roadmap, metrics, stakeholders Skills highlight: Product tools, analytics, user research Software Engineering: Emphasizes: Technical projects, systems, code Skills highlight: Languages, frameworks, tools Data Science: Emphasizes: Analysis, ML, statistical methods Skills highlight: Python, SQL, ML libraries By Industry Tech/Startup: Emphasizes: Innovation, growth, scrappiness Tone: Modern, direct, achievement focused Enterprise/Corporate: Emphasizes: Scale, process, collaboration Tone: Professional, structured, comprehensive Finance: Emphasizes: Analysis, compliance, accuracy Tone: Conservative, precise, credentialed By Seniority Level Individual Contributor: Focus on execution and technical skills Detailed project descriptions Technical accomplishments Manager: Team leadership and development Cross functional collaboration Business impact metrics Executive: Strategic leadership P&L responsibility Organizational transformation Application Tracking Simple Tracker Spreadsheet Information to Track Company name Job title Resume version used Cover letter version used Application date Application method (portal, referral, direct) Current status Follow up dates Notes and contacts Update Workflow When to Update Master Resume Immediately Update For: New job or promotion Completed major project New skills or certifications Significant achievements Awards or recognition Quarterly Review: Add recent accomplishments Update metrics with new data Refresh skills section Remove outdated information Master to Tailored Workflow Common Scenarios Scenario 1: Applying to Similar Roles Strategy: Create one well tailored version for the role type Make minor adjustments for each company Track which slight variation went where Scenario 2: Applying to Different Role Types Strategy: Create separate base versions for each role type Maintain clear folder organization Each version pulls from same master Scenario 3: Rapid Application Volume Strategy: Create 2 3 strong category versions Use "general" versions for quick applications Reserve deep tailoring for top choices Scenario 4: Career Transition Strategy: Create transition focused version Emphasize transferable skills Maintain original industry version as backup Version Control Best Practices DO: ✅ Always work from master as source ✅ Use consistent naming conventions ✅ Track which version went where ✅ Keep master updated ✅ Date your files ✅ Backup to cloud storage DON'T: ❌ Edit master directly for applications ❌ Use vague names like "resume final v2" ❌ Forget which version you sent ❌ Let master get out of date ❌ Have multiple "master" files ❌ Delete old versions (archive instead) Output Format When managing resume versions: Version Management Checklist ✅ Master resume exists and is current ✅ Folder structure is organized ✅ Naming convention is consistent ✅ Application tracker is maintained ✅ Know which version sent to each company ✅ All versions pull from same master ✅ Backup system in place ✅ Old versions archived (not deleted) ✅ Update workflow is established ✅ Regular master resume reviews scheduled

resume-version-manager