There is no single ladder here. Titles in management vary more than almost anywhere, so think of it as two axes. Leading people grows in scope, from one team up to a team of teams. Owning delivery is the coordination track, the plan and the flow, and often carries no direct reports at all.
Pick any role to open it. These are general, universal definitions; the exact title, scope, and ladder shift with company, country, and culture, so treat this as a compass, not a rulebook.
Management is not a switch you flip; it is a set of skills you build, ideally before the title ever arrives. Four phases, drawn from the field's most-cited leadership writing.
Test the role
Build these while still an engineer, ideally as a Tech Lead, so you can confirm the move before committing to it.
- Lead a project end to end: break down the work, sequence it, and keep others unblocked.
- Mentor an engineer, and notice whether their growth energises you or drains you.
- Run a meeting, and write a clear decision doc or status update.
- Give small, direct feedback, and sit with the discomfort of it.
- Check the three signals honestly: drawn to the meta-work, more leverage through others, and the next thing you want needs coordination more than code.
Listen before you act
The most-repeated rule across every source: do not change things fast.
- Days 1 to 30, learn and listen: the team, the systems, the politics. Resist the urge to reorganise.
- Establish the weekly one-on-one as a space for them, not a status check.
- Fix one small, visible problem to earn early credibility.
- Stop coding on the critical path: your output is now the team's output, not your commits.
- Find the IC work you are still secretly holding, and hand it off.
Build the machine
Move from doing the work to building the system that does it.
- Delegate deliberately: match work to people, give context, stay available without hovering.
- Run a full feedback and performance cycle, including your first hard conversation.
- Own hiring end to end: write the role, interview, and make a hire.
- Set a six-month direction, and connect the daily work to it.
- Build the partnership with product and with your peer managers; manage upward as well as down.
Manage through systems
Your leverage is now the team as a system: its design, its process, its direction.
- Manage the system, not just the people: process, team design, and strategy.
- Grow a senior engineer or an aspiring lead beneath you.
- Right-size the team: six to eight reports is the sustainable band.
- Write strategy and drive change, not just run the existing cadence.
- Choose your fork: stay an Engineering Manager, go wider toward Director, or step back to the senior-IC track if the people-work drains rather than fuels you.
Not sure where you fit? Take the quiz ↓