A first VP of Engineering changes how the company builds. The hire is expensive, slow to reverse, and easy to get wrong by optimizing for prestige instead of fit. This guide covers when to hire, what the role is and is not, the profile that tends to work at Series A and B, where candidates come from, and how to run the process.
Correction: An earlier version of this article included compensation ranges, time-to-hire figures, and failure-rate statistics presented as market data. There is no verified dataset behind those figures and they have been removed. This version is a process guide, not a benchmark.
When to hire
The trigger is management surface, not funding stage. Ask three questions:
- Is the founder or CTO spending most of their week on people management, hiring, and delivery coordination instead of product and technical direction?
- Are there enough engineers that a second layer of management is a real job rather than a title?
- Do you have a clear picture of what the engineering organization needs to look like in 18 months?
If the answer to the first two is yes and the third is no, write the 18-month plan first. A VP hired without one inherits a vague mandate and is judged against it later.
Hiring too early creates a manager without a team. Hiring too late means the founder has been doing the job badly for a year and the new VP inherits process debt.
What the role is
The VP of Engineering is an operator. The responsibilities that define the role:
- Hiring: owns the engineering recruiting funnel end to end.
- Performance management: sets up reviews, calibrates levels and pay, manages out underperformers.
- Delivery: the team ships against commitments.
- Cross-functional partnership: roadmap negotiation with product, design, and GTM.
- Organization design: team structure as headcount grows.
Architecture and technical direction usually stay with the CTO or a principal engineer. Write down the scope split before you source a single candidate. Ambiguity here is the most common reason a first VP fails inside a year. See combined product and engineering leader and hands-on engineering leader role mandate for adjacent scope decisions.
Compensation
Set the range before the search from your own comparables: what similar-stage companies in your market have offered for the role, what your existing leadership earns, and what your option pool can support. Label the sources. See set startup hiring budget from comparable roles.
Candidates leaving public companies will weigh unvested equity they forfeit. Decide in advance whether a signing bonus is on the table and under what conditions.
The profile that fits
The best predictor is stage-relevant experience: has the candidate led an engineering organization through the phase you are about to enter?
Profiles that tend to work:
- A director or VP who scaled a team through your next size band at a comparable-stage company.
- An engineering manager at a strong company who has been operating at VP scope informally and can show it.
- A founding or early engineer who grew into leading the team through a later stage.
Profiles that tend to struggle:
- Senior leaders from very large companies with no startup tenure and no recent hands-on proximity.
- Leaders whose last organization was many times larger than yours and who are downshifting.
- Managers of a single team with no organization design experience.
The downshift trap is the most common failure: someone who managed hundreds cannot always manage twenty, because the job at twenty is closer to the work. Test for it. See assess big company engineer startup fit and engineering leader current technical judgment.
Where candidates come from
| Source | What it produces | How to use it |
|---|---|---|
| Investor introductions | High-context candidates from portfolio and network | First ask, with named target profiles |
| Referral network | Introductions from operators who have worked with the candidate | Run in parallel from the start |
| Retained search | Systematic market mapping with a dedicated researcher | When the role is narrow enough to justify a retainer |
| Personal network | Highest trust when it exists | Founder-led outreach, not delegated |
| Cold outbound | Low reply rates at this level | Supplement only |
Run investor introductions and a referral channel in parallel from day one. Investor networks are high-signal and run out quickly; a referral network extends reach to operators you do not know. Refery introduces engineering leaders referred by founders, operators, and investors, screened for the role, at a fee agreed before the search starts.
The interview loop
Five to six conversations, scheduled tightly, with a clear owner for each signal:
- Founder or CEO: fit, ambition, how they think about the company's next phase.
- CTO: scope alignment and technical depth; this is where the scope split gets tested.
- People case: a real personnel situation from your company, worked through together.
- Cross-functional panel: product and design leads on roadmap negotiation and delivery.
- Team conversations: informal one-to-ones with two or three engineers, candidate-led.
- References: founder-led, see below.
Give each stage a rubric before the loop starts. See build an anchored interview scorecard and interview an engineering manager of managers.
References
References are the highest-leverage step for a leadership hire and the most often rushed. Talk to:
- the candidate's last two managers;
- several direct reports at different levels;
- one cross-functional peer;
- if possible, someone they managed out.
Ask for disconfirming evidence: what did not improve under them, which hire did not work, what they would do differently. Reference calls that only confirm what you hope are not reference calls. See structured reference checks for startup hiring.
Closing
A VP offer should arrive with the decisions already made: base, equity, bonus structure, and a one-page note from the founder on the first 90 days. Offer the candidate a reference call on you and the CTO; it signals seriousness and tells you something about how they evaluate. See startup offer decision brief.
The first 90 days
Write the plan with the candidate before they sign:
- Days 1 to 30: meet every engineer, document how the team actually works.
- Days 31 to 60: identify the two most important hires and one process change.
- Days 61 to 90: ship one visible improvement and present the 18-month organization plan.
See turn interview evidence into an onboarding plan.
The mistake to avoid
Founders hire VPs of Engineering on prestige. The candidate who scaled a famous company from very large to enormous is not, by that fact, the right person to take your team from small to medium. The right candidate has done your exact next phase.
Share your role with Refery to agree the scope and fee for an engineering leadership search.