Management Career Ladder: 5 Levels, New Manager to VP

Most career ladders are built around a function: an engineering ladder, a sales ladder, a design ladder. Management is different. Once someone starts managing people instead of doing individual work, the skills that matter, running 1:1s, giving feedback, planning across a team, developing people, look largely the same whether they manage engineers or account executives. That is what a management career ladder captures: a function-agnostic track from a person's first direct reports through running an entire organization.

This guide covers the 5 management levels from New Manager to VP, how team scope actually grows level by level, how this track relates to the individual-contributor ladder it branches from, and promotion criteria for the key transitions. For the broader framework a management ladder fits inside, see our career progression framework guide.

The 5 management levels, New Manager to VP

Below is a common 5-level structure for a people-management track. Team scope is described qualitatively: what actually changes about the work at each level, not a headcount range, since that varies too much by organization to be a reliable signal on its own.

Team scope above describes typical patterns at mid-size companies, not hard rules; actual titles and scope vary by company size and how flat or layered an organization's structure is.

Team-size and scope progression

1. 1

   One team, learning it

2. 2

   One team, owned

3. 3

   Several teams

4. 4

   A department

5. 5

   The organization

Team scope in a management ladder does not grow in even steps. It moves from owning nothing formally, to owning one team, to owning a slice of the organization that spans multiple teams, to owning the whole function.

A New Manager starts by learning to run a single team they did not design: existing people, existing work, existing rhythm, with a manager or HR nearby for the harder calls. A Manager owns that team fully: the 1:1s, the reviews, the hiring, the rituals, all without heavy oversight. The bigger jump comes next. Senior Manager is where scope actually starts crossing team boundaries, coaching other managers, planning across several teams at once, calibrating hiring bars beyond a single group, even though the title still sounds like "just one more manager level." Director consolidates that multi-team work into a formal department: structure, resourcing, and calibration decisions that used to happen team by team now happen once, for the whole group. VP extends the same logic to the organization: strategy, org design, and leadership pipeline decisions that shape every department underneath it, not just one.

How the management track relates to the IC track

The People Management ladder above is deliberately function-agnostic: the same five levels, and the same underlying competencies, apply whether the person leading a team came out of engineering, sales, support, or finance. That is different from a role-specific IC ladder, where scope and skills are tied to a particular craft.

The natural entry point into this track sits around the same seniority as a Staff or Senior individual contributor on a functional ladder: someone has demonstrated enough judgment and scope at the IC level to be trusted with a team, and chooses, or is invited, to manage people instead of continuing to grow their individual scope. For a worked example of exactly where that split happens in one function, see the engineering career ladder, which maps its own management track (Engineering Manager through VP of Engineering) alongside the IC track it branches from, and the engineering manager career ladder, which goes level by level through that specific path.

The same compensation-parity principle that applies to any dual-track ladder applies here too: a New Manager and the Staff or Senior-equivalent IC role they came from should sit in the same band. If management pays meaningfully more, people take the management path for the money rather than the fit, which tends to produce reluctant managers and does not serve the people they end up managing.

How this maps in Harmny

Harmny ships a People Management starter framework that mirrors this ladder directly. The template description is exactly what it sounds like: "Leadership track for anyone who manages people, regardless of function, from New Manager through VP."

It organizes competencies into three categories, Team Leadership, Strategic Thinking, and People Development, covering nine competencies in total, each with its own skill description written for every one of the five levels. A few of the competency names: "1:1s & Team Cadence," "Feedback & Difficult Conversations," "Org Design," "Coaching & Growth," and "Succession Planning."

Picking this template in Harmny materializes all five levels and all nine competencies at once, with the level-by-level skill descriptions already written, ready for a manager or HR admin to adjust rather than build from scratch. See competency frameworks for how these levels turn into ratings, gap views, and development plans employees see directly.

Promotion criteria by level transition

Each promotion decision requires evidence that the manager is already operating at the next level, not that they would be capable of it with time and support. Below are the criteria for the transitions where the shift in scope is largest.

M1 → M2 New Manager to Manager (the first solo review cycle)

• Runs a full review cycle for their team on their own, setting expectations and giving an honest assessment without needing HR or their own manager to walk them through it
• Delivers direct, timely feedback and can handle underperformance or conflict instead of letting a hard conversation slide
• Owns hiring for the team end to end, sourcing, raising the bar, and closing candidates, rather than running interviews someone else designed
• Has built team rituals (standups, retros, planning) that hold up without the manager personally driving every one of them

M2 → M3 Manager to Senior Manager (the coaches-other-managers shift)

• Has coached at least one other manager well enough that the other manager's own team improved, not just their original team
• Plans and sequences work across more than one team, managing dependencies between teams instead of only within one
• Scales hiring across several teams while protecting a consistent bar, rather than running a single team's hiring process
• Navigates the hardest conversations, demotions, terminations, sensitive conflicts, well enough to model that for other managers

M4 → M5 Director to VP (org-wide accountability)

• Has run a department successfully: structure, resourcing, and calibration decisions that held up across multiple teams
• Is ready to set strategy and allocate resources across the whole organization, not just defend one department's roadmap
• Shapes hiring philosophy and employer brand at the company level, and personally lands executive or strategic hires
• Takes ownership of organizational continuity, the leadership pipeline and succession map for the company, not one department's bench

For the plain-language breakdown of what changes at each level in any career ladder, see career ladder levels explained. If you are building this out for your own team, our career ladder and career levels glossary entries define the underlying concepts, and the career ladder library covers roles beyond people management. To turn any of this into skill criteria your managers can actually rate against, start from the free competency matrix template.

Frequently asked questions