Resume structure, achievement bullet formulas, ATS optimization, and job-targeted tailoring for software engineers. Use when reviewing resumes, crafting achievement bullets, extracting keywords from job descriptions, or tailoring content for specific roles.
View on GitHubmelodic-software/claude-code-plugins
soft-skills
January 21, 2026
Select agents to install to:
npx add-skill https://github.com/melodic-software/claude-code-plugins/blob/main/plugins/soft-skills/skills/resume-optimization/SKILL.md -a claude-code --skill resume-optimizationInstallation paths:
.claude/skills/resume-optimization/# Resume Optimization Comprehensive guidance for creating effective software engineering resumes that pass ATS systems and resonate with hiring managers. ## When to Use This Skill - Reviewing or improving a software engineer's resume - Crafting impactful achievement bullets from work experience - Optimizing resume content for ATS keyword matching - Tailoring a resume for a specific job description - Understanding modern resume structure and formatting ## Core Principles ### The Resume's Purpose A resume is a **marketing document**, not a job history. Its purpose is to: 1. Pass ATS screening (keyword matching) 2. Capture a recruiter's attention (6-second scan) 3. Demonstrate value through quantified achievements 4. Secure an interview opportunity ### What Makes Engineering Resumes Different Software engineering resumes should emphasize: - **Technical impact**: Specific technologies, scale, and performance improvements - **Business outcomes**: Revenue, cost savings, user growth, time savings - **Leadership signals**: Mentoring, cross-team collaboration, technical decisions - **Quantification**: Numbers that demonstrate scope and impact ## Resume Structure Quick Reference ### Recommended Section Order 1. **Contact Information** - Name, email, phone, LinkedIn, GitHub (optional) 2. **Professional Summary** (optional) - 2-3 sentences for senior roles 3. **Skills** - Technical skills organized by category 4. **Experience** - Reverse chronological, 3-5 most relevant roles 5. **Projects** (optional) - For junior engineers or career changers 6. **Education** - Degrees, certifications, relevant coursework ### Length Guidelines | Experience Level | Recommended Length | | ---------------- | ------------------ | | 0-5 years | 1 page | | 5-10 years | 1-2 pages | | 10+ years | 2 pages max | ### Formatting Essentials - **Font**: Clean, readable (Calibri, Arial, Garamond - 10-12pt) - **Margins**: 0.5-1 inch - **Format**: PDF (preserves formatting) - **File naming**: