Hiring your first VP of Engineering is a hinge moment. Done well, engineering velocity compounds and the founder gets time back for company-building. Done poorly, delivery slows, senior engineers leave, and the founder ends up re-hiring the role 12 months later at twice the cost.
Most founders hire a VPE either too early (before there is a real team to lead) or too late (after delivery has already collapsed).
Be precise about the role. These titles are not interchangeable.
CTO — technical strategy, architecture, external representation.
VP of Engineering — org design, delivery, hiring, process, culture.
Head of Engineering — often a hybrid, best when the team is 5–15.
Write the scorecard for the role you actually need, then hire against it.
Target Directors of Engineering at one-stage-ahead companies who are ready to level up.
Look for candidates who have scaled a team from 15 → 50, not 50 → 500 (unless you're there).
Reference-check engineers who reported to them as much as their peers and managers.
1. Founder / CTO screen — vision, technical depth. 2. Delivery walkthrough — walk through a project they shipped end-to-end, with numbers. 3. Org design exercise — given your current team, how would they restructure and why? 4. Hiring exercise — mock scorecard and interview for a Staff Engineer role. 5. Incident review — walk through the worst production incident they've owned. 6. Peer panel — meet Product, Design, GTM. 7. Reference deep-dives — at least 3 direct reports, 2 peers, 1 manager. 8. Founder close.
Signing bonus: useful for closing candidates leaving unvested equity.
Refresh: written into the offer with clear performance triggers.
Days 1–30: listen. Skip-level with every engineer. Read the last 6 months of retros. Attend every planning meeting.
Days 31–60: diagnose. Deliver a written memo covering org, delivery, quality, and culture.
Days 61–90: ship one visible operational improvement. Draft the 12-month org plan.
Monthly engineering business review — velocity, quality, hiring, attrition.
Quarterly org review — leveling, comp calibration, succession.
The founder's job is to give context and remove blockers, not to override engineering decisions. Do that once and you lose the VPE's authority forever.
This is the relationship most likely to fail. Set it up carefully:
Write a one-page RACI covering architecture, hiring, delivery, and vendor selection.
Address friction the moment you feel it. It does not resolve itself.
Give them explicit authority to change process, tooling, and org structure.
Back their unpopular decisions in public. Debate them in private.
A great VPE gives you back 20 hours a week and doubles engineering throughput within a year. A bad one costs you a year and your best engineers. Do the sourcing work, run the loop rigorously, and invest in the partnership every week after they join.
