A VP Engineering resignation is not primarily a hiring event. It is a confidence event. The engineers reporting into that seat will decide within about two weeks whether this is a normal transition or the first sign that something is wrong, and their conclusion will be based almost entirely on what you do in the first seven days.
Most companies get the sequence backwards. They open the search immediately, because that feels like action, and leave the team to interpret the silence. Six weeks later they are running two problems instead of one: an empty seat and an attrition spiral. This playbook covers the first thirty days in order, and the order matters more than the speed.
Day 1 to 7: Stabilise Before You Recruit
Nothing in the first week is about the search. The entire week is about making sure the organisation underneath the departing leader is intact by the time you start one.
Tell the team before they hear it sideways
The single most damaging version of this event is engineers finding out from a LinkedIn update. Tell the direct reports first, in person or on a call, before any wider announcement. Tell them the same day you know. What you say matters less than the fact that they heard it from you.
Be straight about what you do not yet know. Saying we have not decided on the replacement approach yet, and I will tell you when we have is far stronger than an improvised answer you retract a fortnight later. Engineers are unusually good at detecting a manufactured narrative, and the credibility you lose here is difficult to recover.
Identify the real flight risks in 48 hours
Some of the team followed the leader, not the company. Those people are already updating their CVs. Work out who they are within two days, and talk to them individually before they reach a decision rather than after.
Do not open with a counter-offer. Open with a question: what would make staying interesting? Frequently the answer is scope, not money, and scope is something you can grant immediately while the seat is empty. A senior engineer given the architecture ownership they had been waiting for is more likely to stay than one handed a retention bonus with no change in their work. Companies with real succession planning for engineering leadership already know who these people are before the resignation lands.
Name an interim, even a weak one
An imperfect interim beats an unowned team. Ambiguity about who decides is what triggers the second resignation. Name someone, define exactly what they can decide alone and what escalates to you, and set an explicit end date so the interim does not quietly become the permanent answer by default.
Day 7 to 14: Define Who You Actually Need Now
The most common failure in these searches is replacing the person who left rather than hiring for the company you now are. The departing VP was hired against a set of conditions that has almost certainly changed.
Ask what the role has to be, not what it was
A VP hired at forty engineers to bring order to chaos is not necessarily the VP you need at a hundred and twenty. The first was a builder. The second is a scaler. These are different people and they rarely convert, which is why a Series B VP Engineering search looks nothing like a Series A one. Write down what the next twenty-four months demand and hire against that document.
| If the next 24 months are about | You need someone who has | Common mis-hire |
|---|---|---|
| Scaling a working org from 40 to 150 | Run a team through that exact size band before, twice ideally | A builder from a 20-person startup who will rebuild what already works |
| Rebuilding delivery credibility after slippage | Shipped under scrutiny and repaired a broken relationship with the business | A visionary architect who will redesign rather than deliver |
| A platform or architecture reset | Owned a migration end to end and lived with its consequences | A manager of managers who has not made a technical decision in five years |
| Holding steady through a funding gap | Operated under real constraint without losing the senior people | Someone from a well-funded environment who has only ever grown headcount |
Decide internal versus external honestly
There is usually an internal candidate, and the decision is rarely as close as it feels. Promote internally when the org is healthy and needs continuity, and when the person has already been doing a meaningful part of the job. Hire externally when the next phase requires experience nobody inside has, or when the team's problems are structural rather than personal.
The version that damages everyone is the unofficial audition: letting an internal candidate act up for months without telling them whether they are a real candidate, then hiring externally over their head. You lose the external hire's honeymoon and the internal person, usually within the quarter. Decide, then say so.
Write the successor profile down
Whatever you conclude, put it on paper before anyone is approached. A written profile covering scope, the first twelve months, the decision rights, the compensation reality, and the two or three things that would make a hire fail is what stops the brief drifting once shortlists start arriving. Where we run these mandates as retained executive search, this is the artefact the whole search is calibrated against.
Lost an engineering leader?
Send us the situation and the timeline. We will come back within one business day on whether to promote, hire, or bridge, and what the search realistically takes.
Discuss a mandate →Day 14 to 30: Launch the Search Properly
Only now does the search begin. By this point the team knows what is happening, the flight risks have been addressed, an interim owns decisions, and you know what you are hiring for.
Expect the timeline to be honest, not fast
A VP Engineering search at any real level of scrutiny runs eight to fourteen weeks to accepted offer, and another one to three months of notice period after that. Anyone promising a shortlist next week is showing you the active market. The strongest engineering leaders are employed, are not applying, and have to be approached directly with a proposition that is worth their attention.
Run it confidentially if the incumbent is still in seat
If the departing VP is working a notice period, the search is confidential by necessity. That constrains sourcing, changes how the role is described in outreach, and rules out anything resembling a job post. It is a confidential replacement search and should be scoped as one from the start.
Protect the offer before you make it
At this level the counter-offer is the default, not the exception. A candidate who is genuinely worth hiring is worth retaining, and their current employer knows it. Motivation work has to happen before the offer, not after it lands: what is actually driving the move, what would their employer have to do to keep them, and what is the honest answer to whether that is achievable.
Skipping that conversation is how searches restart at week ten with nothing to show. The offer is not the finish line; it is the point at which the other side starts competing.
Managing the Transition Period
Everything above assumes the search runs while the org keeps working. That does not happen automatically.
Use the notice period deliberately
A departing leader on good terms is a genuine asset for exactly one thing: documenting what only they know. Decision history, the reasoning behind architectural choices, which relationships are fragile. Get that written down rather than hoping it transfers by osmosis.
What they should not do is shape the successor profile or sit on interview panels. Their model of the role is the one that is ending, and their instinct will be to hire someone like themselves. That is precisely the bias you are trying to avoid.
Protect the interim from becoming the default
If the interim is doing well, the pressure to simply confirm them grows every week, and the search quietly loses urgency. Sometimes confirming them is right. But make that a decision with a date on it, taken deliberately, rather than something that happens because everyone got used to the arrangement.
Plan the onboarding before the offer is signed
The first ninety days decide whether this hire holds. A new engineering leader walking into a team that has been through a departure needs to know what they own, what is already broken, and who the real informal leaders are. Building the onboarding plan for a new engineering leader after they start wastes the only period where they have the licence to change things.
Need the search run confidentially?
If the incumbent is still in seat, the search has to be scoped for confidentiality from day one. Tell us the constraints and we will scope it properly.
Start with the brief →