Stuck Below Staff: The Jump from Executing to Setting Direction
Senior to staff — P6→P7 at Alibaba, T6→T7 at Tencent, 2-2→3-1 at ByteDance; every Chinese big tech company has its own label for the same wall — is the hardest step on the IC ladder. Around 70% of people sit here for two or three years. Some never get through and quietly stop trying.
The reason usually isn't that they're not technical enough. It's that nobody told them the job changed identity.
What Actually Separates Senior from Staff
It isn't more of the same. Staff is not "senior work times 1.5 difficulty."
It's a change of role:
| Senior (P6) | Staff (P7) | |
|---|---|---|
| Where work comes from | your manager assigns it | you find it |
| Unit of work | one feature, one system | a class of problems, a business area |
| Blast radius | you ± your immediate team | your org, or across orgs |
| Decisions you own | how to build it | whether to build it, when, and who does it |
| Definition of success | delivered on time, at quality | the business goal actually moved |
| What the committee looks for | was the work hard enough | what did you change |
The ceiling of senior is "extremely strong executor." The entry ticket to staff is "spots the problem, convinces people it matters, makes it happen."
Three Ways People Get Stuck
Pattern 1: great executor, permanently waiting to be assigned
You write code fast, ship few bugs, document properly, never complain about crunch. But every project you've done started with your manager saying "go do X."
At senior this reads as exceeding expectations — the execution is genuinely strong. Then your manager sits down to write your promo packet and hesitates: "can he own a whole area without me steering? I'm not sure."
How to break it: every quarter, find one thing nobody asked you to do but you believe should be done, do it, and show it. Start small — clean up a process, build an internal tool — and grow the complexity from there.
Pattern 2: deep expertise, famous only inside your own team
You're the person on the team who knows the most about some domain. Nobody outside the team knows you exist.
At the promo review someone asks "does anyone outside their team know what this person did?" and the room goes quiet.
How to break it: at least once every six months, produce something visible outside your team — a cross-org tech talk, an internal writeup people actually forward, or owning the technical design on a cross-team project.
Pattern 3: filing yourself under "I'm the technical one"
Every time something non-technical shows up — a business discussion, a cross-team turf fight, a product review, hiring — you say "not my strength, let the PM or the lead handle it."
Staff engineers are technical experts, but an expert isn't someone who only understands the technology. You have to understand the business the technology serves. If you can't hold a conversation with product, ops, and the teams up and downstream of you, the org has nowhere to put you.
How to break it: get into business decisions on purpose. Even just raising one business-side question in a design review. Build the vocabulary that isn't code.
Four Steps to Move a Promo Within a Year
- Find a staff-sized problem. Go ask three people one level above you (people who already made staff) the same question: "what around here should a staff engineer own that nobody owns?" The answers are usually cross-org tech debt, an unexplored direction, or the architectural evolution of a system that outgrew itself.
- Get your manager to agree that you own it. Not "can I do this," but "I'm going to do this, here's what I need from you." Get it formally assigned, or the credit ends up on someone else's packet.
- Ship a milestone within six months. It doesn't have to be the final state. It has to be visible enough that your org, your manager, and your manager's manager all know X is driving this.
- Start seeding the narrative two months before the review. Talk about your work with three people outside your reporting chain, so the room contains people who have heard your name before.
Something Almost Everyone Misses
You don't wait your way to staff. You do your way there. Every year somebody sits at senior for five years with nothing moving, then gets one thing right and is promoted in six months. The difference isn't tenure. It's whether one staff-sized piece of work got done by you and got seen by the org.
If you're three years into senior and nothing on your plate looks like that, answer one question first: is there no opportunity, did you fail to recognize one, or did you see one and not dare take it?
Three answers, three completely different fixes. It's usually the third.
Closing
Being stuck below staff isn't worth anxiety. It's worth honesty. Look at the last twelve months of your work and ask three things: is it staff-caliber, was it visible, could someone else have done it just as well. Any "no" is the thing to go fix. Talk about the promo after.