VP of Engineering Job Description Template - 2026 Guide

Most companies get this hire wrong before they write the posting, because they decide on a title before deciding what the company needs. A VP of Engineering runs the organization: who's on which team, how work ships, who gets promoted, and why the roadmap is three weeks late. That's different from setting technical direction, and conflating the two means hiring a strong architect into a role that needed an organizational operator, or the reverse. This is hiring and role-design guidance, not an org chart mandate; treat company size and funding stage as the real inputs. For general guidance on structuring any posting well, see our job description best practices guide.

If your team already has a strong technical visionary in the CTO seat and the roadmap still isn't shipping, that gap usually isn't technology. It's execution, and a VP of Engineering is the fix.

Last updated: September 2026

Key Highlights

• This is an organization-and-delivery role, not a technology-strategy role: it owns hiring, structure, process, velocity, and retention, while a CTO owns technology vision and the outward-facing technical voice.
• A founding CTO hiring the first VP Eng is usually admitting an execution problem, not a technology problem: the roadmap has outgrown what one person can both architect and manage.
• Headcount is a real signal, not a vanity metric: most companies need this role around 15 to 25 engineers, and a director layer beneath it once the org passes 80 to 100.
• The job is measured on outcomes, not activity: delivery predictability, retention, hiring throughput, reliability posture, and the platform-versus-feature balance.
• It's frequently filled by promoting a director who has never held the job before: that can work, but only if the company checks for skills the director role never required.
• No government wage survey tracks this title specifically: the closest federal anchor sits well below what a VP Eng earns at a funded technology company, and this guide explains why.

Why This Role Matters

Job postings routinely use "VP of Engineering" and "CTO" interchangeably, and that's the first thing to fix before writing either one. A CTO owns where technology is going: architecture bets, build-versus-buy calls, often the external technical voice, frequently as the founder who wrote the product's first version. A VP of Engineering owns how it gets built: structure, hiring, process, velocity, and whether the roadmap ships on a predictable cadence. One is a strategy job, the other an organization-and-delivery job, and most companies wrongly assume every scaling problem is the CTO's to fix. If the roadmap keeps slipping under a founding CTO doing double duty, adding a VP of Engineering is usually the fix; a second technical strategist just adds a person with no delivery accountability.

Org design data backs this up. Jellyfish's 2025 analysis of manager-to-engineer ratios across 445 companies found the average sits around one manager per five engineers, tightening from 1:7.5 early-stage to 1:4.6 later-stage, with departing engineers disproportionately likely to have had an above-average ratio, and engineers under managers carrying 10+ reports staying roughly four months short of baseline tenure. A VP Eng who lets spans drift unnoticed is quietly manufacturing the attrition problem they'll later explain.

The platform-versus-feature argument every VP of Engineering has with product carries measurable downside either way. Chainguard's 2026 Engineering Reality Report (1,200 engineers and leaders, surveyed August 2025) found engineers spend just 16 percent of their week on new features, with 79 percent naming maintenance a major drain; starve platform work too long and that ratio worsens. Google Cloud's 2025 DORA State of AI-assisted Software Development report (nearly 5,000 professionals) adds an AI-era wrinkle: 90 percent now use AI at work, but AI amplifies whatever system it's dropped into. A well-run org gets faster; a poorly run one gets the same problems, faster.

A short list of outcomes separates a VP of Engineering earning their seat from one who isn't.

A 12-person team rarely needs all four roles; it usually needs a CTO or a single strong Engineering Manager. By 200 engineers, it needs all four, with the VP of Engineering as the connective layer.

Primary Job Description Template

About the Role

We're hiring a VP of Engineering to own how [Company Name]'s engineering organization is structured, staffed, and run day to day. You'll take the direction set with the CTO or founding team and turn it into a predictable delivery cadence: the right teams, process, people, and a roadmap that ships on time. This is a people-and-systems role first; you'll spend more time on org design and hiring than writing production code.

You'll report to [the CEO / the CTO] and partner daily with product leadership on scope, with Directors of Engineering and EMs on execution, and with the CTO on turning strategy into a staffed roadmap. Depending on size, you may also own site reliability and DevOps directly.

