Engineering Manager career ladder: levels, titles, and criteria

Q: How do you know if you should move from IC to engineering management?

The clearest signal is that you already spend real time and get real energy from unblocking other engineers, running design reviews well, and thinking about team process, not just your own code. It is a different job, not a promotion in the usual sense: a strong staff engineer can be a mediocre first-time manager and vice versa. Most companies want to see someone informally doing manager-shaped work, such as mentoring, leading a project across several engineers, or running planning, before they make the formal move.

Q: What changes at the manager-of-managers level?

At Group Engineering Manager or Director, your direct reports are other managers, not individual engineers. The work shifts from running 1:1s about someone code and career to running 1:1s about someone team health, their own management skills, and cross-team tradeoffs. You lose most day-to-day visibility into individual engineer work and instead have to trust and calibrate the managers under you. It is the single hardest transition in the ladder for most people, harder than the original IC-to-manager jump.

Q: What separates promotion between manager levels?

Between EM and Senior EM, it is usually about handling harder problems within a similar scope: tougher performance issues, bigger technical bets, more org design judgment, with the same or slightly larger team. Between Senior EM and Group EM or Director, the change is structural: you take on managers as direct reports and are evaluated on the org you build, not the team you personally run. Above Director, promotion is driven by business scope: how much of the company revenue, product surface, or headcount depends on your organization.

Q: How does this page relate to the general engineering career ladder?

The engineering career ladder page covers both the IC track and a shorter management-track summary side by side, as a single reference. This page is the deep dive specifically on the management track: team sizes, the IC-to-manager transition, the manager-of-managers shift, and promotion criteria between manager levels, in more detail than the summary table on the general page covers.

Career levels, titles, scope, and promotion criteria for engineering manager roles — from entry level to senior leadership.

Last updated August 2026

engineering manager career ladder — quick overview

An engineering management career ladder typically runs six levels: Engineering Manager -> Senior Engineering Manager -> Group Engineering Manager (manager of managers) -> Director of Engineering -> VP of Engineering -> CTO. The biggest structural shift happens at the Group Engineering Manager or Director level, where the job changes from managing individual engineers directly to managing other managers, and success is measured through the org you build rather than the code that ships.

Turn this ladder into a live framework for your team. Start free →

Engineering Manager IC career levels

Level	Title	Scope	Key differentiator	Typical YoE
M1	Engineering Manager	One team, 4-8 engineers, direct reports are ICs	Runs 1:1s, performance reviews, and hiring for their team; owns delivery for a defined product area; usually a former senior or staff engineer in their first management role; still reads code and joins architecture discussions	5-8
M2	Senior Engineering Manager	One larger team or two closely related teams, 8-15 engineers	Owns a larger or more complex product area; handles harder performance and org design problems; mentors first-time managers informally; has more input into hiring plans and roadmap tradeoffs	7-11
M3	Group Engineering Manager	Multiple teams via other managers, 15-30 engineers	First level that is manager of managers: direct reports are EM1/EM2s, not individual engineers; owns cross-team coordination and a multi-quarter roadmap; job shifts from unblocking individuals to unblocking managers and resolving cross-team conflict	9-14
M4	Director of Engineering	A full department or business unit, 30-60 engineers	Owns headcount planning, budget, and org structure for a department; sets technical and delivery strategy across multiple product areas; represents engineering in cross-functional leadership discussions	12-18
M5	VP of Engineering	The full engineering organization	Owns engineering strategy, org design, and delivery for the whole company; sits on the executive team; balances technical investment against business priorities at the company level	15+
M6	CTO	Company-wide technical direction	Owns technology strategy and its connection to business strategy; represents engineering to the board and investors; splits between an org-leadership CTO and a more hands-on technical CTO depending on company stage	18+

Note: Team sizes above are typical ranges, not hard rules. They vary by company stage, engineering culture, and how much of a manager time goes to individual coaching versus process. A company with a strong staff-engineer IC track may run smaller manager spans; a company that pushes more coordination work onto managers may run larger ones.

How the Engineering Manager career path progresses

An engineering manager career path is about scope of organization, not scope of code: progression means going from running one team's day-to-day to managing other managers, then to owning a whole department's headcount, budget, and technical strategy. The hardest single jump is at Group Engineering Manager or Director, where direct reports become other managers instead of individual engineers and success is judged by the org built, not by what gets personally unblocked.

1

Run one team

As an Engineering Manager, the scope is one team of 4 to 8 engineers: running 1:1s, performance reviews, and hiring, and owning delivery for a defined product area, usually as a former senior or staff engineer still reading code.
2

Handle harder problems at similar scope

As a Senior Engineering Manager, the team gets larger or more complex, and the job leans into tougher performance and org design problems, plus more input into hiring plans and roadmap tradeoffs.
3

