The VP of Engineering search that nearly killed a company started with the best intentions. The CEO, a technical founder, wanted someone to "own engineering" so he could focus on product and fundraising. He hired a recruiter, ran a fast process, and brought in a VP with a great resume from a big-name company.
Eighteen months later, the VP was gone. Half the engineering team had quit. Technical debt had spiraled. The company was six months behind their roadmap and struggling to recover.
The mistake wasn't hiring a VP—it was hiring the wrong VP, through the wrong process, for the wrong reasons.
After leading over 45 VP-level engineering searches at SmithSpektrum, I've learned that this hire requires more rigor, more time, and more precision than any other in the company. Here's the playbook that actually works[^1].
Before You Search: Is This the Right Hire?
Not every company needs a VP of Engineering. This role makes sense when your engineering team has 15+ engineers and will grow significantly. When you have or will soon have multiple engineering managers. When the CEO/CTO can no longer give engineering sufficient attention. When you need executive-level representation for engineering in leadership discussions.
This role doesn't make sense when you have fewer than 10 engineers (hire a Director instead). When the founder/CTO still wants to run engineering day-to-day. When you need a player-coach who codes 50%+ of the time. When budget constraints mean you can't pay market rate.
The worst outcome is hiring a VP before you need one. VPs who join too early get frustrated by the lack of scope, create unnecessary process, and often leave within a year—taking organizational knowledge with them.
Defining the Role
VP of Engineering means different things at different companies. Before searching, define exactly what this person will own.
| Dimension | Typical VP Scope | Questions to Answer |
|---|---|---|
| Organization | All engineering | Which teams? All ICs or shared with CTO? |
| Strategy | Technical roadmap execution | Who sets strategy—VP or CTO? |
| Hiring | All engineering hiring | Final decision authority? Budget authority? |
| Architecture | Technical direction | Shared with CTO/architects, or VP owns? |
| External | Engineering reputation | Conferences, blog, recruiting brand? |
| Executive | C-suite participation | Board reporting? P&L responsibility? |
The most common source of VP failure is misaligned expectations. The VP expects strategic authority; the CEO expects execution. Or the VP expects to own architecture; the CTO expects to retain it. Document these boundaries before you write the job description.
The Search Process
A VP search typically takes 14-24 weeks from kickoff to accepted offer. Rushing this timeline increases failure risk significantly.
| Phase | Duration | Key Activities |
|---|---|---|
| Definition | 2-3 weeks | Role scope, requirements, compensation, process design |
| Sourcing | 6-10 weeks | Search, outreach, initial conversations |
| Evaluation | 4-6 weeks | Deep interviews, references, final candidates |
| Closing | 2-5 weeks | Offer, negotiation, acceptance, notice period |
Search Partners vs. Self-Sourcing
For VP-level searches, you have three options:
Retained executive search firm: They dedicate resources to your search exclusively. Typical fee is 30-35% of first-year cash compensation. Best for: first VP hire, confidential searches, time-constrained founders.
Contingency recruiter: They source candidates in parallel with other firms. Fee is 20-25% of first-year compensation, paid only on hire. Best for: cost-conscious companies with some internal recruiting capability.
Self-sourcing: You do it yourself with internal recruiting and founder networks. Cost is time, not money. Best for: strong founder networks, second/third VP hire, plenty of time.
My recommendation: use a retained search firm for your first VP hire if you can afford it. The cost is high but the expertise is invaluable. VPs who fail cost far more than the search fee you save.
If self-sourcing, allocate 8-12 hours per week of founder time to the search. Less than this, and you'll never build momentum.
Sourcing Strategies
The best VP candidates aren't looking. Your job is to find them anyway.
| Source | Quality | Volume | Notes |
|---|---|---|---|
| Your direct network | Highest | Very low | Personal asks to people you know |
| Board/investor network | Very high | Low | VCs see hundreds of candidates |
| Engineering leader referrals | High | Low-medium | Your current team's extended network |
| LinkedIn outreach | Medium | Medium | Requires compelling, personalized messages |
| Executive communities | Medium | Low | Slack groups, YPO, CTO networks |
| Inbound applications | Low | High | Rarely produces VP-quality candidates |
The CEO should personally reach out to top candidates. A message from the CEO signals seriousness and importance that a recruiter email can't match. For your top 20 candidates, send personalized outreach that demonstrates you've researched their background.
Evaluating Candidates
VP interviews require more depth and more perspectives than any other role. Plan for 10-15 hours of evaluation per finalist.
The Interview Structure
| Interview | Duration | Interviewer(s) | Focus |
|---|---|---|---|
| CEO screen | 60 min | CEO | Fit, vision alignment, initial chemistry |
| Deep dive #1 | 90 min | CEO + Board member | Leadership, strategy, experience |
| Technical credibility | 60 min | CTO or Staff+ engineer | Technical depth, architecture thinking |
| Organization building | 60 min | Current EM or Director | People management, team development |
| Cross-functional | 60 min | VP Product + other exec | Partnership, communication |
| Team panel | 45 min | Future reports (2-3 people) | Culture fit, working style |
| Final executive | 45 min | Board member or CEO | Decision maker conversation |
The CEO should interview every serious VP candidate at least twice—once early to assess fit and once late to close. Chemistry matters at this level.
The Questions That Reveal Truth
On organizational building: "Walk me through how you built your current organization. What structure did you inherit, what did you change, and why?"
This reveals whether they've actually built organizations or just managed existing ones. Push for specifics: timelines, rationale for reorgs, what worked and didn't.
On technical credibility: "Describe a significant architectural decision your team made recently. What was your role in that decision?"
VPs don't need to be the best engineer, but they need to earn engineers' respect. Listen for whether they can engage substantively or defer entirely.
On executive partnership: "Tell me about a significant disagreement with your CEO or a peer executive. How did you handle it?"
VPs who've never had executive conflict either haven't been in hard enough roles or are conflict-avoidant—both concerning.
On failure: "What's the biggest mistake you've made as an engineering leader, and what did you learn?"
Self-awareness matters enormously at this level. VPs who can't articulate meaningful failures lack introspection.
On talent: "Who are the best three engineering leaders you've developed? Where are they now?"
Great VPs develop great leaders. If they can't name specific people who've grown under them, they're not developing talent.
Reference Checks
VP references require more depth than standard checks. Call at least six references: two peers, two direct reports, and two supervisors. Ask explicitly about weaknesses, not just strengths.
Questions that reveal truth:
"Would you work for/with this person again? Why or why not?" Hesitation on this question is the most important signal.
"What type of organization is this person best suited for?" Helps you understand fit beyond generic praise.
"What would they need to succeed? What support, context, or guardrails?" Reveals realistic expectations.
"What's one thing they could improve?" Reluctance to answer suggests either the reference is too positive or doesn't know the candidate well.
Back-channel references—people you find who've worked with the candidate but weren't provided as references—are often more revealing than formal references. Use LinkedIn to find connections.
Compensation
VP Engineering compensation in 2026 varies dramatically by company stage and location. Here are current market ranges for the US:
| Market/Stage | Base Salary | Equity (Annual Value) | Total Comp Range |
|---|---|---|---|
| Series A (SF/NYC) | $280K-350K | $200K-500K | $480K-850K |
| Series B (SF/NYC) | $300K-380K | $250K-600K | $550K-980K |
| Series C+ (SF/NYC) | $320K-420K | $300K-700K | $620K-1.12M |
| Growth/Pre-IPO | $350K-450K | $400K-1M+ | $750K-1.5M+ |
| Other major metros | 75-85% of SF/NYC | Similar ratios | Adjusted accordingly |
Equity structures vary by stage:
| Company Stage | Typical Equity Grant |
|---|---|
| Series A | 0.5-1.5% (options) |
| Series B | 0.25-0.75% |
| Series C+ | 0.1-0.4% |
| Pre-IPO | $300K-800K RSUs annually |
Signing bonuses of $50K-150K are common for VP hires, particularly when they're leaving unvested equity at their current company.
The Negotiation
VPs negotiate harder than other levels—it's part of demonstrating their executive capability. Expect pushback on base, equity, title, scope, and reporting structure.
What's typically negotiable: equity (20-40% movement common), signing bonus (highly flexible), start date (very flexible), title nuances.
What's rarely negotiable: base salary (5-10% max movement), reporting structure (predetermined), scope (predetermined).
When negotiating, understand their current compensation fully—base, bonus, unvested equity. Their walk-away number is usually driven by what they'd leave behind.
Closing the Candidate
VP candidates have options. Closing requires a concerted effort from the CEO and, often, board members.
The Sell
Tailor your pitch to what each candidate values:
| Candidate Motivation | Your Pitch |
|---|---|
| Impact | "You'll own engineering for [specific scope] affecting [business outcomes]" |
| Growth | "This role will grow to [future scope] as we scale to [stage]" |
| Mission | "We're solving [meaningful problem] for [sympathetic users]" |
| Team | "You'll work with [impressive team], including [notable people]" |
| Financial | "The equity upside is [realistic scenario] given [company trajectory]" |
The CEO should make the final pitch personally. At VP level, candidates are joining the CEO as much as the company.
Common Objections
"The scope is smaller than what I'm doing now." Counter with growth trajectory and impact per person. Smaller teams can mean more ownership and less bureaucracy.
"I'm concerned about runway/stability." Share metrics transparently: runway, growth rate, customer retention. Offer to connect them with investors for independent validation.
"The equity feels light." If you can't move on equity, address it with signing bonus, accelerated vesting, or an early refresh clause.
"I need to talk to my spouse/think about it." Normal and healthy. Give space but maintain contact. Offer to answer their partner's questions directly if helpful.
The First 90 Days
How you onboard your VP determines whether they succeed or become another failed executive hire.
Day 1-30: Learning
The VP should meet everyone—not just their direct reports, but product, sales, customer success, and founders. They should understand current state before proposing changes. They should identify quick wins that build credibility without requiring organizational change.
Document their 30-day goals explicitly. What should they know, who should they have met, what should they understand?
Day 31-60: Assessing
By week 6, they should have formed an opinion on organizational structure, talent, and technical direction. They should share this assessment with the CEO—but not act on it yet. They should identify their first significant initiative.
Day 61-90: Acting
First significant decisions should come in month 3—not before. This might be a reorganization, a key hire, a process change, or a technical direction shift. By day 90, they should have demonstrated visible impact.
Success signals at day 90: engineers trust and respect them (ask directly in skip-levels). They've delivered at least one meaningful improvement. They've identified the real problems, not just surface issues. They've built an effective partnership with product leadership.
Failure signals at day 90: engineers are confused about their role. They've made no meaningful decisions. They're still "learning" without forming perspectives. Conflicts with CEO or other executives are emerging.
The company that nearly died from their VP hire eventually recovered. They ran a rigorous search the second time: clear role definition, thorough evaluation, proper references. The new VP has been there three years now. Engineering is their competitive advantage.
Getting this hire wrong is expensive. Getting it right changes everything.
References
[^1]: SmithSpektrum VP Engineering search data, 45+ placements analyzed, 2017-2026. [^2]: Compensation data from Levels.fyi, Glassdoor, and SmithSpektrum client data, 2025-2026. [^3]: First Round Review, "How to Hire a VP of Engineering," 2024. [^4]: Larson, Will. "An Elegant Puzzle: Systems of Engineering Management," 2019.
Running a VP Engineering search? Contact SmithSpektrum for executive search support and assessment expertise.
Author: Irvan Smith, Founder & Managing Director at SmithSpektrum