The real criteria for Staff (not what the ladder says)
Every big tech ladder says roughly the same thing about Staff: "sets technical direction for a team or small org, drives multi-quarter initiatives, mentors senior engineers." Read it charitably and it's a scope statement. Read it operationally and it's four things your VP has to be able to say about you in a promo committee:
- Multi-team impact. Something shipped in the last 12 months that touched at least two teams and wouldn't have happened without you.
- Technical direction others followed. A design doc, an architecture call, or a migration where the org went the way you said, not the way it was going.
- Force multiplication. Junior and senior engineers around you are meaningfully more effective because of a system, doc, or standard you own.
- Judgment under ambiguity. A call you made where the right answer wasn't obvious, the data was thin, and the outcome validated the call.
Notice what's not on this list: line count, ticket velocity, on-call heroics, or "senior for three years." Those are the traps.
The trap: doing more Senior work harder
The single most common pattern I see in senior ICs who don't get promoted: they respond to "you're close to Staff" by doubling down on Senior work. Bigger tickets. Harder problems. More PRs merged. More on-call weeks taken. This is why they stay at Senior.
Staff is not "Senior with more output." It's a different job. If your calendar this quarter looks like last quarter's, ticket queue, code review, standup, on-call, you are not promotable, regardless of how well you're executing.
What the promotable calendar looks like
Six months before you make the case, roughly 30% of your week should be work only a Staff engineer would be doing. Concretely:
- A cross-team initiative you're driving (not participating in).
- Design docs on choices at the org level, not the feature level.
- Standing 1:1s with staff+ peers in other teams - this is how information asymmetry gets fixed.
- A visible artifact that outlasts you - a standard, a library, a migration playbook, a runbook other teams cite.
- Time with your skip and your VP that isn't project status - architecture, org shape, hiring bar.
If none of that fits inside your current job description, the conversation is not "should I get promoted" - it's "what work do I need to be doing that I currently am not?" Your manager owes you that conversation. If they won't have it, that's diagnostic.
The promo packet that works
Most promo packets read like a resume: "I did X, Y, and Z." That format is designed for someone who doesn't know you. The committee already knows you exist. What they need is the case.
The four-section packet:
- The scope claim. One paragraph. "Over the last 12 months I operated at Staff scope on [initiative], across [teams], with [outcome]." Concrete, not adjectival.
- Two to three artifacts. Links to the design doc, the migration plan, the RFC - the actual documents. Not descriptions of them.
- Testimonials from staff+ peers outside your team. Not your manager, not your reports. Peers at the level you're being promoted to, in adjacent orgs. This is the single highest-signal item in the packet.
- The forward statement. One paragraph. "In the next 12 months at Staff, I will own [X] and unblock [Y]." The committee is not just promoting you for the past - they're making a bet on the future. Give them the bet.
The five mistakes that kill promo cycles
- Waiting for your manager to raise it. They won't. Your promotion is not on their P0 list. It's on yours. Raise it in your 1:1 by name, with a target cycle.
- Only having your manager as a sponsor. Committees discount single-source cases. You need at least one staff+ voice outside your reporting chain to say the words.
- No skip-level relationship. Your VP will be in the room. If they can't picture you doing the job, the packet doesn't matter. See our skip-level pillar below.
- Ambiguous artifacts. "I influenced the architecture" is not an artifact. A design doc with your name on it, that shipped, is.
- Missing the calibration window. Promo committees run on a cycle. If you find out in month 10 that the packet is due at month 11, you've already lost the cycle. Ask your manager, in writing, when the next Staff calibration is - this quarter.
What to do if you keep getting "next cycle"
"Next cycle" is not neutral. It's a soft signal you're close, or a soft signal your manager is buying time. The right question, asked once and directly, is: "What specific evidence would you need to see between now and [date] to write the case yourself?"
Three outcomes from that question:
- They give you a concrete list. Execute against it. Confirm delivery in writing.
- They give you a vague list. You have a manager problem, not a scope problem. Fix the manager problem - skip-level, mentor, or move.
- They tell you the committee, not them, is the blocker. Ask which staff+ engineers on the committee they can introduce you to. Real sponsorship shows up here or it doesn't.
When to leave for Staff instead of promoting to it
Sometimes the fastest path to Staff is a different company. Two signals it's the right move:
- Your current org has no Staff engineers doing what you'd do - there's no seat to promote you into.
- You've been at "close" for 18+ months with no committee cycle-over-cycle movement.
External Staff offers usually beat internal Staff promotions on comp by 20–40%. That's not an argument for leaving - it's an argument for having the option. The Senior Landing Program™ works on exactly this: senior operators running a real search while still holding down the current role.
The bar under the bar
The written Staff criteria are a floor. The real bar is: can your VP quote you in a room you're not in? If your VP can't finish the sentence "the reason we shipped X the way we did was because [your name] argued that…" - you don't have a promo case yet. That's the work.