Resume Writing

Deep resume workflow—target role, positioning statement, impact bullets with metrics, keyword alignment, ATS hygiene, and proofreading. Use when rewriting tech resumes, transitioning roles, or tailoring for specific companies.

Resume Writing (Deep Workflow)

A strong tech resume proves impact with evidence, not adjectives. Optimize for skimmability (recruiters spend seconds) and interview-defensible depth.

When to Offer This Workflow

Trigger conditions:

• Active job search; career pivot (IC ↔ management, domain change)
• Low response rate; resume too long or generic

Initial offer:

Use six stages: (1) target & positioning, (2) experience structure, (3) impact bullets, (4) skills & keywords, (5) ATS & format, (6) review & tailoring). Confirm regional norms (one page vs two for mid/senior).

---

Stage 1: Target & Positioning

Goal: One-line headline aligned with the next role you want—not every past title.

Exit condition: 2–3 target job descriptions saved as references for keyword alignment (without copying dishonestly).

---

Stage 2: Experience Structure

Goal: Reverse chronological; roughly 3–5 bullets per role; most recent role deepest.

Practices

• Projects section only for early career, OSS, or notable side work

---

Stage 3: Impact Bullets

Goal: Pattern: strong verb + scope + quantified outcome (“Reduced p95 API latency 40% by…”).

Practices

• Metrics: users, revenue, %, incidents avoided, time saved
• Never fabricate numbers—approximate ranges only if ethically OK

---

Stage 4: Skills & Keywords

Goal: Skills section mirrors target JD language for tools you can defend in interview.

---

Stage 5: ATS & Format

Goal: Simple layout; standard headings; avoid critical text only inside images; PDF unless employer specifies otherwise.

---

Stage 6: Review & Tailoring

Goal: Tailor top bullets per application; proofread; peer review for clarity and exaggeration checks.

---

Final Review Checklist

• Headline matches target role
• Bullets emphasize measurable impact
• Skills honest and interview-defensible
• ATS-friendly formatting
• Proofread; consistent tense and date format

Tips for Effective Guidance

• Remove filler (“team player”) unless proven by story elsewhere.
• Staff+ candidates: emphasize scope, multi-team leadership, and business outcomes.
• Link GitHub/portfolio only if maintained and impressive.

Handling Deviations

• Non-traditional path: emphasize projects with outcomes and certifications if relevant.