VP Engineering

The VP of Engineering (VP-E) is the senior executive responsible for engineering organization leadership, team management, delivery operations, and engineering culture. Sometimes called Head of Engineering, Director of Engineering, or Engineering Manager at smaller scale. The VP-E owns performance management, hiring and onboarding for engineering roles, and ensuring the engineering team delivers product effectively against business requirements. The role typically becomes necessary when the engineering team grows past 8-15 engineers and a single technical leader (often the founder CTO) can no longer effectively manage all engineering people-management responsibilities while also doing technical leadership work. It is the operational counterpart to the more-strategic CTO role and one of the most-consequential executive hires a scaling startup makes.

The core responsibilities of a VP Engineering:

People management and leadership:

• Direct management of engineering managers (or engineers directly at smaller scale).
• Career development for engineers across all levels.
• Performance management (reviews, promotions, PIPs, terminations).
• Hiring and onboarding for engineering roles (often partnering with CTO on senior hires).
• Engineering compensation philosophy and band management.

Delivery operations:

• Engineering processes (planning, sprints, code review, deployment, on-call, incident response).
• Cross-team coordination (product/engineering/design rituals).
• Delivery metrics (velocity, quality, predictability).
• Tooling and infrastructure for engineering productivity.

Engineering culture:

• Technical-quality bar (what does "good code" mean at this company?).
• Engineering values and norms.
• Knowledge sharing, documentation practices, learning culture.
• Inclusion and equity in the engineering organization.

Cross-functional leadership:

• Partnership with product, design, sales, customer success on what gets built and when.
• Roadmap planning and resource allocation.
• Business-context translation for engineering team.

The CTO vs VP Engineering distinction at scale:

• CTO: technology strategy, architecture vision, technical positioning externally, build-vs-buy decisions, emerging-technology evaluation, partnership with CEO on strategic technical questions.
• VP Engineering: operational leadership of engineering org, people management, delivery operations, engineering culture, hiring and team scaling.
• At small companies: one person plays both roles (typically the founder CTO).
• At scale: they become distinct, sometimes peers reporting to CEO, sometimes VP-E reporting to CTO.

When to hire VP Engineering:

• Trigger #1: founder CTO no longer has bandwidth for both technical strategy AND people management. Typical at 8-15 engineers.
• Trigger #2: engineering team is missing predictable delivery, with no clear owner of that problem. The fix is dedicated delivery leadership.
• Trigger #3: company is hiring multiple engineering managers and needs a single accountability for managing them.

The VP Engineering hiring profile:

• 10+ years of engineering experience including 5+ years managing engineers.
• Has scaled engineering teams from current size to 2-3x larger.
• Strong people-management skills (not just senior IC who became a manager).
• Cultural fit with company's engineering culture.
• Can partner effectively with the founder CTO (if applicable) or other technical leaders.

The common failure modes:

• Hiring too early: VP-E for a 5-engineer team is overkill; manager-level person is better.
• Hiring too late: founder CTO burns out from managing 20+ engineers while also trying to do technical strategy.
• Hiring wrong profile: senior IC who's never managed teams at scale; experienced manager from much-larger company who can't operate in startup conditions.
• Unclear CTO/VP-E split: ambiguity about who owns what leads to org friction.

What founders get wrong: Hiring VP Engineering with unclear delineation from the founder CTO, leading to ambiguity, conflict, and operational friction. The right discipline: at hiring, explicitly define what the CTO owns vs what the VP-E owns. Strategy/architecture/external goes to CTO; operations/people/delivery goes to VP-E. High mutual trust is essential. Regular alignment sessions between CTO and VP-E maintain coordination. When the split is clean and trust is high, the combination is one of the most-leveraged executive structures available.

Related: CTO · Technical Cofounder · First Hire · Hiring Plan · CEO

FAQ

What does a VP of Engineering do?
The senior executive responsible for engineering organization leadership, team management, delivery operations, engineering culture, performance management, and hiring for engineering roles. Distinct from CTO (technology strategy) in that VP-E focuses on operational leadership and people management.

When should a startup hire a VP Engineering?
Typically when the engineering team grows past 8-15 engineers and the founder CTO can no longer effectively manage all engineering people-management responsibilities while also doing technical leadership. The trigger is often the CTO burning out or the engineering team missing predictable delivery.

What's the difference between CTO and VP Engineering?
CTO focuses on technology strategy, architecture, external technical representation, and partnership with CEO on technical questions. VP Engineering focuses on operational leadership of the engineering org, people management, delivery operations, and team scaling. At small companies, one person plays both roles; at scale, they become distinct.