UK Career Change · 2026
Software Engineer to Engineering Manager
Difficulty
Moderate
Typical timeline
6-18 months
From → To
Tech → Tech
Engineer-to-EM is one of the most common transitions in UK tech — and one of the most under-prepared for. Roughly half of engineers who become managers regret it within 12 months and either return to IC or struggle for 2-3 years before settling into the role. The 6-18 month timeline reflects the time needed to build credibility doing manager-shaped work before formal promotion. The successful EMs are the ones who explicitly chose the people-management path, not the ones who fell into it because senior IC felt blocked.
Salary impact
Often slight cut at transition (-5 to -10%) at growth-stage; reaches +10-30% at senior EM/director
Why this transition works
- ✓Internal transitions where the engineer already has the technical respect of their team are the highest-success path
- ✓Senior engineers who've been informal mentors and tech leads have proved interest and aptitude before formal promotion
- ✓Engineering organizations need EMs who understand engineering work; pure-people-manager EMs lose credibility fast
- ✓Senior EM and director paths in UK 2026 pay well — £130-200k base plus equity at growth-stage SaaS
The hard parts (don't skip these)
- !The first 6 months are existentially uncomfortable — you're being judged on your team's output, not yours, and the team takes time to mature
- !Many EMs struggle to give up the dopamine hit of solving production problems themselves and instead let engineers grow
- !Performance management — including managing out — is a skill no engineering training prepares you for
- !The IC ladder at senior levels (Staff, Principal) often pays as much as EM with less context-switching cost
Step-by-step plan
- 1
Decide explicitly: do you want to manage people?
The honest version of this question is: do you want to spend 60% of your time on 1:1s, performance management, hiring, and stakeholder work, with engineering work as a small minority? If the answer is "I want to do more eng but with manager title", aim for staff/principal IC instead.
- 2
Take on tech lead or informal mentorship work (3-6 months)
Before formal manager promotion, do manager-shaped work without the title. Run technical onboarding for new joiners, mentor 1-2 junior engineers, lead a cross-team project. This builds the credibility for formal promotion.
- 3
Read EM-specific material
"The Manager's Path" (Camille Fournier) is the canonical EM book. "Resilient Management" (Lara Hogan) is the second-best. "Staff Engineer" (Will Larson) helps decide between EM and Staff IC paths.
- 4
Practice 1:1s, performance feedback, hiring
Volunteer for hiring panels at your company. Ask your current EM to let you run 1:1s with junior engineers. Volunteer to give performance feedback. The skills are practiced, not innate.
- 5
Internal promotion is the highest-success path
If your current company has a clear EM track and you've done the manager-shaped work, internal promotion has 80%+ success vs 50% for external EM hires. The team already trusts you.
- 6
Plan to fail-stop the transition if needed
Some engineers try EM and discover they hate it. Have an explicit conversation with your VP/director: "If after 12 months I want to return to IC, what's the path?" Companies that can't answer this are red flags.
CV adaptations for this transition
- →Lead with team/scope: "Engineering Manager — 8 reports across 2 squads"
- →Hiring numbers (hires made, retention rate) prominent
- →Promotion track record (engineers you helped promote) — the highest-leverage EM signal
- →Reduce technical depth in CV by half — you don't need to demonstrate IC strength at EM level
Red flags that derail this transition
- ✗Becoming EM because senior IC promotion was blocked — bad reason, common cause of failed transitions
- ✗No interest in 1:1s, hiring, performance management — flags wrong fit
- ✗Trying to keep IC depth while managing — the dual-track works for ~6 months then breaks
- ✗External EM hire at company where you don't know the codebase or team — high-failure path