Short answer: 8 to 15 years from your first EM role to a real VP seat, and you almost never skip the Director step in between. The path is longer than most people realize when they take their first EM promotion — and shorter than it looks on LinkedIn, where every EM-turned-VP seems to have made the jump in 5 years flat because they founded their own company.

The version that matters — getting a VP-of-Engineering title with an actual VP-scope job at a company someone else built — runs through a fairly predictable sequence. First-time EM to Senior EM. Senior EM to Director. Director to Senior Director. Senior Director to VP. Each step is a real one; each has a different skill set; each takes on average 2 to 4 years. Try to skip a step and you'll usually get stuck at the next one.

This piece maps the full path in the way we wish someone had explained it when we started tracking career ladders across our culture directory — not the LinkedIn version, the real one. Timeline, compensation at each rung, the skills that separate people who climb from those who plateau, and the honest reasons some of the best EMs never make VP (and often don't want to).

The Full Ladder, In Real Years

Every company’s titles differ, but the pattern is remarkably consistent across engineering-driven tech. In rough form:

4–6y
First EM → Senior EM
2–4y
Senior EM → Director
2–5y
Director → VP

Years 0–1 (First-time EM). You take your first management role. You still write some code. You’re running a team of 3–8 engineers. Almost everything is new: 1:1s, performance conversations, sprint planning as a manager instead of a lead, hiring loops as a hiring manager rather than an interviewer.

Years 1–4 (Established EM). You’re competent at the mechanics. Your team ships. Your engineers grow. You start earning the reputation of being “the manager people want to work for.” This is the phase most people underrate: doing the EM job well for three to four years is what earns you the shot at the next step.

Years 4–7 (Senior EM). You either take on a larger team (12–20 engineers), a more strategic team (platform, infra, an important product area), or a Tech Lead Manager who effectively runs a subteam beneath you. This is the point where you start doing pieces of Director work informally: cross-team coordination, occasional strategy, hiring for peer EMs.

Years 7–10 (Director). You now manage managers. Your reporting line is 3–8 EMs, and through them, 30–80 engineers. Your role shifts from executing a team’s work to owning a system of teams. See our full Director of Engineering career-path deep-dive for what that looks like day-to-day.

Years 9–13 (Senior Director / VP-in-waiting). Some companies use “Senior Director” as a formal rung; others just widen the Director scope. Either way, you now own multiple areas and often influence the overall engineering function’s strategy alongside a VP or CTO. This is where the VP audition happens — usually invisibly.

Years 12–15+ (VP of Engineering). You own the engineering function. The whole thing. Culture, hiring bar, technical strategy, delivery accountability — end to end. In an org of 100–500 engineers, you probably report to a CTO or CEO. In a smaller company, you may be the head of engineering.

The compressed version: At high-growth startups, especially early-stage AI labs, this whole ladder compresses. A talented EM who joins a 40-person startup can be effectively a VP by the time headcount hits 200 — not because they skipped steps, but because the steps happened much faster around them. This is the fastest path to the title, but it’s also the path where the “VP” label may not translate to a bigger company, where the same person would be a first-time Director.

What Actually Changes at Each Level

The clearest way to see the ladder is by what changes about the job at each step. The titles matter less than the shift in what you spend your time on.

EM: You run a team

Your unit of work is the sprint. You care about the team’s velocity, the quality of the code they ship, the health of your 1:1s, and the ratio of shipping to burnout. Your credibility is technical and tactical.

Senior EM: You run a bigger or more strategic team

Same unit of work, wider scope. You’re trusted with something that matters more — a payments team, a platform team, a launch-critical initiative. You start being invited to org-wide discussions.

Director: You run a system of teams

Your unit of work is the quarter. Weekly sprints happen at your reports’ layer, not yours. You care about org health, cross-team dependencies, delivery predictability, and whether your EMs are growing.

VP: You run the engineering function

Your unit of work is the year. You own culture, hiring bar, technical strategy, and how engineering fits into the company’s bets. Your credibility is executive: can the CEO trust you to make engineering a competitive advantage?

The transitions in-between are where careers stall. The Senior EM to Director jump is about scope. The Director to VP jump is about accountability — specifically, about being accountable for outcomes you can no longer personally guarantee.

The Compensation Ladder

Comp climbs faster than the title. A Director often earns 30–50% more than the Senior EM they were 18 months ago. A VP earns 30–80% more than the Director they were before that. The equity-to-base ratio also flips: EM comp is heavily base-driven, VP comp is heavily equity-driven, especially at private companies.

$260–$400K
Senior EM total comp (2026)
$400–$700K
Director total comp (2026)
$500K–$1M+
VP total comp (2026)

For VP of Engineering specifically in 2026, base salary typically sits between $250K and $450K, with total packages running from around $300K at a seed-stage startup to $700K–$900K+ at growth-stage and public companies. At frontier AI labs and top public tech (Anthropic, OpenAI, Google, Meta, Nvidia, Stripe), the ceiling is well into seven figures thanks to equity refresh grants that dwarf the base.

By company stage, the pattern looks roughly like this:

Two things matter more than the numbers themselves. First, VP comp is heavily equity-driven and equity is heavily company-driven — you’re not really negotiating your VP package, you’re negotiating your company. Second, the biggest predictor of realized comp isn’t the offer letter; it’s the eventual liquidity event. A VP who joined a growth-stage company two years before an IPO can outearn a VP at a mature public company by an order of magnitude — and just as often, the other way around.

The Step You Can't Skip: Director

The single most important thing to understand about the EM-to-VP path is that Director is not optional. Companies almost never promote or hire a first-time VP who has not previously done Director-level work.

The reasoning is straightforward. A VP is expected to own an engineering function — culture, hiring bar, technical strategy, delivery. To do that, you need to have already run multiple teams through other managers. That’s the Director job. Trying to hire a Senior EM straight into a VP seat means the company is betting they’ll figure out manager-of-managers work simultaneously with function-level accountability. Almost no one is good enough to pull that off, and companies have been burned enough times that they mostly stopped trying.

The Director step usually takes at least 2–3 years to do credibly. You need enough time on the role to have (a) shipped a substantial cross-team outcome, (b) grown at least one EM you hired or promoted yourself, and (c) survived at least one full performance-review cycle managing managers. Faster than that and it’s hard for a hiring committee to trust the pattern.

Two exceptions to the “can’t skip Director” rule:

  1. Founding a company. If you co-found a startup and become the CTO or VP of Engineering yourself, you skip the ladder by definition. You’re also skipping the compensation and stability of a real VP job; you’re trading it for equity.
  2. Small startup, informal titles. At a 15-person startup, the second engineering hire may get the “VP” label because someone has to. If the same person moved to a 400-engineer company, they’d be a first-time Director. The title inflated because scope inflated, not because the person skipped a step.

What Separates EMs Who Reach VP From Those Who Don't

Most strong EMs plateau. Not because they’re bad managers — they’re often great ones — but because the skills that get you promoted at the EM level are different from the skills that get you promoted at the Director level, and different again from what gets you the VP seat.

1. Executive communication

EMs write status updates. Directors write strategy memos. VPs write documents that a CEO can hand to a board without editing. If you cannot translate engineering trade-offs into business outcomes in one page, without technical jargon, you’re not ready to sit in the VP seat. This is the single most common gap we see in strong EMs who don’t make VP: they can execute but can’t communicate upward at the required altitude.

2. Strategic bets, not execution

Great EMs are handed problems and solve them. Great VPs choose which problems the whole engineering function should tackle. That’s a completely different skill: the ability to look at 20 possible investments and articulate why 3 of them matter more than the other 17. It requires business context, product taste, and a tolerance for being wrong in public.

3. Hiring your own bench

VPs don’t manage individual engineers. They manage Directors and Senior Directors. If you’ve never hired an EM externally, never promoted an EM into a Senior EM, never coached a Tech Lead into their first EM role — you don’t have the operating experience VP requires. The best predictor of VP-readiness is a track record of building the leadership layer beneath you.

4. Comfort with ambiguity

EMs live on weekly sprints. VPs live on quarterly and yearly bets that may not pay off for 18 months. If you get anxious when there’s no visible weekly progress, the VP role will burn you out. The best VPs we’ve interviewed describe learning to be genuinely comfortable with long feedback loops as one of the hardest transitions in their career.

5. A track record of picking direction, not just executing it

By the time you’re a serious VP candidate, you should have at least one large bet you can point to and say “this was my thesis, I convinced leadership, my team executed it, and it worked.” VPs are hired to make consequential calls. If your career reads as competent execution of other people’s ideas, you’ll get considered for Director-level jobs, not VP jobs.

Do You Have to Change Companies?

Often, yes. Internal promotions to VP stall because the seat is usually already filled and only opens on rare transitions (a VP leaving, a company reorg, a headcount doubling that justifies a second VP). Many of the VPs we’ve profiled built their careers by moving companies every three to four years, taking progressively larger roles at each step: Senior EM at a large company → Director at a medium one → VP at a smaller one, or a similar sequence.

The counter-pattern — internal promotion to VP — happens most reliably at fast-growing private companies (early-stage AI labs, well-funded Series B–C startups) where the scope is expanding faster than the company can hire external VPs. If you’re on a career-driven path to VP, joining a high-growth company one to two years before their engineering org doubles is one of the highest-leverage moves you can make. Just don’t confuse growth for guaranteed promotion — the same growth that creates the opportunity also attracts external candidates.

Where the VP Path Looks Different in 2026

The VP-of-Engineering role has evolved. A few specific shifts worth understanding:

At engineering-driven companies

Stripe, Databricks, Cloudflare

At companies with strong engineering-driven cultures, the VP role is highly technical — often a VP of Engineering is expected to hold their own in architecture reviews and stay close to the code, even if they don’t write it. Compensation is at the top of the market for public/private tech. Promotion criteria are more explicit than at most companies but the bar is genuinely high: you’re competing with peers who are unusually strong.

Explore engineering-driven companies →

At flat orgs

PostHog

At companies with deliberately flat hierarchies, the VP title often doesn’t exist. The closest equivalent is “Head of Engineering” and there may be only one of them. The scope is real; the impact is high; the title may not translate cleanly to your next company — a Head of Engineering at a 60-person flat org will be evaluated as a Director if they leave for a 500-engineer traditional org.

Explore flat-org companies →

At frontier AI labs

OpenAI

VPs at frontier AI labs run functions that didn’t exist five years ago — VP of Applied AI, VP of Model Deployment, VP of Safety Engineering. The technical scope is unusually deep and compensation is at the top of the market thanks to private-valuation step-ups. The trade-off: the work moves fast enough that org structures change every few months, and you may find your function has been reshaped around you between the offer letter and your first quarterly.

Read our Anthropic deep-dive →

The Honest Question: Do You Actually Want This?

A pattern that commonly emerges when engineering leaders reflect on this path: many great EMs would actually be worse VPs than they are EMs. Some recognize this about themselves. The ones who don’t tend to find out the hard way.

The VP role is a different job. It rewards a very specific temperament: comfortable with long feedback loops, energized by strategy and org-building, willing to trade weekly wins for yearly ones, tolerant of politics and executive dynamics, unfazed by being accountable for outcomes you can’t personally cause. Not everyone finds those things energizing. Many exceptional EMs realize somewhere around Senior EM or early Director that they were happier managing one great team than they are managing a system of teams, and choose to specialize sideways rather than up.

There is no shame in that. The IC ladder — up to Staff and Principal — pays comparably to the management ladder up through Senior Director. The Senior EM ceiling in a well-designed company is well above $400K. And in 2026, some of the most sought-after engineering hires are Senior EMs who’ve made the deliberate choice to stay at the team level. If you get to Senior EM and don’t want to keep climbing, that’s a legitimate career, not a failure.

A Realistic 12-Month Plan for the Next Step

Whether you’re a Senior EM trying to make Director, or a Director trying to make VP, the mechanics of “get promoted” are similar. Here’s the compressed version:

  1. Get explicit about what you’re trying to become. Have a direct conversation with your manager. “My goal in the next 12–18 months is to be considered for Director/VP. What’s the gap between where I am and that bar?” Their answer is your work plan.
  2. Manage a manager, formally. If you don’t already have an EM (or an EM-in-waiting) reporting to you, this is the single biggest gap to close.
  3. Own one cross-team outcome end-to-end. Not partial credit — primary accountability. This becomes your promo case study.
  4. Write a strategy memo your leadership circulates. Not a status update. A forward-looking document that reshapes what your VP thinks about. If you don’t know what you’d write, that’s data about your readiness.
  5. Hire externally at senior level. Own a senior IC or peer EM search, from sourcing through close. This is a Director-level skill; being able to do it is a VP-level requirement.
  6. Build your executive vocabulary. Read strategy memos from CEOs you respect. Read letters to shareholders. Watch how good VPs talk in engineering all-hands. Learn the register.
  7. Get feedback from someone senior to you outside your reporting line. Your VP is invested in your success; a peer VP at another company can tell you the truth about how you’d be evaluated in an external search.

The honest timeline: If you’re a mid-career EM reading this, the earliest realistic VP seat is 5–7 years away, and the median is closer to 8–10. That’s not discouraging — it’s clarifying. The people who make VP are the ones who took the runway seriously. The ones who tried to sprint the last mile in 18 months usually stalled at Director for another five years anyway.

Frequently Asked Questions About the EM-to-VP Path

How long does it take to go from Engineering Manager to VP?+
The typical timeline from first-time Engineering Manager to VP of Engineering is 8 to 15 years, split roughly as 4–6 years as an EM, 3–5 years as a Senior EM or Director, and then the jump to VP. At high-growth startups where scope expands quickly, the timeline can compress to 5–8 years. Very few people skip the Director step — companies almost universally require multi-team leadership experience before considering a VP hire.
How much does a VP of Engineering make in 2026?+
VP of Engineering base salary in 2026 typically sits between $250K and $450K. Total compensation ranges from around $300K at a seed-stage startup to $700K–$900K+ at growth-stage and public companies, and can reach seven figures at frontier AI labs and top public tech where equity refresh grants drive most of the package. Equity at private companies often runs 0.4–2.5% of fully diluted shares depending on stage.
What’s the difference between a Director of Engineering and a VP of Engineering?+
A Director owns delivery for a product area or technical domain — typically 30 to 80 engineers through 3 to 8 reporting managers. A VP owns the engineering function for a business unit or the entire company, typically 100 to 500+ engineers, and reports directly to a CTO or CEO. The VP is accountable for the whole engineering culture, hiring bar, and technical strategy, not just one slice of it.
Do I have to change companies to reach VP?+
Often, yes. Internal promotion paths to VP stall because the VP seat is usually already filled and only opens up on rare transitions. Many VPs build their careers by moving between companies every three to four years, taking progressively larger roles at each step. That said, high-growth companies expanding fast (early-stage startups, frontier AI labs) create VP seats internally more often than mature companies.
What skills separate EMs who reach VP from those who plateau?+
Three things: (1) executive communication — being able to translate engineering work into business outcomes for a CEO or board, (2) strategic bets — proving you can pick which problems the whole function should tackle, not just execute problems handed to you, and (3) scaling leadership — hiring and developing your own directors and senior EMs rather than being the best manager on the team. Many strong EMs plateau because they stay in execution mode too long.
Is the VP of Engineering role becoming obsolete?+
No, but its shape is changing. Some engineering-driven companies (PostHog, small AI labs) run flat orgs and use titles like “Head of Engineering” instead. Others have consolidated VP roles into Chief Engineering Officer or CTO+VP hybrid positions. The core work — owning the engineering function’s culture, hiring, and strategy — still exists. Only the title varies. Most companies over 200 engineers still have someone in a VP-equivalent role.

Browse Engineering Leadership Roles

See open EM, Director, Head of Engineering, and VP roles across our directory — all with culture context so you can find the right fit for the next rung.

Browse Leadership Roles → Explore Companies →