Why You Keep Rejecting Every Candidate: A Mid-Search Diagnostic
When slate after slate comes back with no offer, the problem is rarely candidate quality. Here's how to find out what's actually broken before you burn a third round.
If you've rejected two full slates (roughly 6-10 candidates) without an offer, the issue is almost never candidate supply. It's usually a miscalibrated comp range, a scorecard that rewards the wrong traits, an ambiguous veto with no written standard, or an internal sponsor who wasn't aligned before the search started.
The Math Behind a Stalled Slate
A slate is typically three to five candidates. One rejected slate is normal — it's calibration. Two consecutive rejected slates with zero offers, six to ten people in, is a different event. At that point the probability that you've simply had bad luck twice in a row is low; something upstream of sourcing is broken, and a third slate built the same way will likely produce the same result.
Run the math on what a third slate costs you. Take a retained director-level search at a 25% fee on a $150,000 role: roughly $37,500 total, often billed a third at engagement, a third at slate presentation, a third at start. If you're requesting slate three with no offer made, you've typically paid out two-thirds of that fee — around $25,000 — against zero hires, plus six to eight weeks of calendar time the seat sat open. That's the real cost of treating a structural problem as a sourcing problem.
Four Reasons Slates Stall (and How to Tell Which One You've Got)
Comp mismatch disguised as 'not quite right.' The candidates who get furthest in your process are the ones countering 10-15% above the posted range, or dropping out at offer stage over base pay. If your rejection reasons keep circling back to money without anyone saying the word, the range is wrong, not the people.
Scorecard rewarding the wrong trait. If every rejection cites the same single competency — 'not strategic enough,' 'too operational' — despite candidates clearing every stated must-have, the recruiter is screening to a spec that doesn't match what your approvers actually reward in the room. That's an intake failure, not a talent-pool failure.
No real standard, just a veto. If feedback across candidates is inconsistent in kind — one rejected for being too quiet, the next for being too aggressive — there's no written scorecard anyone is actually scoring against. The rejection is a feeling, and feelings don't generalize across five different resumes.
No committed sponsor. If different approvers reject the same candidate for contradictory reasons, or the person with final veto power wasn't on the original intake call, the search was built on a spec nobody with authority actually signed off on. Candidates aren't failing an evaluation — they're walking into a disagreement that predates them.
Running the Rejection Debrief
After every reject, the recruiter should log the reason against a specific scorecard line item, not a general impression. 'Reject — scored 2/5 on P&L ownership, must-have' is usable data. 'Not a fit' is not. If two consecutive rejections can't be mapped to a written line item, stop sourcing and fix the intake before a third slate goes out.
Test for recency bias before you trust your own read: re-score the candidate from two interviews ago using today's stated criteria, cold, without looking at your original notes. If the standard you're applying to candidate five would also have killed candidate two — who you initially liked — the standard moved mid-search, and candidates are being judged against a moving target.
A sharper version of the same check: re-score your current best performer in that role, if one exists, against the exact rubric being applied to the slate. If the rubric would have rejected your own strongest hire, the rubric is miscalibrated, not the market.
Recalibrate, Escalate, or Kill
Recalibrate when the pattern points to comp or spec. Move the range, or narrow the must-have list to what's truly non-negotiable, before the next slate goes out — not after it comes back rejected again.
Escalate when the pattern points to indecision. Get the final approver into the live screen instead of reviewing resumes after the fact. A veto exercised in real time, with context, behaves very differently than a veto exercised over a one-page summary three days later.
Kill or pause when recalibration doesn't change the outcome. If you've already adjusted comp and tightened the scorecard and a third slate still stalls, the candidates aren't the variable — the market has answered a question your organization hasn't fully accepted yet, usually about what this role is actually worth or whether it's actually funded to succeed.
The Two Biases That Fake You Out
Halo bias: comparing every candidate to the best qualities you remember from a predecessor, rather than to the written scorecard. Memory smooths out the predecessor's weaknesses over time, so no live candidate can win that comparison.
Order bias: the last person interviewed disproportionately shapes the group's verdict, especially after a long gap between interviews. The fix is mechanical, not willpower — score each candidate against the written baseline immediately after the interview, before discussing them relative to anyone else in the slate.
Frequently asked
Good questions.
How many rejected candidates is normal before we should worry?
One rejected slate of three to five candidates is normal calibration — searches rarely land on the first pass. Two consecutive rejected slates, roughly six to ten candidates total, with no offer made is the threshold where you should pause and audit before requesting a third. At that point the odds favor a structural issue in comp, scorecard, or internal alignment over a run of weak candidates.
Our recruiter says we're being too picky. How do we know if that's true?
Check whether your rejection reasons map to specific, written scorecard criteria or to general impressions. If two rejections in a row can't be tied to a concrete line item — a skill, a comp number, a must-have — the recruiter is likely right that the standard is ambiguous. If every rejection maps cleanly to the same documented gap, the candidates genuinely aren't clearing the bar, and the spec or sourcing channel needs to change, not your judgment.
Should we switch search firms if we keep rejecting candidates?
Usually not yet. Switching firms resets the clock without fixing the underlying cause, and a new firm sourcing against the same flawed intake will likely produce the same pattern. Run the rejection debrief first. If the pattern traces to comp or an unclear scorecard, fix that internally before concluding the firm is the problem.
Is it a bad sign if we reject the entire first slate?
Not necessarily. A first slate is often a calibration tool — it tells the recruiter what your stated criteria actually mean in practice, which is sometimes different from what was written in intake. Rejecting all of it once, with specific feedback the recruiter can act on, is normal. Rejecting it with vague feedback, or rejecting a second slate the same way, is the signal worth stopping for.
Ready to make the hire?
Tell us the role, the comp band, and the timeline — we'll tell you exactly how we'd run the search.