VP of Engineering and CTO Recruitment

The Board asks who is going to run Engineering after the raise, and the room goes quiet. Not because nobody has thought about it, but because three people around the table mean three different things by the title.

That is where most Engineering Leadership searches start. It is also why so many of them stall six weeks in, with a shortlist nobody is excited about and a Founder quietly wondering whether they needed the hire at all.

Runtime places Engineering Leaders into VC-backed SaaS companies from our UK headquarters in Manchester and our US base in Tampa. Leadership hires are the ones Founders get wrong most expensively, so we run them differently to an individual contributor search: fewer names, far more context, and a long conversation about what the role actually is before anyone is approached.

VP of Engineering or CTO: not the same hire

A CTO owns technical direction. Architecture, build versus buy, the technical story you tell investors and enterprise buyers, and often the surface where engineering and product meet. In an early-stage company the CTO is frequently a founder, and the real question is not who to hire but what to build around them.

A VP of Engineering owns the machine that ships. Team structure, hiring, delivery cadence, on-call, performance, and the career ladders that stop your best engineers leaving in year two.

Plenty of companies advertise for one and need the other. If your architecture is settled and your problem is that features take four months, you need a VP of Engineering. If you are shipping fine but cannot answer a security questionnaire or explain your platform strategy to an enterprise buyer, the gap is technical direction, not delivery.

We make that call with you before the search opens, honestly, even when the answer is that you do not need the hire yet. If you want to work through it yourself first, our guide on how to tell if you need a VP of Engineering or a CTO walks through the questions we ask.

What an Engineering Leadership search actually involves

Leadership candidates are not looking. The good ones are two years into a job they are proud of and have no reason to take your call, which means a leadership search is a persuasion problem long before it is a screening problem.

So we start with the pitch, not the profile. What is genuinely interesting about your engineering problem. What the last two years of the roadmap look like. What autonomy the person will actually have, and where the Founder intends to keep their hands on the wheel. Where the equity sits and how it vests. Candidates at this level ask all of that in the first conversation, and a vague answer ends the process.

From there we map the market properly rather than search a database. For a VP of Engineering role at a Series B SaaS company that usually means fifty to eighty credible names, of whom perhaps fifteen are worth an approach and six are worth your time.

Why Leadership hires fail

The three failure modes we see most often have nothing to do with technical ability.

The first is a role that was never defined. The person arrives, discovers the Founder still runs architecture and the VP of Product still runs the roadmap, and leaves inside a year.

The second is hiring for the company you will be in three years rather than the one you are in now. A Leader who ran a hundred-engineer org at a public company is often miserable managing twelve people and writing job specs.

The third is interviewing for the wrong thing. Founders default to a deep technical interview because that is the conversation they enjoy. It tells you very little about whether someone can run a hiring process, hold a performance conversation, or say no to a customer commitment.

How we Work with You

We run Leadership hires through Exec Search, our Retained model, because these searches need genuine market mapping and a consistent story told to every candidate. For Companies building out a wider engineering team at the same time, we also run Container, RPO, Embedded and Contingent models, and they combine well: the Leadership search anchors the structure, the team hires follow it.

You get one point of contact throughout, a written market map rather than a list of CVs, and a shortlist that comes with the reasoning attached.

What the Numbers look like

Across our Engineering searches, Runtime averages 6 weeks from brief to placement, an 8:1 CV-to-hire ratio, 94% offer acceptance and 95% retention. Leadership searches sit at the longer end of that range, as they should. The ratios matter more than the speed here: a shortlist you actually want to meet is the whole point of a Retained search.

Where we Hire

Manchester is our UK headquarters and Tampa is our US base, so we run Engineering Leadership searches across the UK, the US and Europe. For SaaS companies opening a second Engineering site, that dual footprint matters. The first Leadership hire in a new region sets the hiring bar for everyone who follows, and getting it slightly wrong is expensive for years.

Frequently asked questions

What is the difference between a CTO and a VP of Engineering?

A CTO owns technical direction: architecture, build versus buy, technical strategy, and the technical narrative for investors and enterprise buyers. A VP of Engineering owns execution: team structure, hiring, delivery cadence, performance management and engineering process. In a small company one person often covers both, but as the team passes roughly thirty engineers the two jobs pull apart and need separate owners.

When should a Startup hire its first VP of Engineering?

Most VC-backed SaaS companies need one somewhere between twenty and forty engineers, or when the founding CTO is spending more time in one-to-ones and hiring loops than on technical direction. The trigger is usually organisational rather than headcount: delivery has become unpredictable, and nobody owns fixing it.

How long does it take to hire a VP of Engineering or CTO?

Runtime averages six weeks from brief to placement across engineering searches. Leadership searches typically run longer, because the market map is wider and senior candidates need several conversations before they engage. Expect eight to twelve weeks end to end for a retained engineering leadership search, plus notice periods that are often three months at this level.

Should we use an Executive Search firm or hire through our network?

Hire through your network if you already know the person and they are available. That is the fastest and cheapest route and there is no reason to complicate it. Use a retained search when you need to see the whole market, when the role is genuinely hard to define, or when discretion matters because the incumbent is still in post. The value is the market map and the calibration, not access to CVs.

How do you assess an Engineering Leader without being technical yourself?

You do not need to assess raw technical depth alone. Bring an engineer you trust into one session for that, and spend your own time on judgement: ask the candidate to walk through a delivery failure they owned, a performance conversation they got wrong, and how they decided what not to build. The answers separate people who have genuinely led from people who have sat near leadership.

Do you work with pre-Series A companies?

Yes. At pre-Series A the honest answer is often that you need a strong founding engineer or a fractional technical leader rather than a full-time VP of Engineering, and we will say so. When a first leadership hire is the right call at that stage, we run it as a focused search rather than a full retained process.