The ideal candidate has run a comparable or larger org, has hired and let go of engineering managers, and can defend a numbers-backed answer on rebalancing a team shipping features while quietly accumulating technical debt.

Key Responsibilities

• Organization Design: Decide team boundaries, reporting lines, and manager spans as headcount changes.
• Hiring & Talent Pipeline: Own the hiring plan and funnel, from headcount planning through final offers.
• Delivery & Predictability: Set the planning cadence and own the gap between shipped and promised.
• Retention & Team Health: Track engagement and regretted attrition, and act before it shows in an exit interview.
• Platform vs. Feature Allocation: Own the recurring negotiation with product over infrastructure versus features.
• Incident & Reliability Posture: Set the standard for on-call and postmortems with a site reliability engineer or platform team, and agree where engineering on-call hands off to whoever owns detection, whether that is a security analyst or an outsourced provider.
• Process & Tooling: Choose and evolve process without letting it become its own bottleneck.
• Manager Development: Hire, coach, and evaluate managers; org health rarely exceeds its middle management.
• Cross-Functional Partnership: Represent capacity honestly with product, including technical program managers on cross-team work.
• Budget Ownership: Own headcount and tooling budget, trading more people against better infrastructure.

Requirements

Must-Have Qualifications:

• 8+ years of engineering experience, including 4+ years managing managers
• Experience scaling a team through a significant headcount inflection point
• Track record improving a measurable delivery or reliability metric
• Experience owning an engineering budget and headcount plan
• Comfort making organizational tradeoffs with incomplete information
• Track record hiring, developing, and when necessary, exiting engineering managers
• Ability to translate technical constraints for a non-technical stakeholder

Nice-to-Have Qualifications:

• Prior experience as a Director of Engineering before a VP-level scope
• Experience partnering with or reporting to a technical co-founder or CTO
• Background maturing an on-call and incident response program
• Familiarity with AI-assisted workflows and how they change capacity planning
• Experience in platform engineering or infrastructure-heavy environments

What We Offer

• Competitive Compensation: Base salary and equity aligned to company stage (see Compensation Guide below)
• Meaningful Equity: A grant sized for a leadership hire building a function, not an IC grant
• Comprehensive Benefits: Medical, dental, vision, retirement match, and flexible PTO
• Leadership Development: Budget for executive coaching and conferences
• Real Authority: Ownership of hiring, structure, and process decisions, not a title without the mandate
• Growth Path: A defined track toward CTO or a larger-scope VP or SVP role

Context Variations

Corporate Environment

At a large or public company, a VP of Engineering typically owns several hundred engineers through a layer of directors, measured on portfolio-level delivery rather than any single team's output. Expect a formal leveling framework and a cadence tied to company-wide OKRs. Progression runs Director to VP, then SVP of Engineering or CTO.

Startup Environment

At a startup, the VP of Engineering is often the first dedicated people-and-process leader the org has had, arriving after a founding CTO has managed by instinct for a year or two. Expect to build the hiring process from close to nothing while staying hands-on enough to unblock a stuck project. Equity is a meaningful share of comp, and the honeymoon is short: no delivery improvement within two quarters and confidence slips.

Remote or Hybrid Environment

A remote VP of Engineering can run planning and skip-levels effectively over video, and distributed teams often force a discipline around written specs that in-person teams skip. What's harder: catching a struggling newly promoted manager before it shows in delivery metrics, and building trust that gets an engineer to flag a problem early instead of quietly job-hunting. In-person time still matters most around offsites and a new director's first months.

Industry Considerations

The core job doesn't change much by industry. What changes is which constraint dominates the org design conversation.

Company stage still explains more variation than industry does.

Compensation Guide

How the Federal Data Maps to This Title

No government wage survey publishes a category called "VP of Engineering." The closest match is Computer and Information Systems Managers, which the U.S. Bureau of Labor Statistics reports at a median annual wage of $175,140 as of May 2025, across 685,800 jobs, projected to grow 16 percent from 2025 to 2035, much faster than average, with about 53,500 openings a year. Typical entry requires a bachelor's degree plus 5 years or more of related work experience.

