How to Hire CTOs

A founding CTO at pre-seed is really a senior engineer who codes 70% of the week and makes architecture calls the other 30%. By Series B the job has split into two very different roles: some companies still want a hands-on technical co-founder shipping product, others need a VP-Eng-plus-external-face who owns platform strategy, board reporting, and vendor and build-vs-buy calls. Most failed CTO searches happen because the board wrote a job description for one archetype and interviewed for the other.

At Series C+ the CTO mandate is almost entirely about scaling systems and scaling leaders: owning a multi-year architecture roadmap, running a VP Eng and a Head of Security underneath them, and representing engineering credibility to enterprise prospects and acquirers. Coding time drops toward zero. If your board still expects the CTO to review pull requests weekly at 200 engineers, you've mis-scoped the role and will churn through candidates in 18 months.

The single biggest calibration error we see is boards treating 'has been a CTO before' as a must-have when the real must-have is 'has scaled an org through the specific inflection point you're at now.' A CTO who took a company from 5 to 40 engineers is a different candidate than one who took 150 to 400. Write the scorecard around the transition, not the title.

Nice-to-haves that get over-weighted: FAANG pedigree, a computer science PhD, prior CTO title at a company nobody's heard of. Must-haves that get under-weighted: has personally made a wrong architecture bet and recovered from it, has hired and fired at least one VP Eng, can explain a security incident they owned end to end.

Sitting CTOs rarely apply to job posts. The pool splits into three groups: current VPs of Engineering at companies one stage ahead of yours who are ready for the exec seat, former startup CTOs whose company sold or shut down and are between things, and Staff/Principal engineers at scale-ups who've been quietly running architecture decisions but never had the title. That third group converts surprisingly well when the equity story is strong.

Adjacent titles worth sourcing directly: VP Engineering, Head of Platform, Chief Architect, and founding engineer at a company that later scaled past 100 people. Warm intros from your existing investors and current engineering leaders outperform outbound by a wide margin for this seniority, but outbound sourcing into the VP Eng pool at Series B/C peers is the highest-volume channel that actually converts.

CTO comp is driven almost entirely by stage and dilution appetite, not by candidate leverage alone. Boards that try to lowball equity to protect the cap table end up losing candidates to a competing offer with 2x the equity and lose 6–10 weeks restarting the search. Cash comp has become less of the differentiator than it was two years ago; equity percentage and vesting acceleration on acquisition are now the real negotiation points.

A retained CTO search typically runs 8–14 weeks from kickoff to signed offer when the scorecard is tight; it stretches past 20 weeks when the board keeps revising the mandate mid-search. The most common failure mode isn't sourcing, it's internal disagreement surfacing in week 6 about whether you actually want a builder or an operator. Resolve that before you write the first outbound message.

The second failure mode is a slow, multi-week reference and negotiation process that lets a strong candidate accept elsewhere. Compress your decision window to under a week once you're at final round, and have the equity conversation early rather than saving it for the offer stage.