Growing your career
How promotion works
Evidence, packets, calibration and the manager conversations that turn next-level work into a title.
Promotion is not a prize for loyalty or a receipt for hours worked. At companies with a real ladder, it is recognition that you have already been operating at the next level for a sustained period — usually multiple quarters, not a heroic month. The packet, the calibration meeting, and your manager's advocacy are the machinery that turns that reality into a title.
If the machinery feels opaque, that is normal. The underlying game is still legible once you know what committees read and what they distrust. People who ask for the title first, then scramble for stories, get read as miscalibrated. People who operate, write the evidence down, and partner with their manager on gaps get a fair shot — or a named reason to move.
Treat promo season as editing, not creating. Five minutes a week on a brag document beats a weekend of archaeology. Every strong piece of work should answer: which next-level criterion does this prove?
A packet that works is a mapping, not a memoir. Quote the next-level ladder line, claim you already do it, and attach two or three linked stories with numbers — p99 420 ms → 80 ms, flake rate 12% → 2% — plus a peer who can speak to the rollout. Cut anything that only proves your current level. If your manager and one senior peer independently say the evidence is there, submit. If only you think so, gather another quarter of artifacts rather than burning a thin case.
When someone asks "tell me about a time you grew," narrate scope change and evidence, not "I got promoted." Committees and interviewers both buy outcomes.
Concepts in this section
Read them in order.
| Step | Concept | What it answers |
|---|---|---|
| 1 | Promotion is lagging recognition | Why the title follows the work, not the other way around? |
| 2 | Building a promo packet | What do committees read, and how do you map evidence? |
| 3 | Working with your manager on promo | How do you get advocacy, scope, and a plan after "not yet"? |
| 4 | Promo blockers and when to move | What keeps strong engineers stuck, and when is leaving rational? |
Common mistakes
- Inverting the order. Asking first, evidencing later.
- Activity without outcome. Ticket counts and "key contributor" language.
- Going up with a thin case because you are impatient — or waiting forever after the evidence is there.
- Accepting a title without new scope.
Key takeaways
- Promotion recognizes sustained next-level operation. It is lagging, not leading.
- Calibration compares evidence across people. Artifacts and metrics beat vibes.
- Map examples to ladder criteria. Partner with your manager on gaps and scope.
- Sometimes the move is a new team or company. Leave with relationships intact.
Further learning
Edmond Lau's Talks at Google talk on leverage is useful context for what to put in a case — impact per time, not activity.
Related
What the levels mean
Junior, SDE2, SDE3 and staff: scope, autonomy, impact and influence at each level.
One-on-ones, feedback and performance reviews
Run your 1:1s, ask for and act on feedback, and keep a brag document through review cycles.
Growing your scope
From tasks to features to projects to problems: finding and taking on higher-leverage work.