That occupation code is a useful floor, and a wide one: it spans an IT manager running a help desk to a VP of Engineering running a 150-person org at a funded company. The median sits well below what an actual VP of Engineering earns at a venture-backed or public company, and that gap is the real story here. Use the BLS figure as a floor, not a target offer.

Market Compensation by Experience Level

The ranges below translate that federal floor into employer-set market planning bands by company stage, built around 2026 job postings and typical practice. They are starting points for budgeting, not a quote from any salary database.

Equity is a bigger share of this package than a base-only band suggests, especially early on; this guide skips specific equity percentages since they move too much by round and leverage. Price equity against your own cap table.

Metro Adjustment Guide

Location still moves these bands. Use the tiers below as directional multipliers, not fixed figures.

Experience Level Requirements Matrix

Headcount is a more reliable sizing signal: a 12-year veteran managing 20 engineers and one managing 200 hold the same title but different jobs.

Interview Questions

At this level, the technical questions test org design, delivery systems, and technical judgment, not whether the candidate can still write a for-loop.

Technical/Functional Questions

1. Org Design: "Structure a 40-person org from scratch." Look for: a rationale tied to product ownership, not a copied chart.
2. Manager Spans: "When does a manager have too many direct reports?" Look for: a specific number and a plan.
3. Delivery Predictability: "Your org kept missing committed dates. What changed?" Look for: a real diagnosis and a process fix, not "we tried harder."
4. Platform vs. Feature: "How do you split capacity between tech debt and features?" Look for: a framework they've defended to a skeptical product leader.
5. Incident Response: "Describe an incident program you built or improved." Look for: ownership of both the fix and the human side.
6. Hiring at Scale: "How do you keep hiring bar consistent across 5 loops instead of 1?" Look for: calibration mechanisms, not "I trust my managers."
7. Architecture Literacy: "A major architecture decision your team made that you didn't design." Look for: enough depth to catch a bad call without overclaiming.
8. AI-Era Capacity Planning: "How has AI-assisted development changed capacity planning?" Look for: a concrete answer, not "AI makes us faster."

Behavioral Questions

1. Rebuilding Trust: "You inherited a low-morale team. First 90 days?" Look for: diagnosis first, then specific action.
2. Difficult Tradeoffs: "Cutting scope to protect your team. How did you decide?" Look for: willingness to take the resulting pushback.
3. Managing Managers: "A manager who was struggling. How did you know, and what did you do?" Look for: real signals and a real intervention, up to a hard conversation.
4. Cross-Functional Conflict: "A serious disagreement with a product leader over scope. Resolution?" Look for: resolution by data, not seniority.
5. Scaling Through an Inflection Point: "Your org roughly doubled. What broke first?" Look for: awareness that growth breaks things predictably.
6. Owning a Miss: "A delivery commitment your org missed publicly. How did you communicate it?" Look for: direct ownership and a fix, not blame elsewhere.

Culture Fit Questions

1. Leadership Philosophy: "Balancing protecting your team from pressure with transparency." Look for: a real point of view, not a dodge.
2. Partnership Style: "Your ideal relationship with a CTO or technical co-founder." Look for: clarity on where authority starts and stops.
3. Process Philosophy: "How do you know a process has become overhead?" Look for: a habit of removing process, not just adding it.
4. Standards for Their Own Team: "From your last three reports, who would you hire first, and why?" Look for: specific people and reasons, signaling real talent development.

Hiring Tips

This role is more often filled by promoting an internal director than by an external search, and that can work since a strong director already knows the team. But the jobs select for different skills: a director executes a structure someone else designed, a VP Eng designs it. Before promoting from within, check for what the director role never required: building a hiring pipeline, negotiating a budget, or defending an unpopular org call. If the answer is no across the board, plan a real ramp period rather than assume the promotion alone builds those skills.

Quick Sourcing Guide

Red Flags to Avoid