Growing your career
Promo blockers and when to move
Most stuck cases are missing scope, invisible impact, or a team with no next-level problems. Sometimes leaving is the plan.
Strong engineers get stuck for boring reasons. The title is not always available where you sit. Name the blocker, try the fix, and treat a team or company change as a strategy — not a failure of grit.
Walking through the usual blockers
| Blocker | What it looks like | Fix |
|---|---|---|
| Lack of scope | Great code, always on someone else's project | Take a finishable project; negotiate scope with your manager |
| Invisible impact | Quiet production heroics, no write-ups | Metrics, demos, launch notes; stop being secret |
| Communication gaps | Strong work, messy updates, surprise misses | Status habit from project execution |
| One-axis spike | Deep tech, no collaboration — or the reverse | Deliberately practice the weak axis |
| Team too small or flat | No next-level problems exist here | Change team or company |
| Manager mismatch | Will not advocate or cannot coach | Skip-level clarity; transfer; or leave |
"Needs more consistency" after a single strong project is often legitimate. "Needs more leadership" with no definition is a red flag. Ask for a behavioral definition and an example of someone who recently cleared it.
Change teams when: the product area has no next-level problems; your manager systematically blocks growth; or you are typecast as "the person who does X tickets."
Change companies when: the ladder is fake (titles without scope); the org is freezing promos indefinitely while you already meet an external bar; or total compensation and growth diverge badly from the market. Interviewing elsewhere is also how you learn what your level is outside your current bubble — useful even if you stay.
Leave well: finish critical handoffs, document ownership, and do not trash people in exit interviews. The industry is small; your reputation travels faster than your title.
Important
A title bump without scope growth is a trap. Push for responsibilities that match the new level.
If gaps keep shifting every cycle with no stable definition, combine that with the stay-or-go advice above. See also career strategy.
Common mistakes
- Waiting for grit to unlock a missing problem. If the work does not exist here, it will not appear from effort.
- Staying secret. Unwritten impact cannot be calibrated.
- Leaving badly. Finish handoffs. Reputation outruns the title.
Check yourself
Your manager says you need "more leadership" and cannot define it. What do you ask?
A behavioral definition and an example of someone who recently cleared that bar.
The team has no next-level problems and your manager will not move you onto one. What is the rational move?
Change teams — or companies if the ladder itself is fake or frozen.
Key takeaways
- Common blockers are missing scope, invisible impact, and fuzzy communication.
- A flat team or a blocking manager is not fixed by working harder on the same tickets.
- Leaving can be the correct strategy. Leave with relationships intact.
- Interviewing elsewhere calibrates your level even if you stay.
Further learning
Back to the map: how promotion works.
The Pragmatic Engineer (Gergely Orosz)Observations across the software engineering industry.The Pragmatic Engineer
Related
How promotion works
Evidence, packets, calibration and the manager conversations that turn next-level work into a title.
Working with your manager on promo
Make the goal explicit, share the brag doc early, and ask for scope that fills gaps — not only adjectives.
Career strategy
Choosing companies, teams and specialties deliberately: big tech vs startups, generalist vs specialist.