Tech lead to engineering manager
A tech lead is accountable for how the work is built. An engineering manager is accountable for the team that builds it: who is on it, whether they grow, whether the work is staffed, prioritised and sustainable. Many tech leads find the move is less 'more of the same, plus 1:1s' and more a change of what counts as a good day.
What changes
- Your output shifts from code and designs to decisions, hiring, feedback and a team that works without you in every thread.
- You become responsible for people's careers, pay conversations and performance, including difficult ones, not only for technical direction.
- You trade fast, visible feedback (a merged change) for slow feedback (a quarter of team health and delivery).
- You spend more time with product, other managers and stakeholders, translating between them and the team.
Skills to build
- Coaching and feedback. Weekly 1:1s, specific feedback and growth plans are the core of the job and are learnable with practice.
- Hiring. Structured interviews, calibration and closing candidates. Start by interviewing for your team now.
- Performance management. Setting expectations, documenting, and handling underperformance fairly and early.
- Delivery planning and prioritisation. Turning goals and capacity into a plan and saying no with reasons.
- Stakeholder communication. Explaining trade-offs to non-engineers and managing expectations upward.
- Staying technically credible. You rarely write production code, but you need enough depth to challenge designs and judge risk.
How to show evidence
- Hiring: number of interview loops you ran, roles you helped define, how you improved the process. Name outcomes you can verify, not claims about 'building teams'.
- Mentoring: a specific engineer you grew, what you changed together and what happened (with their consent if you name them).
- Operations: an incident-process or on-call improvement with before/after numbers you actually have.
- Planning: a delivery you owned across teams, what slipped and what you changed.
- Ask your manager for a trial scope (e.g. run planning or 1:1s for part of the team) so the evidence is real.
Common pitfalls
- Staying the best engineer on the team and becoming the bottleneck instead of delegating.
- Treating the move as a promotion without testing whether you enjoy the work; many people go back to IC and that is a fine outcome.
- Avoiding hard feedback because the team used to be your peers.
- Claiming people-management experience in interviews that was really technical leadership. Interviewers probe the difference.
First steps
- Run a role-fit check against two real engineering manager postings to see which requirements you can evidence.
- Volunteer for hiring loops and a recurring 1:1 with at least one junior colleague.
- Read a structured management text and write down three behaviours you will change.
- Practise leadership interview questions with specific stories from your own work.
This guide describes common patterns, not guarantees. Roles and expectations differ between employers.
See which skills you still need for this move and get ordered learning resources.
Build my roadmapAlso see the role guide and interview questions.