Short answer
Staff engineer is a scope change, not a seniority increase. You move from owning systems to owning technical direction across teams, and the promotion is usually granted for solving a problem the organisation already recognised as important - which means the work has to be visible before the title exists.
Senior engineer is the last level most companies will promote you to on the strength of your own work. Staff is different: it is granted for influence over decisions you did not personally implement, which is why so many excellent senior engineers stall there. They keep getting better at the thing that stopped being the criterion.
The Visibility Prerequisite
Staff promotions are almost never awarded for potential. They are awarded after someone has already been doing the job informally - usually for six to twelve months - and the title catches up to reality. This means the standard advice to "ask what you need to do" is less useful here than finding a real organisational problem and quietly starting to own it.
The four staff archetypes
Will Larson's framing in Staff Engineer has become the common vocabulary, and it is useful because different companies reward different archetypes:
- The Tech Lead guides the direction of one team, usually the largest and most ambiguous work. Closest to what most people picture.
- The Architect owns the direction of a critical area across teams - the data model, the platform, the API surface.
- The Solver gets dropped onto whatever is currently on fire and is trusted to go deep on hard, poorly-understood problems.
- The Right Hand operates with the scope of a senior leader without the reporting line, often as an extension of an engineering director.
Knowing which archetype your organisation actually promotes matters more than being excellent at a different one. Look at the last two people promoted to staff and work out which pattern they matched.
What the work actually looks like
- Writing that changes decisions. RFCs and design docs are the primary staff artefact. If your writing is not changing what other teams do, you are producing documentation rather than direction.
- Being the person consulted before the work starts. Not the reviewer who catches problems late, but the person teams check with while the plan is still cheap to change.
- Owning the boring cross-cutting problems. Build times, migration paths, the deprecation nobody wants. These are high-leverage precisely because nobody volunteers.
- Saying no with a reason. A large part of the job is talking the organisation out of expensive mistakes, which requires being trusted rather than being right.
How to get the scope before you have the title
You cannot be promoted for cross-team influence if you have never had any, and nobody will hand you cross-team scope. The reliable route is to find a problem that is genuinely hurting more than one team, is unowned, and is something you can make progress on without permission - then write the document that names it.
The opening move
Write a two-page document describing the problem, its cost in concrete terms, and three options with a recommendation. Circulate it to the people it affects. Most staff careers start with a document that made a vague shared frustration specific enough to act on.
Staff versus engineering manager
At most companies these are the same level with the same pay band and different work. Staff engineers own technical direction and influence without authority; managers own people, headcount and delivery. The honest test is which set of problems you want to spend your time on - neither is more senior, and moving between them later is normal.
Frequently asked questions
What does a staff engineer actually do?
They own technical direction beyond a single team - writing the RFCs that change what other teams build, being consulted before projects start, and taking on cross-cutting problems like migrations and platform decisions that no single team owns.
Is staff engineer the same level as engineering manager?
At most companies with a dual ladder, yes - same level, same pay band, different work. Staff engineers influence through technical judgement and writing; managers own people, hiring and delivery.
How do I get promoted to staff engineer?
By doing the job before you have the title. Find a real problem affecting several teams that nobody owns, write the document that makes it concrete, and drive it to a decision. Staff promotions typically recognise six to twelve months of already operating at that scope.
Can you be a staff engineer without leading people?
Yes - that is the point of the track. You will lead work and influence decisions, but without direct reports, performance reviews or headcount. Influence comes from being trusted rather than from reporting lines.