Career Progression

Getting from Senior to Staff is not the next level of the same game. It is a different game wearing the same scoreboard. Senior is granted for reliably doing the work well — you ship, your designs hold, your reviews catch things, you can be handed an ambiguous problem and trusted to return it solved. Keep doing that better and you stay a strong Senior. You do not become Staff.

Staff+ is granted for impact and scope, and it is almost always recognized after the fact, not earned by asking. You operate at the level for a while — months, often a year — and the title catches up to a reality that already exists. Nobody gets promoted into Staff scope; they get promoted because they were already exercising it. If you are waiting to be handed Staff-level work so you can prove you deserve the title, you have the order backwards.

This page is about how the promotion actually works, why people stall on it, and what to do about it. For the shape of the destination, see Staff+ archetypes.

The Currency Is Scope and Impact

There is a difference between "did great work" and "changed what the org does," and the promotion turns entirely on the second.

• Did great work — shipped a hard feature, owned a service well, closed the gnarly bug, mentored a junior. This is excellent Senior behavior. It is also the floor, not the case.
• Changed what the org does — the architecture three teams now build on, the migration that unblocked a quarter of roadmap, the standard everyone adopted, the incident class that stopped happening. The blast radius extends past your own keyboard.

Scope is the size of the problem you own; impact is the size of the dent the solution made. The promotion needs both. A perfectly-executed solution to a small problem does not get you to Staff, and a half-executed swing at a huge problem does not either.

And the brutal part: quietly excellent work that nobody can see does not get promoted. This is not a call to politics. It is a recognition that a promotion committee decides based on what they can perceive of your impact, and impact that left no visible trace — no doc, no decision attributed to you, no stakeholder who'll vouch — is impact the committee cannot credit. Sponsorship and visibility are not optional extras layered on top of good work; they are how good work becomes legible to the people who decide.

How Staff+ Promos Actually Work

In most orgs past a certain size, Staff+ is not a manager's gift. It runs through a committee or calibration process, and it is decided on written evidence, not vibes.

The mechanism, roughly:

1. You and your manager (and ideally a sponsor) build a case — a packet, a promo doc, whatever your org calls it.
2. The packet maps concrete artifacts and outcomes against the level's expectations.
3. Peers and stakeholders supply supporting evidence, often as written feedback.
4. A committee of people who mostly do not work with you daily reads it and decides.

That last point reframes everything. The deciders weren't in the room for your work. The packet is the only version of you they meet. If the work was real but the packet is thin, the answer is no — and "no" usually means another cycle.

What strong evidence looks like:

Strong evidence is specific, attributable, and outcome-shaped. It names the problem, the decision you owned, and what changed in the world. Effort is not evidence. Busyness is not evidence. "Trust me, it was hard" is not evidence.

Finding and Shaping the Right Scope

The single most common reason a strong Senior never makes Staff: they keep waiting to be assigned Staff-level work. It rarely arrives wrapped and labeled. At this level you usually have to find the high-impact problem yourself, make the case that it matters, and create the opportunity to own it.

• Look for the problem that spans teams, that everyone agrees is bad and nobody owns, that keeps generating incidents or stalling roadmap. That is Staff scope sitting unclaimed.
• Pitch it. Write the doc that frames the problem and the bet. Get a sponsor to back it. Carving out the scope is the Staff-level skill — see scaling yourself.
• The role you get promoted into has to already be visible. If your impact is invisible glue work, identify a piece of it that can be made legible and own that piece loudly.

Waiting to be assigned is a trap because the assignment never comes — managers assign Staff work to people already operating at Staff, which closes the loop against you.

Sponsors, Managers, and the Trajectory Conversation

A manager owns your performance, your day-to-day, and submits your case. A sponsor is someone senior — often not your manager — who will spend their own credibility advocating for you in rooms you are not in. The committee is one of those rooms. You need a sponsor; a supportive manager is necessary but rarely sufficient at Staff+.

