A curated shortlist hides the two candidates who’d have said yes

A shortlist is a bet about who's worth a conversation. The trouble is what the bet is placed on. Curation scores what a document can show: current title, current city, current employer, years in the exact function. Those are proxies for fit, and they're legible on paper, so they get weighted heavily. The thing that actually predicts a close, whether the person wants to move and would move for this, leaves almost no trace on a CV.

So the filter does its job and produces a tidy list of people who look right. Some of them are lukewarm. A few are flattered by the outreach and will interview politely and stay put. Meanwhile 2 candidates who read as an 80% match on paper, but who were ready to leave their current role this quarter, never made the cut. The list is clean. It's also missing the people most likely to say yes.

This isn't a hypothetical margin. When 4 in 5 employers report difficulty finding the skills they need (82% for Q2 2026, per ManpowerGroup's Employment Outlook Survey), the scarce variable is the availability of skilled people who are actually willing to move. A shortlist that filters on skill and ignores willingness is optimising the abundant thing and discarding the scarce one.

Over-curation rarely fails loudly. It fails through a handful of defensible-sounding filters that each strip out a slice of the highest-intent pool. The location filter is the clearest. Screen to candidates already in the metro and you remove the person 2 cities away who's been trying to get back for a year, whose partner just took a role here, who'd relocate on their own rupee. On paper they're a “no, wrong city.” In a 5-minute call they're the most motivated name on the list.

The tenure filter does similar damage. “Must have 3 years at current employer” reads as stability, but it also deletes the person at 18 months who's just hit the exit cliff and is quietly looking. High intent and short tenure correlate more often than a screen assumes. The exact-title filter is the third: it keeps the person whose title matches and drops the person doing the same work under a different label who's outgrown their scope and wants out.

None of these filters is stupid. Each is a reasonable heuristic that happens to be blind to intent. Stacked together on the same requisition, they shrink the pool selectively, cutting hardest into the segment that would have converted fastest.

The reason curation misses intent is structural. A CV is a record of the past. It tells you what someone has done and where they sit now. It says almost nothing about what they want next, because nobody writes their reason for leaving into the document you're screening. The signals that predict a move, a manager change they can't stomach, a relocation they've been planning, a promotion that didn't come, a project that just shipped and freed them up, live in conversation and nowhere else.

So the tighter you curate before anyone talks, the more you're betting the match on the one dimension the paper is silent about. You end up with a list selected for legibility and unselected for motivation. The candidate who reads perfectly and won't move survives every filter. The candidate who reads at 80% and would start Monday gets cut in the first pass.

There's a cost hiding inside speed, too. A heavily filtered pool feels efficient because it's small. But a small pool of lukewarm names takes longer to close than a wider pool that includes 2 motivated people, because motivation is what compresses a process. The efficiency is a mirage. You've traded a short list for a long search.

When a search stalls, the instinct is to widen the spec or raise the band. Before either, run the pool back through the filters that built the shortlist and ask what each one cost you. This is a diagnostic you can do in an afternoon on any open req.

Pull the full sourced set, the names you screened and the names you cut. Then take each filter in turn and count. How many candidates did the location screen remove, and of those, how many are within a plausible relocation of the role? How many did the tenure floor cut, and how many of those sit in the 12-to-24-month window where people move? How many did the exact-title match drop who are doing the same work under another name? You're surfacing only the people a filter removed for a reason that has nothing to do with whether they'd take the job.

Then reach out to that recovered set with a different opening move: a short, direct message that names the role and asks one question about timing and willingness to move. You're testing for intent cheaply, before you invest a screening call. On a genuinely stuck req, a re-opened pool of 10 to 15 recovered names, contacted for intent first, will frequently produce a live candidate the original shortlist never contained. If it doesn't, then the spec or the band is the real problem, and you've ruled out the cheaper cause first.

Most processes discover intent last, at the offer, when it's too late to have changed the shortlist. Move it forward. The cheapest way to read intent is to ask for it directly and early, in the first contact, in plain terms: is now a time you'd consider a move, and would you relocate for the right role? The answer tells you more about likelihood of close than another line of their CV ever will.

Beyond the direct question, a few signals reliably indicate a person who's ready. Someone who replies fast and asks about the team and the mandate, beyond the comp, is usually already looking. Someone at the tenure window where they typically move is worth a call even at an imperfect title match. Someone whose stated reason for interest is specific, a relocation, a scope they can't get where they are, a manager situation, is telling you the move is real. Read those signals in the first conversation and let them re-rank the list. The best-fit name on paper and the most-likely-to-say-yes name are frequently two different people, and the second one wins you the hire.

A shortlist has to narrow, or nobody gets hired. The point is to narrow on the right axis. Filter on the skills the role genuinely requires, and hold the intent-blind filters, location, exact title, tenure floor, loosely, as flags to investigate. Let a 5-minute intent read decide the borderline names.

Do that and the shortlist stops hiding your two best candidates. You spend the same sourcing effort, but you weight it toward people who will actually move, which is the variable that decides whether a req closes in a market where willing supply is the scarce input. The over-curated list feels safer because it's cleaner. The wider, intent-read pool is the one that gets you to a yes.