Engineering Manager career path: from tech lead to CTO
Each step up the engineering management ladder, from tech lead to engineering manager, senior engineering manager, director of engineering, VP of engineering and CTO: what changes in the job, the gap to close, how to show it on your CV and in interviews, and a plan.
The cvscored team
Contents
The ladder at a glance
| Step | What you are measured on next | Typical time |
|---|---|---|
| Tech lead to engineering manager | People: their growth, hiring and the team's health | 1 to 3 years as lead |
| Engineering manager to senior engineering manager | Several teams and their leads | 2 to 4 years |
| Senior engineering manager to director of engineering | Managers of managers and an area's plan | 3 or more years |
| Director of engineering to VP of engineering | The engineering organisation and its budget | Several years |
| VP of engineering to CTO | Technology strategy for the company | When a company asks |
Most engineering managers were engineers first. The developer ladders, with their own step from lead developer into management, are on the software developer career paths, the backend developer career paths and the frontend developer career paths; operations engineers come up through the DevOps engineer career paths.
Not every senior engineer wants to manage. The expert road, through architecture to chief architect, is on the software architect career paths; it meets this ladder at CTO, which companies fill from either road.
Engineering managers and enterprise architects meet in the technology strategy: one leads the people, the other plans the landscape; the architects' road to chief enterprise architect is on the enterprise architect career paths.
From tech lead to senior engineering manager
Tech lead to engineering manager
What changes: you become responsible for people, not only for the technical direction: their one-to-ones, feedback, growth and hiring, and the team's delivery and health.
The gap: leading peopleAsked in 8% of engineering manager ads (as of 5 Nov 2026).Lead people who know more than you about their code: set direction, give feedback, grow them, decide. without doing their work for them, hard conversationsAsked in 36% of engineering manager ads (as of 5 Nov 2026).Say the hard thing clearly and kindly, in one-to-ones, in writing and in front of leadership., hiring, and letting go of most of your own coding time.
On the CV and in interviews: the people you mentored, the project you led, the incident review you ran and the hire you helped make. Expect a question on feedback to a peer.
Plan (6 to 12 months): take on one-to-ones for one or two engineers with your manager's support; run the team's planning; sit on interview panels; read your company's career ladder.
Engineering manager to senior engineering manager
What changes: you lead two or more teams, often through tech leads or first-line managers, and plan work across them with product and other departments.
The gap: planning across teamsAsked in 36% of engineering manager ads (as of 5 Nov 2026).Plan larger deliveries across teams: milestones, dependencies, risks and an honest date range., stakeholder managementAsked in 10% of engineering manager ads (as of 5 Nov 2026).Keep product, design, sales and leadership informed and agreed on what the team does and why. at department level, growing new leads, and decisions on team shape and size.
On the CV and in interviews: the teams you led, a cross-team delivery, the leads you grew and a reorganisation you handled. Expect a case on splitting a team that grew too large.
Plan (12 to 24 months): take a second team or a cross-team project; coach a tech lead into their first people duties; own the quarterly plan of your area with product.
Director, VP of engineering and CTO
Senior engineering manager to director of engineering
What changes: you lead managers rather than engineers, own an area of the product or the platform, and answer for its plan, headcount and results.
The gap: managing managers, a yearly plan and budget, presenting to leadershipPresent a plan, an incident or a headcount request to leadership in a few clear slides., and setting standards for hiring and promotion across teams.
On the CV and in interviews: the size of the area, the managers you hired or grew, the plan you delivered and the change you led. Expect questions on calibrating promotions and on a manager who struggles.
Plan (2 to 3 years): lead the yearly planning of your area; hire and coach a new manager; own one engineering-wide topic, such as the career ladder or the incident process.
Director of engineering to VP of engineering
What changes: you run the engineering organisation or a large part of it: its structure, budget, hiring plan and ways of working, and you sit with the leaders of product, sales and finance.
The gap: organisation design, budgets and vendors, the culture of a large group, and speaking for engineering in the leadership team.
On the CV and in interviews: the organisation you built, its growth or restructuring, the budget you owned and the outcomes for the business. Expect a case: the first quarter in an organisation that misses its plans.
Plan (several years): own the engineering budget with finance; lead a reorganisation or a large hiring push; build a bench of directors and managers.
VP of engineering to CTO
What changes: you answer for the company's technology as a whole: strategy, architecture direction, security and risk, and often the board's questions about technology.
The gap: technology strategy tied to the business, working with the board, buying or building decisions, and partnership with the chief product officer.
On the CV and in interviews: the technology bets you made and their results, the risks you managed and the organisation you led. Expect questions from the board and investors.
Plan (when a company asks): take part in board and investor meetings; own a company-wide technology decision; build a successor for your current role.
Titles differ by company size: in a small company the CTO may lead a single team, and in a large one a director may lead hundreds of people. Read the scope in the ad, not only the title.
Your CV for the next step
Moving up in engineering management shows on a CV as a wider reach: from one team, to several teams, to an organisation. Three rules:
- Write each title as the company used it. The number of people and teams under it tells the reader the real level.
- Speak the next level's language. Manager ads say "one-to-ones", "hiring", "delivery"; senior and director ads say "managers", "planning", "organisation"; VP ads say "budget", "strategy", "leadership team".
- Tie a result to every line. People grown, hires made, delivery steadied, incidents reduced, costs controlled.
| Skill | Weak line | Strong line, with proof |
|---|---|---|
| Director of engineeringAsked in 8% of engineering manager ads (as of 5 Nov 2026).Lead people who know more than you about their code: set direction, give feedback, grow them, decide. | Led several teams. | Led four teams and their managers in the payments area; delivery became predictable and two leads stepped up to manager. |
| Organisation | Restructured the department. | Split a team of fourteen into two teams around customer journeys; hand-offs dropped and each team owned its releases. |
| PlanningPresent a plan, an incident or a headcount request to leadership in a few clear slides. | Responsible for planning. | Ran the yearly engineering plan with finance and product; headcount was approved in one round. |
| GoalsTurn company goals into a few team outcomes, measured by results rather than by tasks done. | Set team goals. | Introduced outcome goals for all teams; each quarter's review now shows customer results, not lists of tasks. |
Key takeaways
- The ladder runs tech lead, engineering manager, senior engineering manager, director and VP of engineering, then CTO.
- Each step is measured on a wider reach: people, then teams, then an organisation and its budget.
- The developer and DevOps ladders lead into this one; the career pages of those roles are linked above.
- At CTO the management road meets the architecture road.
- Titles differ by company size; the scope in the ad matters more than the title.
Frequently asked questions
- What comes after engineering manager?
- Senior engineering manager, then director of engineering, VP of engineering and, in some companies, CTO.
- Can I go back to engineering after managing?
- Many do, and good companies make room for it; this page describes only the steps up the management road.
- Do I need a management course to move up?
- No law or rule asks for one. Courses can help with the basics; the people you grew and the teams you led count for more.
- How many people does a director of engineering lead?
- It depends on the company: often several teams through their managers. Read the scope in the ad.
- What should my CV show for a director role?
- The managers you led and grew, the area and plan you owned, and the results for the business.