How to write a Staff Engineer promotion case that survives calibration
Updated · YouDeserveNow editorial
The jump from Senior to Staff is where most engineering promotion cases stall. Senior is judged on what you deliver; Staff is judged on what changes because you were there, beyond your own team. A packet full of shipped projects reads as a very good Senior. A Staff case has to show direction you set, problems you chose, and engineers who are more effective because of you.
What the committee is looking for
Scope beyond one team
Evidence that your technical decisions shaped work across multiple teams or a whole system, not only the projects you personally built.
Ambiguity turned into direction
A problem that was poorly defined until you framed it, wrote the proposal, and got people to agree on the path.
Multiplying others
Engineers you mentored, standards you set, reviews or docs that raised the bar for people who never reported to you.
Business-relevant outcomes
Reliability, cost, velocity, or revenue impact with a number someone else can confirm, not just 'improved performance'.
Sustained, not one-off
A pattern across two or more halves, because committees discount a single heroic project.
The holes that sink most cases
- 01
Project lists instead of outcomes
"Built X, shipped Y" proves execution, which is the Senior bar. Each line needs the result and why it mattered.
- 02
"We" with no "I"
Committees cannot credit you for team results unless your specific decision or contribution is explicit.
- 03
Influence without witnesses
Cross-team impact that no one outside your team can vouch for. Name the teams and the people who relied on it.
- 04
No mapping to the ladder
Evidence is strong but never tied to the Staff expectations in your company's rubric, so reviewers must do the mapping themselves (and often do not).
Before and after
Highlighted brackets are the facts you need to supply. Never fill them with numbers you cannot back up.
Before
Worked on the migration to the new event pipeline.
After
Proposed and led the migration of [number] services to the new event pipeline across [teams], cutting p99 ingestion latency from [before] to [after] and unblocking [team]'s launch.
Before
Mentored junior engineers.
After
Mentored [number] engineers through their first on-call and design reviews; [name/role] now independently owns [system], freeing [time] of senior review capacity per sprint.
Before
Improved our CI.
After
Identified CI flakiness as the top drag on [org] velocity, set the reliability target, and drove fixes that cut median build time by [X%] for [number] engineers.
A structure that works
- One-paragraph summary: the level you are asking for and the 2-3 themes that prove it
- Theme 1: technical direction across teams (proposal, decision, outcome, who relied on it)
- Theme 2: a hard, ambiguous problem you framed and resolved
- Theme 3: how you multiplied other engineers
- Evidence appendix: design docs, metrics dashboards, peer quotes
- Explicit mapping to your company's Staff expectations
Frequently asked
How many projects should a Staff promotion packet include?
Usually 2-4 substantial examples grouped into themes beat a long list. Committees remember the strongest example and discount padding.
Do I need to be leading a team to get to Staff?
No. Staff is typically an individual-contributor level. You need evidence of technical leadership and influence across teams, not people management.
What if my biggest impact was preventing problems?
Prevention counts when you can make it concrete: the risk you identified, what it would have cost, the change you drove, and the incidents or delays that did not happen.