The 5 People Who Actually Decide If You Make Staff

A few weeks ago I wrote about how your manager can’t actually promote you to Staff. That post hit 63,000 impressions, which told me a lot of engineers didn’t fully understand the mechanics of what happens in a calibration room.

This post is the follow-up. Because once you understand that your manager doesn’t decide alone, the obvious next question is: who does?

The answer is five distinct people or groups. Some of them you know. Some of them you’ve never thought about in the context of your promotion. All of them matter.

Here’s who they are and what they’re looking at.

1. Your Skip-Level Manager

Your direct manager makes the case. Your skip-level either backs it up or quietly kills it.

In most calibration processes, the skip-level is in the room alongside your manager. They’re not a neutral observer. They’re expected to have a view, and their view carries more weight than your manager’s because they’re less likely to be seen as biased.

If your skip-level doesn’t have an independent impression of you - if the first time they really heard your name was when your manager put you forward - that’s a problem. It doesn’t mean you won’t get promoted. It means your manager is carrying the whole argument alone, and that’s a weaker position than it needs to be.

What your skip-level needs to see is not just performance data. They need to feel like they know you. They need a mental model of what you work on, how you think, what kind of problems you solve. That mental model gets built through exposure, not through your annual review doc.

The practical implication: your skip-level should already know who you are before calibration season starts. That means being visible in forums they attend, speaking up in all-hands or planning discussions, and making sure you’ve had at least a few substantive conversations with them directly - not just through your manager.

At Meta, I watched promotions succeed or fail based almost entirely on whether the skip-level had enough signal to actively support the case rather than just not object to it.

2. Peer Staff and Principal Engineers

Technical credibility at the Staff level gets validated by the people who already hold it.

Most calibration processes include senior technical voices - Staff or Principal engineers who can speak to whether your work genuinely operates at the level being proposed. They’re there specifically because engineering judgment isn’t something managers can always assess on their own. Their job is to say: does this work look like Staff work to me, or does it look like ambitious Senior work?

These are your peers. You probably work alongside some of them. And if they don’t respect your technical judgment, if they haven’t seen you make calls that turned out to be right, if they know you mostly as someone who executes well but defers to others on design decisions - that’s the impression they’re bringing into the room.

What they’re looking for isn’t a list of projects. It’s a pattern of judgment. Have you made technically defensible decisions under ambiguity? Have you pushed back on a direction when you had good reason to, and been right? Have you identified a problem before it became a crisis?

Those moments - the ones where you were visibly right about something hard - are what Staff engineers remember about other Staff engineers. Your promotion case is stronger when multiple people in that room have a memory of you doing something like that.

This is also why code review behavior matters more than most engineers realize. How you engage with other people’s work, what you catch, how you frame feedback - all of that is signal. It’s not just contribution. It’s evidence of technical judgment at scale.

3. Cross-Functional Leads You’ve Worked With

Calibration and review meetings are primarily engineering folk. PMs, design leads, and TPMs aren’t usually in the room. But their voices get there through a different channel: you.

Your self-review is where XFN feedback lives or dies. If a product manager you partnered with on a complex migration thinks your technical judgment was the reason it shipped on time, that’s powerful evidence. But nobody in the calibration room will know about it unless you surface it yourself.

This means two things. First, you need to actively collect feedback from XFN partners throughout the year, not scramble for it before review season. A quick message after a project wraps (“how did the collaboration go from your side?”) gives you material to draw on later. Second, your manager needs to know about these relationships well before calibration. If the first time your manager hears that the payments PM considers you indispensable is when they’re reading your self-review, it’s too late to build that into a compelling case.

“We wouldn’t have shipped the Q3 platform migration without the architecture decisions [your name] made in the design phase” is a different kind of evidence than a manager saying “they showed technical leadership.” The first is specific and comes from someone with no direct stake in your promotion outcome. The second is expected.

XFN leads also speak to something managers often can’t fully characterize: whether you’re someone other functions actually want to work with. At Staff level, a significant portion of your job is influencing people you don’t have authority over. If your XFN partners find you difficult, territorial, or hard to align with, that will surface in your peer feedback and your manager’s own observations, even when it doesn’t show up directly in your performance review.

The engineers who get promoted to Staff most cleanly are the ones whose cross-functional credibility is already well-known to their manager and skip-level. Not because the XFN leads are in the room, but because the evidence they provided made it there first.

4. The Skeptic in the Room

Every calibration has one. Sometimes it’s a peer Staff engineer from a different org. Sometimes it’s a senior manager who’s seen a lot of promotions and has a high bar for what Staff actually means. Sometimes it’s the VP running the session who’s calibrating against candidates from five other teams.

The skeptic’s job - whether or not it’s a formal role - is to push back on the cases that aren’t airtight. They ask things like: “What’s the system-level impact of that project?” or “Could a strong Senior engineer have done this with the right support?” or “What’s the evidence that this person sets technical direction rather than follows it?”

You cannot prepare for the skeptic directly. What you can do is make sure your manager has answers to those questions before they walk into the room.

The preparation that matters is working with your manager months before calibration to anticipate the hardest version of the pushback. What would someone skeptical of your promotion say? What’s the weakest part of the case? What evidence exists that directly addresses those weaknesses?

Promotions that get deferred most often aren’t deferred because the work was bad. They’re deferred because the case wasn’t built to survive scrutiny. The skeptic found a gap that nobody had thought to fill.

If your manager can’t tell you what the hardest objection to your promotion case would be, that’s a signal that the prep isn’t done yet.

5. You

Not you in the room - you’re not there. But you through every piece of evidence that exists before anyone says your name in that room.

Your written communication. The design doc you authored that got referenced by three other teams. The incident post-mortem where your analysis changed how the org thought about a class of problems. The email thread where you laid out a trade-off clearly enough that a VP cited it in a planning meeting. The PR descriptions that actually explain why a change was made, not just what it does.

At calibration, your manager summarizes. The summary is built from a stack of artifacts you produced, conversations you had, moments people remember. If that stack is thin, the summary is thin. If the stack is rich, your manager has material to work with.

This is the part you control most directly, and it’s the part engineers underinvest in most consistently.

The mistake is thinking that the work speaks for itself. It doesn’t. The work speaks through documentation, through the reactions it generated, through the problems it visibly solved. Staff-level work that nobody outside your team knew about isn’t Staff-level evidence at calibration.

Write things down. Share your thinking publicly. Make your reasoning visible in forums where people with calibration input can see it. Not to self-promote - to create a record that your manager and your skip-level can point to when someone asks “what’s the actual evidence here?”

The engineers who get promoted to Staff most consistently are the ones who understand this and build the evidence trail intentionally, not retroactively.

Calibration rooms are not mysterious. They’re rooms full of people with limited time, limited context, and a hard decision to make. The ones who succeed are the ones who gave those people something real to work with - months before anyone said their name out loud.

If you’re building toward Staff and want someone who’s been in those calibration rooms to look at your specific case, book a consultation. I coach senior engineers through exactly this transition. If you’d rather start with a self-guided approach, the SWE Interview System covers how to talk about scope, impact, and technical leadership in ways that land with hiring committees.