The risk is not the vacancy. It is the next resignation.
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.
The risk is not the vacancy. It is the second and third resignations that follow if the team concludes nobody is steering.
If you have ten minutes before a hiring review, read only this.
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.
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 dedicated 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.
Managing the transition period.
Everything above assumes the search runs while the org keeps working. That does not happen automatically.
Where a specialist partner changes the outcome.
Leadership hires are where a wrong decision costs the most. Executive search is built to reach the passive candidates these roles need and to test fit before anyone reaches you.
Brief → The mandate is pressure-tested with the founder before any outreach.
Market map → The real market is mapped, not just the active one, and shared before candidates.
Assessment → Motivation, closing variables and fit are tested before you invest time in a candidate.
Fees → Executive search with milestone-based fees: 20% Search Activation Fee, 10% on offer acceptance, 70% after the hire completes 30 days.
Discuss a mandate →Real mandates, real numbers.
Four earlier offer-stage declines. Motivation was treated as something to investigate rather than assume, and tested before the client invested time in any candidate.
A Head of Engineering, two AI Engineers and a Product Analyst. Each role sat in a different talent market and needed a different read on what strong looked like.
Hiring a leader your next two years depend on?
If you are hiring a CTO, VP Engineering, product or design leader, we can map the market and test the brief before any commercial conversation.
A senior team member responds within one business day. No pitch deck, no obligation.