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

Four to six months end to end is normal, and the search itself is rarely the slow part. Finding and convincing candidates takes weeks; the interview process usually takes four to eight weeks because every stakeholder wants time with the finalist; and then the notice period starts. In India a senior leader commonly serves 60 to 90 days, so an offer signed in March frequently means a start in June. Searches we have run have closed faster — one head-of-engineering search that had been open nine months signed in five weeks — but the notice period is not compressible.

What does it cost to hire a VP of Engineering?

Two costs, and the second is larger. The recruiting fee is typically 25-35% of first-year compensation for retained executive search, 15-25% for contingency recruitment, and in India CIEL HR publicly indicates 30-40% for senior and executive work. 100Networks charges 8.33% of first-year salary, invoiced on the joining date. The bigger cost is the vacancy: an engineering organisation without a leader for six months compounds delivery slippage, attrition risk and deferred hiring decisions that no fee line captures.

Should I use retained or contingency search for a VP Engineering role?

Retained search buys dedicated attention and a consultant who will work the search whether or not it is easy, which matters for genuinely rare profiles and for board-level accountability. You pay in instalments regardless of outcome. Contingency and marketplace models cost less and carry no risk if nobody joins, but you are one of several priorities unless the model routes your role to named specialists. For a first VP Engineering hire at a Series A or B company, contingency or a specialist marketplace is usually proportionate. For a public-company or board-reporting role, retained still earns its fee.

Why do VP of Engineering searches take so long?

Three compounding reasons. The pool is small — people who have genuinely run an engineering organisation at your stage number in the hundreds, not thousands, in any given market. Almost none of them are applying for jobs; they are employed and being retained hard. And the bar moves: after meeting six candidates, most founders realise the role they wrote is not the role they need, and the brief changes underneath the search.

How do you run a confidential VP Engineering search?

The constraint is that the incumbent, the team and the market must not find out. That rules out posting the role, and it rules out any marketplace that broadcasts briefs to a large network. A confidential search should go to a small named subset of recruiters under NDA, with candidates told the company name only once they have signed one themselves. Ask any partner specifically how they route confidential mandates before you brief them; if the answer is vague, that is your answer.

What should a VP of Engineering interview process include?

Four things, and technical depth is only one. An architecture and technical judgment conversation with your strongest engineer. An organisational design exercise — how they would structure the team you actually have, not a hypothetical one. A cross-functional session with product and go-to-market, since most VP Engineering failures are interface failures rather than technical ones. And backchannel references from people who reported to them, not only people they reported to. Five rounds maximum, scheduled inside two weeks.

How to Hire a VP of Engineering (2026): Cost, Timeline and Why Searches Stall

A VP of Engineering search is not a harder version of hiring a senior engineer. It is a different problem with different failure modes, and the most common one is that the search runs for five months and then closes with an internal promotion nobody was happy about.

Here is what these searches actually cost, how long they take, and where they go wrong.

The pool is smaller than you think

For any given profile — someone who has run engineering at your stage, in roughly your domain, and would consider your company — the realistic pool in a single market is measured in hundreds. Not thousands.

Narrow it to people who have done it at the specific transition you are hiring for, and it gets smaller fast. Scaling a team from 15 to 60 is a different job from running a stable 200-person organisation, and the second person often fails at the first job.

Almost none of them are applying for jobs. Across our own placements, 72% of the people we hired were not applying anywhere when we found them, and that proportion goes up as seniority does. A VP-level person in a good seat is being retained hard, has equity vesting, and has not looked at a job board in years.

That has a direct consequence: a job post will not fill this role. Not because the post is bad, but because the people you want will never see it.

What it costs

Recruiting fee. Retained executive search typically runs 25–35% of first-year compensation, paid in instalments whether or not the search closes. Contingency runs 15–25%, paid only on a hire. In India, CIEL HR publicly indicates roughly 30–40% for senior and executive work. We charge 8.33% of first-year salary, invoiced on the joining date.

The vacancy cost, which is larger and never budgeted. An engineering organisation without a leader for six months does not simply pause. Decisions defer. Senior engineers who were ready for more leave for somewhere that has it. Delivery slips in ways that show up two quarters later. If you are costing a search, cost the six months of not having the person.

The timeline, honestly

Phase	Realistic
Brief and alignment	1–2 weeks
Search and approach	2–6 weeks
Interview process	4–8 weeks
Offer and negotiation	1–3 weeks
Notice period	30–90 days

Four to six months end to end is normal. The interview process is usually the most compressible part and the one people compress least — every stakeholder wants their hour, and a process with seven sequential conversations takes six weeks of calendar even when everyone is enthusiastic.

The notice period is not compressible. In India, 60 to 90 days is standard at this level. An offer signed in March means a start in June, and the risk window between signature and start is where searches die — counter-offers land during notice, not before it.

Where searches actually stall

The brief changes after candidate six. The most common failure. You write a brief for a scaling VP, meet six people, and realise you actually need someone who can rebuild the platform team. Every week before that realisation was spent searching for the wrong person. Spend two hours on the brief with whoever will make the final call — not a JD, a brief: what this person will own in twelve months, what a strong one looks like, what the deal-breakers are, and what you will say when they ask why they should leave a job they like.

Nobody owns the close. VP candidates have options and long notice periods. Someone has to stay close to them from acceptance to day one — flagging counter-offer risk, keeping the CEO warm on them, noticing when they go quiet. This is the single most neglected part of a leadership search and the one that wastes five months of work in a week.

The process signals chaos. A candidate at this level is evaluating you throughout. Rescheduled panels, contradictory answers about the role's scope, and a fourth round that appears from nowhere all tell them what working there will be like. Your process is your pitch.

The confidential case

Replacing someone who does not know they are being replaced changes the mechanics entirely.

You cannot post the role. You cannot brief a wide network. You cannot let candidates talk freely about where they are interviewing. And you probably cannot use a marketplace that broadcasts your brief to thousands of recruiters, because your team will hear about it.

What works: a small named subset of recruiters under NDA, candidates told the company name only after signing one themselves, and interviews off-site or after hours. Ask any recruiting partner specifically how confidential mandates are routed before you brief them. A vague answer is an answer.

Questions that separate real from plausible

At this level, most candidates interview well. These get past that:

"Describe the last time you had to remove someone senior. What did you do first?" — Everyone has a clean version. Ask for the messy one.
"Walk me through how you'd structure the team we have now." Not a hypothetical org — yours, with its actual gaps.
"What did you get wrong at your last company that you'd do differently?" A candidate with no real answer either has not operated at depth or is not being straight.
"Which of your reports has been promoted since they worked for you?" The most reliable proxy for whether they actually develop people.

And take backchannel references from people who reported to them. Upward references tell you they managed up well, which is not the job you are hiring for.

If the search is already stuck

If your VP Engineering role has been open more than three months, the problem is almost never the pipeline.

It is usually the brief, or it is reach. Either you have not decided what the role actually is — in which case more candidates will not help — or the people who fit are not applying anywhere and nobody is going out to get them. Both are fixable, and they are fixed differently.

We run engineering leadership searches across India, the US and Europe, including confidential backfills, on a success fee of 8.33% of first-year salary paid on the day the person joins. One recent head-of-engineering search that had been open nine months closed in five weeks: seven people approached off-market, none of whom had applied for a job anywhere.

If that sounds like your search, send us the role.