Why senior engineers stall at the manager threshold.
The promotion bar isn't about more output — it's a different operating model. What changes at the threshold and how to evidence it before the panel.
Most senior engineers who stall at the manager threshold aren't stalling on talent. They're stalling because they keep showing up to the promotion conversation with the wrong evidence.
The threshold is an operating-model change
Up to Senior, you're rewarded for personal output: hard problems solved, systems shipped, code quality. The promotion to EM (or Staff, on the IC track) is not "more of that". It's a different job with a different scorecard — throughput of a team, clarity of direction, hiring, retention, cross-functional trust.
Panels reject candidates who present a louder version of the Senior scorecard. They promote candidates who present early evidence of the next scorecard.
What to evidence before the panel
- Throughput you caused but didn't ship yourself. Projects where your leverage came from unblocking others, sharpening scope, or coaching a junior into a senior moment.
- Written artefacts. Quarterly plans, RFCs, post-mortems, hiring scorecards. The currency of leadership is written thought.
- Org judgement. A moment where you made a call about *people* or *team shape* and it paid off — or a moment you made the wrong call and learned from it publicly.
- A hiring-manager-shaped narrative. Two sentences on what kind of EM you'll be, who you hire, and what your team will be known for in 12 months.
The trap
The trap is staying technically excellent and waiting to be noticed. Promotions at this level are *granted*, not *earned* — and they're granted to the person whose evidence already looks like the next role. Start producing that evidence now.
