Senior to Staff: What Actually Gets You There

The senior-to-staff transition trips up more engineers than any other level change. Not because the technical bar is impossibly high. Because the game changes completely and nobody tells you the rules.

I watched this play out hundreds of times at Meta. Strong senior engineers who were clearly ready technically, stuck at the same level for two or three years. Not because they weren’t good enough. Because they were still playing the senior engineer game.

What actually changes at staff.

Senior engineers solve the problems in front of them. Staff engineers find the problems nobody named yet.

At the senior level, you’re expected to take a well-scoped problem and execute it well. Break it down, estimate it accurately, handle the ambiguity in implementation, ship it.

That’s not the staff engineer’s primary value. A staff engineer’s job is to look at a system, an organization, or a product area and see the thing that’s going to hurt you in 18 months, before it becomes a crisis. Then make it someone’s problem to fix - often including their own.

This is harder than it sounds because it requires a kind of thinking that engineering culture actively discourages. You’re trained to solve problems, not spend time identifying them. You’re measured on shipping. Spending a month mapping technical debt nobody asked you to map feels like slack.

The engineers who make staff find a way to do both.

Scope isn’t about complexity. It’s about whose problems you’re solving.

A senior engineer is responsible for their team’s work. A staff engineer is responsible for outcomes that span teams and often doesn’t have direct authority over any of them.

This is where a lot of strong engineers stall. They can run circles around anyone technically. But the moment the problem involves crossing org boundaries, aligning teams with competing priorities, or convincing a skeptical principal engineer in another org, the skills that got them to senior don’t transfer.

What does transfer: being right consistently enough that people want your opinion before making decisions. Not because you have the title, but because your judgment has track record behind it.

You can’t manufacture that quickly. But you can accelerate it by deliberately taking on cross-team problems, even when you don’t have to. Volunteer for the messy coordination work that senior engineers avoid. That’s where the visibility comes from.

The promotion isn’t a reward for being a very good senior. It’s a recognition that you’re already operating at staff.

This is what most engineers get backwards. They wait to be promoted and then start behaving like a staff engineer. The ones who actually get promoted are already doing staff-level work before anyone formally acknowledges it.

What that looks like in practice: other teams come to you for technical guidance on things adjacent to your area. Your work unblocks people you don’t work with directly. You’ve influenced a technical decision that affected a roadmap you didn’t own. You’ve identified a systemic problem and driven the solution to completion - not just flagged it.

If you can’t point to examples of these things, the promotion committee is going to tell you to go build them before they’ll say yes. Get ahead of that conversation.

The interview is a separate problem.

If you’ve done the work and you’re applying for staff roles externally, the interview is a completely different challenge.

Staff-level interviews expect you to demonstrate all of the above in real time. System design questions stop being “design Twitter” and start being “here’s a messy real-world situation with conflicting constraints, walk us through how you’d think about it.” Behavioral questions are looking for evidence of organizational impact, not just technical execution.

Most engineers who are legitimately operating at staff level still struggle in staff-level interviews because the communication patterns are different. Delivering signal in a structured interview, under time pressure, for a senior audience - that’s a skill you have to develop separately from doing the actual job.

The SWE Interview System includes level-specific guidance through senior and staff, including the system design and behavioral frameworks that matter at that level. Built from the hiring committee work I did at Meta calibrating exactly this.