What sourcing signals actually predict a hire

Most sourcing decisions are made forwards. You see a profile, you read a set of signals off it, the right title, a marquee employer, a fast reply, and you form a view of who's worth pursuing. The trouble is that those signals were never validated against the only outcome that matters, which is whether the person actually took the job. So we ran it the other way. Across a run of Director-and-up searches we'd already closed, we sorted candidates by the early signals they showed, then checked each signal against who converted to a hire and who dropped out along the way.

The result cut against instinct. A perfect title match, an impressive current employer, a reply within the hour, the signals that feel like a strong start, turned out to be nearly uncorrelated with closing. At best they told us a first conversation would go well. They said nothing about whether it would finish. The candidates who looked most promising on paper were, disproportionately, the ones who enjoyed the chat and then stayed exactly where they were.

There's a reason the obvious signals disappoint, and it's built into what they measure. Title match, employer brand and response speed all get at the same thing: how well a person fits the shape of the role on paper, and how easy they are to reach. None of them touches the variable that actually governs a senior move, which is the friction between where the person is now and where they'd have to go. Someone who fits perfectly and has nothing pulling them out of their current seat will happily take a call and go nowhere.

This matters because most sourcing pipelines are tuned for exactly the loud signals, largely because they're the easy ones to measure. Keyword-fit scoring, seniority filters, responsiveness ranking, the machinery rewards whatever's legible. So the top of the funnel fills with people who are pleasant to talk to and unlikely to move, while the person with a real reason to leave, who may have a slightly-off title and a slower reply because they're being careful, sits lower in the stack. The pipeline measures the wrong thing, and it does it with a lot of confidence.

The signal that held was harder to see and much harder to fake. It was a concrete reason the person might actually change roles. A named ceiling. A scope they'd visibly outgrown. A mandate they couldn't get where they were. A decision they wanted to own and couldn't. A reorganisation that had moved the thing they cared about out of their remit. Candidates who could put one of those on the table in the first real conversation converted at a markedly higher rate than those who were simply open to a chat.

Specificity is the whole thing here. “I'm always happy to hear what's out there” is a reason to talk, and in our closed searches it rarely turned into a reason to move. “I've built the platform team twice and I'm not going to get a third mandate here” names an actual ceiling, and a ceiling is something a new role can credibly clear. What separates the two is whether the person can point to the specific thing their current seat can't give them.

If the reason to move is what predicts, then early qualification should be chasing that reason, and most first calls chase availability instead. “Are you open to hearing about a role” selects for politeness and curiosity. There's plenty of both around, and neither closes a search. A more useful question is some version of “what would have to be true for you to move,” because it forces the person to either name the ceiling or show that there isn't one. In our closed searches, the clarity of that answer told us more than any credential on the page about which candidates would still be there at offer.

This reorders the work. You spend less of the first conversation confirming the fit the profile already implied, and more of it probing the friction the profile hides. A vague, upbeat answer becomes a yellow flag rather than a green light. Enthusiasm without a named reason is, more often than not, the signature of the candidate who withdraws 2 weeks before the offer. And you become willing to advance a slightly-off-title candidate with a sharp reason to move ahead of a perfect-title one who can't say why they'd leave. Looking back across the searches, that trade paid off far more often than it didn't.

The operational consequence is that the top of the funnel should be built to surface motive early, rather than to run up a tally of pleasant conversations that go nowhere. That runs against how most sourcing is scored, where a recruiter's week is measured in profiles reviewed and replies received, both of which reward the loud signals we found to be near-useless. Scoring on those metrics actively fills the pipeline with the wrong people and then reports it as productivity.

The obvious signals are still worth keeping. A title-and-employer scan is the fastest way to bound a long list. The fix is to demote them to what they are: a coarse filter for plausibility. Plausibility gets someone into the first conversation. It's the first conversation that has to do the real qualification, and it has to be built to find the ceiling. Across the searches we reviewed, the ones that closed were, disproportionately, the ones where we had a specific reason-to-move on the record early, and the ones that stalled were the ones where we'd confused a good fit for a live candidate. Anonymised across the set, the pattern was consistent enough that we now treat “what would have to be true” as a gating question.

There's a mirror to all of this on the client side, and it's uncomfortable. If the signal that closes a senior hire is a specific reason to leave, then the role has to offer a specific reason to arrive: a scope, a mandate, a decision the candidate can't get where they are. A search briefed as “we need a strong Director of X, similar to what we have but better” is asking the market to move people who have no reason to. The reason-to-move and the reason-to-arrive are the same axis viewed from two ends, and a mandate that's only a lateral copy of the candidate's current seat has nothing to put on the far end of it.

So the sourcing insight resolves into a briefing discipline. Before a senior search opens, the useful question is “what does this role let someone do that their current one doesn't.” Where the honest answer is “not much,” the search will be slow and the offers will be countered, because we'll be competing on money against employers who hold the relationship. Where the answer is specific, a genuinely larger remit, a build rather than a maintain, ownership that didn't exist before, the same reason-to-move that we score for in candidates is the thing the mandate can credibly satisfy. That alignment, more than any sourcing tool, is what turns a strong shortlist into a closed hire.