Staff engineer promotion
Earned by impact beyond your own team — judgment, technical direction, and lifting other engineers — not by writing more code. Reaching staff is a job change, not a title bump.
A staff engineer promotion is earned by demonstrating impact beyond your own team — judgment, technical direction, and lifting other engineers — not by writing more code. As Will Larson puts it, reaching staff is a job change, not just a title bump.
What "staff" evidence looks like
- Initiatives multiple teams adopt — a framework, a shared service
- Judgment: risks you caught early, directions you changed, the wrong solutions you said no to
- Sponsorship: making senior engineers better, not just shipping the most
- Glue work that keeps cross-team efforts moving, and its impact
- More of your senior-level output, just more of it
- Lines of code, PR counts, ticket tallies
- Solo heroics with no organizational leverage
- Complexity for its own sake, with no outcome
How to prioritize the case
- Scope beyond your team first — the defining staff signal.
- Judgment and technical direction second.
- Sponsorship and leverage third.
- Glue work and its impact, named because no one else logs it.
Build it over time
Larson's advice is concrete: keep an evolving promo packet, review it with your manager across cycles, and let it steer you toward the criteria over quarters and years. Staff cases are built up over time — and so the evidence has to be, too. The complexity that earns staff (legacy systems with no docs, multi-stakeholder efforts) is exactly the kind you'll forget the specifics of if you don't capture them.
How Workfied helps here
Workfied keeps a running record of your cross-team impact and your judgment calls, so your staff case builds itself across quarters instead of being reconstructed under deadline. It never reads from company systems — only what you send it. Encrypted in transit and at rest.
Evidence
The mechanism
Staff is impact beyond your team — direction and leverage — not more code. It's a different role, not a bigger one.
Source: Larson, Staff Engineer
Include vs cut
Cut output counts. Keep cross-team initiatives, judgment calls, and the engineers you made better.
Workfied house view
What committees want
Consistent high-impact work wider than one team, plus the technical complexity you navigated.
Engineering promotion practice