Why You're Losing VP Candidates You Never Even Rejected
A hiring manager liked three VP finalists, then went quiet for two weeks. Here's what silence costs — and how to keep candidates engaged while you decide.
Howard, a hiring manager at Espera Health, interviewed four VP candidates over three weeks. He liked three of them. Then he went quiet.
Not because anything was wrong. He got busy. He took a long-planned vacation. And underneath both, if he’s honest, he genuinely didn’t know which of the three to move forward with.
Two weeks later, he resurfaced, ready to schedule final rounds.
By then we were scrambling. Two of his three finalists had gone quieter themselves — not rejecting anything, just slower to respond, clearly fielding other conversations. We spent those two weeks doing damage control: checking in, keeping them warm, racing to get Howard back in the room before one of them signed somewhere else. That race isn’t over. It’s the one we’re running right now.
Here’s the part that gets missed: nobody rejected anybody. There was no bad interview, no lowball offer, no red flag. Candidates don’t go cold because they found something better. They go cold because they stopped hearing anything at all, and something else showed up in the meantime.
Silence reads as disinterest, even when it isn’t.
A slow “no” still tells a candidate where they stand. A slow nothing tells them nothing — so they fill in the blank themselves, usually with the worst-case version, and start returning other recruiters’ calls.
I get why the stall happens. Liking three candidates is genuinely harder than liking one. You’re not just evaluating people anymore, you’re trying to rank them, and ranking is uncomfortable when there’s no obviously wrong answer. So the calendar fills up, the trip gets taken, and “I’ll figure it out next week” becomes the plan.
Meanwhile, the market doesn’t wait for you to get back from vacation.
If you’re the hiring manager
The stall almost never happens because you don’t know what you want. It happens because you haven’t built in a forcing function to decide. Put the decision on the calendar before the interviews even start — a specific day you’ll rank the finalists, not a vague “sometime after we’re done.” If you’re about to be out for a stretch, tell your recruiter and your candidates that upfront. A known delay is a non-event. An unexplained one is how you lose people.
If you’re the candidate
If you’ve finished a final round and gone quiet on, that quiet is rarely about you. It’s usually a calendar problem on their end, not a verdict on your interview. Ask for a specific date you’ll hear something, not just “soon.” And if that date keeps moving without a real reason, that’s useful information too — about how decisions get made at that company, not just about this hire.
If you’re the recruiter in the middle
This is the part nobody sees. You’re not just managing a search anymore, you’re managing a countdown on candidates who have no idea one started. The job becomes buying time honestly — real updates, real timelines — instead of vague reassurance that quietly turns into a lie the longer the client stays dark.
The best candidates aren’t sitting around waiting to find out if they made the cut. They’re taking other calls. Every week of silence is a week you’re betting they won’t.
If you’ve got a search stuck in the “I’ll get to it” phase — on either side of the desk — hit reply. I’d like to hear where it’s stuck.