You build sponsorship the slow way: by doing visible, attributable work that a senior person can point at and say "that was them, and it mattered." You cannot ask for a sponsor; you earn one by making it easy to advocate for you.

Managing up about your trajectory is your job, not your manager's. Make the goal explicit. Have the trajectory conversation on purpose:

• "I'm aiming for Staff. What does the bar look like here, concretely?"
• "What scope would I need to be owning that I'm not yet?"
• "Where's the gap between what I'm doing and that bar, and what closes it?"
• "Who would need to vouch for me, and do they have evidence yet?"

A manager who can't answer these is a signal in itself. So is one who keeps saying "soon" without naming the gap.

Why People Stall

Capable people get stuck at Senior for years. The usual causes:

• Invisible glue work with no narrative. The coordination, the unblocking, the quiet fixes that keep everything running — real impact, zero legibility. Glue work that isn't framed into a story the committee can read counts for almost nothing.
• No sponsor. Great work, nobody senior advocating. The committee never hears the case made well.
• Scope too small. Owning one service flawlessly. Excellent, and not Staff. The dent is the size of the problem.
• Optimizing for busy, not impact. A full calendar and a closed ticket queue feel like progress and read like Senior. Being maximally busy is often the opposite of increasing scope.
• Refusing to leave the comfort zone of hands-on coding. The hardest one. Staff+ means more writing, more aligning, more deciding, and less of the keyboard work that got you here and that you're good at. People who won't let go of the comfortable work cap themselves.

The IC vs Management Fork

At some point the track forks: keep going as a senior IC, or move into management. This is a real choice, not a demotion in either direction.

• They are different jobs, not different levels. Staff IC and Engineering Manager are usually paired in level and pay.
• IC keeps technical judgment as the product; management makes the team's output the product. See the IC vs management breakdown.
• Picking management because "that's how you advance" is a mistake at any org with a real IC ladder. Picking IC because "I don't want to deal with people" is also a mistake — Staff+ is full of people work, just without the reporting line.
• You can switch tracks, and often switch back. A tour in management makes a sharper Staff engineer; a strong IC makes a more credible manager. Treat it as a two-way door, not a cliff.

Decide on the work you want to spend your days doing, not on the org chart.

Down-Leveling Honestly

Sometimes the next level genuinely isn't available where you are. The Staff scope is taken, the org isn't big enough to need another Architect, the budget for the level doesn't exist this year. This is not always a verdict on you.

Be honest about which situation you're in:

• You're not at the level yet. Then the answer is the rest of this page: scope, evidence, sponsor, time.
• You're operating at the level and the slot doesn't exist here. Then the calculus shifts to changing companies. A different org may have the headcount, the unmet need, and a committee that will read your case fresh.

Changing companies for a level is legitimate and common — but go in clear-eyed. You usually start without the relationships and context that made your scope possible, and some orgs down-level externals on the way in to see them prove it. Often the cleaner move is to get the title where your reputation already is, then carry it. Run the calculus on scope and sponsorship, not just on the offer.

A Practical Cadence

The work is long-horizon; the habits are weekly.

• Keep a brag / impact doc. A running log of what you did, what changed because of it, and the artifacts that prove it. You will not remember in eighteen months when the packet is due. This doc is the packet, drafted continuously instead of in a panic. Tie it to your individual development plan.
• Run trajectory check-ins. Every quarter or two, the explicit conversation above. Don't let the goal go unstated for a year and then be surprised.
• Seek calibrating feedback early. Ask someone already at the level — ideally a committee member or a sponsor — to read a draft of your case while there's still time to act on it. The expensive version of this feedback is a failed promo cycle.
• Check your level against the framework, not your feelings. Map your real behavior onto the career framework and find the honest gap.

The Self-Check

The title follows the level; the level is the work you're already doing, visibly, at scope.

Are you waiting to be given Staff-level work — or are you already doing it where the people who decide can see it?

If you're waiting, the title will keep waiting too. If you're already operating there and it's legible, the promotion is paperwork catching up to a fact.