The Best Candidates Leave First

Think about the person at the top of a good shortlist. She applied on Monday, got a screening call within a day or two, answered well, and learned she'd made the shortlist. So far your process has told her something flattering about your company: that it's organized, and that it wants her.

Then a week goes by with no word, and then another.

What is she doing in the meantime? Probably talking to other employers. The qualities that put her at the top of your list are the same ones that put her at the top of other people's lists. This is the part of slow hiring I think teams underweight. The wait doesn't cost you candidates evenly. It costs you the ones you wanted most, and it costs you those first. Your fifth choice may still be around in two weeks. Your first and second choices are the least likely to be.

Why the wait got more noticeable

Screening used to be slow enough to hide this. One estimate puts the time from a shortlist reaching the hiring manager to interviews being finished at around fourteen days. When screening itself took weeks, those fourteen days were one slow stage among several and nobody singled them out. Once screening gets fast, they're most of what's left.

The way candidates arrive has changed too. Six months ago a hiring manager might have seen vetted candidates trickle in over three weeks, a few at a time, which is a pace you can keep up with between other work. Now twenty-five of them can land on a single Thursday. Nothing about a hiring manager's week was set up for that. I wouldn't blame the managers themselves. They're working inside a process built for one arrival rate that is now being fed at another.

Candidates don't see any of these stages, of course. From her side there's just your company, which was quick and then went quiet. Whatever good impression the fast screen made gets worn away by the silence after it.

What makes a shortlist slow to act on

The obvious fix is pressure: tell hiring managers to respond faster. But look at what a traditional shortlist asks of them. It's a list of names with resumes attached. A busy manager opens it on a Tuesday afternoon, reads four profiles, and has to decide whether to interview all twenty or narrow the list further. Usually the answer is a thirty-minute call with the recruiter to talk it through, and that call goes on the calendar for later in the week. The manager may be perfectly engaged. What they were handed simply needs interpreting before anyone can decide anything, and interpreting takes time they don't have.

So I think the more useful question is what a shortlist would have to contain for a manager to decide from it in one sitting.

That question is close to the center of what we've built at Asendia. It phones applicants and screens them in a live conversation that follows up on what each person says, and every candidate for a role gets asked the same core questions. So instead of a stack of resumes, the hiring manager gets a short written summary for each candidate: their answers in their own words, a score against the role's criteria, and the reasoning behind the score. Say the role is in logistics operations. The manager can read what each candidate said about handling shift scheduling conflicts, see how that was scored, and put five people's answers to the same question side by side. Deciding to interview the top five and pass on the rest becomes a short job. The summaries are saved to the ATS, so they sit where the manager would look anyway. If you're making the case internally that speed affects whether offers get accepted, the post on offer rejection rates looks at candidate timelines from the other side of the offer.

I don't think pushing hiring managers harder does much on its own. People who are told to hurry but handed something hard to read still put it off. Hand them something they can decide from quickly, and the person at the top of the list has a better chance of still being there when they do.

Ready to transform your hiring strategy? Schedule a Demo with our founders today!