Your Manager Can't Promote You to Staff (Here's Who Can)

Most engineers think promotion to Staff is their manager’s decision.

It isn’t.

Your manager can nominate you. They can advocate for you in the calibration meeting. They can write a compelling promo doc. But they cannot give you the title. That decision belongs to a room full of people who have never worked with you directly and will never see your day-to-day contributions. They’ll evaluate you based on a document, a few data points, and whatever your manager says in a 10-minute discussion.

That’s the game. Understanding it changes how you play it.

The Calibration Room

At Facebook, promotion decisions happen in calibration. Your manager presents your case to a group of other managers and senior ICs. These people have their own teams to advocate for. They’re also implicitly the check on whether someone is being promoted for the right reasons or just because they’ve been around long enough.

Your manager is your advocate. Everyone else in that room is, at best, neutral. Some are quietly skeptical. They’re asking: is this person actually operating at Staff, or does their manager just like them?

The way they answer that question is by looking for evidence that people outside your immediate team know who you are and can speak to your impact. If your manager says “she’s been critical to our infrastructure reliability” and nobody else in the room has heard of you or your work, that’s a soft no. If three other managers have worked with you on cross-team initiatives and can independently confirm the claim, it becomes very hard to block.

That’s the mechanic. Your manager doesn’t have enough votes to carry a promotion alone. You need social proof from people outside your chain of command.

The Scope Problem

Most engineers who get stuck at Senior are operating at the right level technically. They’re good engineers. They ship reliably. Their manager trusts them.

The problem is scope.

Senior engineers own their work. Staff engineers own problems that span teams. The gap isn’t technical depth - it’s organizational reach. A Staff engineer at Facebook was expected to identify something that was going wrong across multiple systems or teams, take ownership of it without being asked, and drive it to resolution. Not as a project handed to them. As something they surfaced themselves.

If you’re waiting to be assigned cross-team work, you’re operating as a Senior. Staff engineers find the cross-team work. They see the gaps between teams - the places where nobody owns the problem because it falls between org boundaries - and they walk into those gaps.

The engineers I saw get promoted to Staff weren’t the ones who executed perfectly on their assigned scope. They were the ones who kept expanding their scope until the scope matched the title.

Who Actually Needs to Know Your Name

Think about the last six months of your work. Now ask: which engineering managers outside your direct team know what you contributed? Which Staff or Principal engineers outside your org have worked with you on something substantive? Which product or infra leaders have seen your judgment in a room?

If the answer is mostly nobody, you have a visibility problem - and no amount of excellent execution fixes it.

The engineers I watched get promoted had typically done a few things: presented work at a broader engineering forum, driven a project that required sign-off or collaboration from another org, or written something (design doc, post-mortem, technical analysis) that circulated beyond their immediate team and got traction.

These aren’t career management tactics. They’re outputs of doing the kind of work that Staff engineers actually do. If you’re doing Staff-level work, visibility follows naturally because that work touches other teams. If you’re doing Senior-level work but trying to manufacture visibility, calibration rooms see through it pretty quickly.

The Promo Doc Problem

Your manager writes your promo doc. But the most effective promo docs I ever saw were heavily influenced by the engineer being promoted, because the engineer knew their work better than anyone.

A weak promo doc describes what you did. A strong one makes a case for what you’re already operating at.

There’s a difference. Describing work says “she built the reliability dashboard.” Making a case says “she identified that our on-call escalation patterns pointed to a systemic gap in observability tooling, proposed and drove adoption of a new standard across four service teams, and measurably reduced mean time to resolution by 40%. This was work she initiated, not assigned.”

The second version answers the calibration room’s implicit question: is this person already operating at Staff, or are we hoping they’ll grow into it? Promotions to Staff are supposed to recognize that someone is already there, not bet that they’ll get there.

If you want to make your manager’s life easier and your promotion more defensible, document your work the way the second version does. Keep a running list. When you finish something significant, write down what you saw, what you decided, who you influenced, and what changed. Your manager will use it.

The Three Things That Carry a Promo

When I think about the Staff promotions that went through cleanly versus the ones that got deferred, three things kept appearing in the clean ones.

Cross-team impact with receipts. Not “worked with other teams” but “drove adoption of X across teams A, B, and C, resulting in Y.” Names, numbers, outcomes. The calibration room can verify this if they want to.

Technical judgment under ambiguity. Everyone who gets to calibration has shipped things. What separates Staff is documented evidence that they made hard calls in unclear situations and were right. Design docs where they analyzed trade-offs and made a defensible choice. Post-mortems where they identified systemic issues, not just immediate fixes. Technical decisions with real stakes.

Someone else in the room who knows your work. A manager from another team who can say “yes, I worked with them on the data pipeline redesign and their judgment was critical” is worth more than three paragraphs in the promo doc. Not because it’s more accurate. Because it’s independent confirmation. It removes the question of whether your manager is just advocating for their favorite person.

What This Means for How You Work

If you’re a Senior engineer who wants to make Staff, here’s the practical implication.

The work that gets you promoted is probably not the work on your current team roadmap. It’s the gap nobody assigned you to own. The cross-team problem your manager would say yes to if you proposed it. The technical standard that doesn’t exist yet but should. The post-mortem that turns a production incident into organizational learning.

That work won’t appear in your sprint planning. You have to find it.

And when you do it, document it clearly enough that someone who wasn’t there can understand what you saw, what you decided, and what got better. That’s what ends up in the promo doc. That’s what gets talked about in calibration.

Your manager is on your side. But they can’t win the room alone. You have to give them ammunition - and then make sure there are other people in that room who’ve seen you operate firsthand.

The title doesn’t come from your manager. It comes from the organization’s collective recognition that you’re already working at that level. Your job is to make that recognition undeniable.

If you’re preparing for Staff-level interviews or building the case for promotion, the SWE Interview System covers what interviewers are actually looking for at senior and Staff levels - including what “operating at the next level” looks like in an interview room.