Become a manager of managers

As a Group Engineering Manager, direct reports become EM1/EM2s instead of individual engineers. The job shifts from unblocking individuals to unblocking managers and resolving cross-team conflict, and it owns a multi-quarter roadmap across those teams.
4

Own a department

Director of Engineering owns headcount planning, budget, and org structure for a full department, and sets technical and delivery strategy across multiple product areas.
5

Own the engineering organization

VP of Engineering owns engineering strategy, org design, and delivery for the whole company, sitting on the executive team and balancing technical investment against business priorities.
6

Own technology strategy

CTO owns technology strategy and its connection to business strategy, and represents engineering to the board and investors.

Note: CTO splits in practice between a largely org-leadership role and a more hands-on technical role depending on company stage and founder background, but both are reached through this same management track. Moving from IC into the first Engineering Manager role is the one discontinuous step: most companies expect someone already doing manager-shaped work, like mentoring or leading a project across several engineers, before making it official.

Skills and competencies by level

Each level below lists the hard skills (tools, techniques, deliverables) and soft skills (judgment, communication, stakeholder handling) that typically distinguish it.

New manager (Engineering Manager)

Hard skills

1:1 cadence running. Runs a consistent 1:1 that surfaces a report's real blockers, not just status updates.
Performance review writing. Writes a review grounded in specific examples instead of vague impressions.
Sprint delivery ownership. Keeps a team's delivery on track for a defined product area.
Hiring loop participation. Runs a structured interview and gives a decision-useful hiring recommendation.

Soft skills

Code-to-people shift. Lets go of being the one who writes the code, without disengaging from the team's technical work.
Direct feedback delivery. Tells a report something isn't working clearly enough that they can actually change it.
Individual unblocking. Notices when someone is stuck and removes the blocker before it costs a sprint.
New-manager humility. Asks a peer manager for help instead of pretending to already know how to handle a hard situation.

Growing scope (Senior Engineering Manager)

Hard skills

Org design input. Shapes how a larger team should be structured as it grows, not just staffs the current plan.
Roadmap tradeoff ownership. Decides what a team does not build this quarter, and defends that call.
Performance plan design. Builds a real improvement plan for underperformance instead of documenting toward an exit.
Cross-team dependency management. Coordinates delivery when a team's work depends on another team's timeline.

Soft skills

Peer manager mentoring. Helps a first-time manager work through a hard people problem without taking it over.
Difficult conversation range. Handles a harder class of performance and conflict issue than a first-time manager typically sees.
Upward influence. Changes a roadmap decision by making the case to leadership, not just accepting it.
Team morale reading. Notices a team's energy shifting before it shows up in delivery metrics.

Manager of managers (Group EM, Director)

Hard skills

Manager coaching. Develops another manager's judgment instead of solving their team's problem for them.
Multi-quarter roadmap ownership. Sets a roadmap spanning several teams and quarters, not one team's current sprint.
Headcount and budget planning. Builds the hiring plan and budget case for a department.
Cross-team conflict resolution. Resolves a dispute between two managers whose teams disagree on ownership or priority.

Soft skills

Indirect visibility judgment. Reads a team's health through a manager's report instead of direct daily contact.
Manager calibration. Compares managers' performance ratings fairly against a consistent bar, not personal rapport.
Org-level trust building. Earns credibility with managers who used to be peers before the promotion.
Strategic patience. Lets a manager work through a problem their own way even when a faster fix is obvious.

Executive (VP of Engineering, CTO)

Hard skills

Org strategy setting. Decides how the entire engineering org should be structured and staffed against business priorities.
Technology-business alignment. Ties technical investment decisions directly to what the business needs to win.
Board-level reporting. Presents engineering's plan and risk in terms a board or investor can act on.
Executive team representation. Speaks for engineering credibly in company-level strategic decisions.

Soft skills

Executive peer influence. Shapes company strategy as a peer to other functional leaders, not just an engineering voice in the room.
Company-wide accountability. Owns engineering outcomes at the board level, including delivering hard news clearly.
Org-wide vision setting. Sets a direction the entire engineering org can actually rally around.
Talent bar setting. Defines what strong engineering leadership looks like for every manager below them.

Common questions

Frequently asked questions

How do you know if you should move from IC to engineering management?

What changes at the manager-of-managers level?

What separates promotion between manager levels?

How does this page relate to the general engineering career ladder?

Build your Engineering Manager career framework in Harmny

Turn this career ladder into a live system — employees see their gap to the next level, and development goals connect directly to the framework.

Start free See competency frameworks →

Related career ladders

IT Support career ladder QA Engineer career ladder Security Engineer career ladder Solutions Architect career ladder Solutions Engineer (Sales Engineer) career ladder Technical Writer career ladder

All career ladders → Career progression framework guide Competency matrix template Career pathing software