05 — Career Accelerator
Goal: condense 01–04 into a fast-track progression framework — a closed loop that converts daily engineering into a promotion case.
The core principle: Promotions are not awarded for potential; they are awarded for demonstrated impact at the next level, sustained for 6+ months, and made legible to decision-makers. This chapter turns that definition into a machine you run quarterly.
Part 1 — The compounding loop (01 × 02 × 03 × 04)
Each chapter feeds the next; skip one and the machine leaks:
04 Reliability ──→ makes your delivery trusted (the foundation)
↓
03 Execution ──→ turns trust into consistent, on-time delivery
↓
02 Architecture ──→ raises the ceiling: system-level leverage
↓
01 Visibility ──→ makes the leverage legible to the org
↓
05 Accelerator ──→ frames it as a promotion case, then re-loops
The one equation to internalize:
Impact = (Value shipped) × (Reliability) × (Leverage of what you chose to build) × (Number of people who know it was you)
You can be excellent at the first three and invisible on the fourth — the equation returns zero. This is why 01 is not optional "self-promotion"; it is the multiplier on the product of your work.
Part 2 — The operating rhythm (weekly, monthly, quarterly)
Weekly (already in 00 — the loop)
- Mon 30 min: plan the week (03) — features → ≤4h tasks with DoDs
- Daily: execute with the pre-PR + pre-merge gates (04)
- Fri 60 min: artifact (01) + impact-ledger line + gap note (03 §2.3)
- Fri 30 min: career arc check (below)
Monthly — the calibration
- Review the impact ledger: does this month show value, reliability, architecture, or influence? If it shows "busy," re-scope next month toward leverage.
- One skip-level or cross-team connection per month (a backend lead, a PM, a staff engineer) — a professional network of 5 senior relationships inside the org is worth more than 500 LinkedIn connections.
- 30-min deliberate study on the month's slowest area (03 §2.3) — gaps closed on purpose compound.
Quarterly — the 90-day arc (the promotion engine)
Pick ONE high-leverage, visible initiative per quarter (see Part 3), then:
- Define the outcome as a number (e.g., "INP p75 from 400ms → 200ms," "design-system adoption 20% → 80%," "QA rework on my features < 5%").
- Write the artifact trail as you go — ADR, metrics note, demo. Never "write it up later"; the artifacts ARE the work (01).
- Review mid-quarter: is the number moving? Is the visibility happening? Correct course at week 6, not week 12.
- At quarter end: one-page outcome summary with before/after numbers → send to your manager as the input for the promotion case.
Part 3 — Choosing the quarter initiative (the leverage filter)
Score candidate initiatives:
| Filter | Question |
|---|---|
| Business value | Does it move a metric leadership cares about? |
| Visibility | Will the result be seen by decision-makers? |
| Leverage | Does it make 3+ engineers faster/better (not just you)? |
| Fit your level | Does it demonstrate next-level work (system scope, not ticket scope)? |
| Success probability | Can you make it succeed in 90 days with the team you have? |
Rule: pick the initiative scoring highest on Leverage × Visibility with a realistic success path. Classic candidates at Senior→Principal:
- Kill the class of top production errors (reliability, measurable, visible)
- Build/complete the design system or platform layer (leverage × visibility)
- Re-architect the slowest user journey (architecture, measurable via RUM)
- Introduce contract-first API + generated types org-wide (influence + leverage)
The sponsor rule: before starting, tell your manager the goal and the artifact trail — a manager who knows what you're building becomes your sponsor (and later your advocate in calibration). Sponsorship is earned by pre-alignment, not surprise.
Part 4 — Building the promotion case (the document that does the talking)
A promotion case at the end of 2–3 arcs should contain:
- The level gap closed: 3 examples where you operated at Principal scope (system decisions, org-level artifacts, teaching).
- Numbers: before/after on the initiatives + your delivery record (on-time %, QA rework rate, bug count on your features — 04 gives you these).
- Artifact trail: links to ADRs/RFCs/demos/metrics notes (01) — the reviewer can verify without taking your word.
- 360 evidence: named colleagues you've unblocked/taught (your reviews and mentoring are the receipts).
Timing insight: the case is written continuously (one ledger line/week) and assembled in an afternoon — never written from memory at review time. Memory is lossy; the ledger is evidence.
Part 5 — The Principal transition (what to stop doing)
| Stop (Senior reflexes) | Start (Principal reflexes) |
|---|---|
| Taking the hardest ticket to prove yourself | Delegating/coaching the hardest ticket — others' delivery is your output |
| Optimizing your own code | Optimizing the team's architecture and the developer loop |
| Answering "how should we build X?" | Asking "should we build X at all? what's the leverage?" |
| Visibility in your lane | Visibility across lanes (backend, PM, QA, leadership) |
| Winning arguments | Pre-aligning so arguments rarely happen |
| Reviewing code | Reviewing plans, RFCs, and trade-offs before code exists |
| Fixing bugs | Killing bug classes (04's systemic eradicators) |
The identity shift: a Senior is measured by what they deliver; a Principal by what the system delivers because they shaped it. Every week in the loop, ask the one question that keeps you honest: "Did I move the system this week, or just my tickets?"
✅ The 90-day fast-track checklist
- One high-leverage initiative chosen (leverage × visibility filter), outcome as a number
- Sponsor aligned up front (manager knows the goal + artifact trail)
- Weekly loop running: Mon plan · daily gates · Fri artifact + ledger
- Mid-quarter check at week 6 (number moving? visibility happening?)
- Quarter-end one-pager with before/after numbers delivered
- 3 Principal-scope examples banked (system decisions, org artifacts, teaching)
- Promotion case document exists and grows weekly
- Identity check: moving the system, not just the tickets
The whole rulebook in one line: Build the right thing (02), deliver it flawlessly and reliably (03 · 04), make it visible and shape what comes next (01), and run the loop on a quarterly arc (05) — for six months, and the promotion case writes itself.