magicbowen/resume

Resume

Introduction

Use this template for experienced technical professionals, especially senior or staff-level candidates.

Background:

• The template is optimized for outcome-driven resumes where impact, scale, and leadership matter more than dense skill inventories.
• It is intended for readers such as hiring managers, recruiters, and interview panels who scan quickly.

Precautions:

• Do not fabricate metrics, job scope, or technical claims.
• Keep the document ATS-friendly and easy to scan.
• Refer to templates/experienced_technical_resume.md for the structure and examples/senior_backend_resume_excerpt.md for a compact example.

Writing Steps (Process)

1. Choose target role, seniority, and domain.
2. Inventory the last 2-4 roles and the strongest initiatives in each.
3. Convert initiatives into impact bullets using Action + What + How + Result.
4. Draft a headline and summary aligned to the target role.
5. Build a grouped skills section with only defensible skills.
6. Add projects only when they strengthen the case more than additional experience bullets.
7. Tighten language, remove weak bullets, and optimize for page-one scanning.

Writing Requirements

• Length: 2-3 pages by default; 3 pages is acceptable for 8+ years of experience.
• Order: Header -> Summary -> Skills -> Experience -> Optional Projects -> Education -> Optional Certifications.
• Bullets: 3-6 per role, led by the strongest outcomes.
• Metrics: quantify impact whenever possible.
• Style: concise, scannable, no first-person pronouns, no long paragraphs.

Skills Guidance

• Group skills by category and prioritize depth over breadth.
• Match the job description truthfully rather than stuffing keywords.
• List only technologies and practices the candidate can discuss in detail.

Senior-Level Best Practices

• Make scope visible: traffic, users, systems, data volume, team size, or organizational impact.
• Show ownership with verbs such as "Owned", "Led", "Designed", or "Established".
• Prefer outcomes over responsibility lists.
• Keep tense, dates, and formatting consistent throughout.

Companion Files

• templates/experienced_technical_resume.md: reference structure for the finished resume.
• examples/senior_backend_resume_excerpt.md: example of concise, impact-oriented resume content.