Who Survives a Six-Week Hiring Process

Every hiring process is a filter, and most of it was designed on purpose. Someone chose the screening questions, the take-home exercise, the interview panel. But one part of the filter nobody designs is time, and I suspect it does more sorting than all the others.

Here's how it works. When a strong candidate drops out in week three, they don't write to explain why. They accept another offer and stop replying. What you're left with is whoever was still around when you were ready to decide. One commonly cited average puts time to offer for professional roles at 23 days, and past 40 for roles with four or more interview rounds. That's a long time for the market to go through your pipeline before you do.

So who is still there in week five or six? Some are out of work and can afford to wait. Some are unhappy enough in their current job to put up with almost anything to leave it. Others just don't have competing offers making them impatient. None of that disqualifies anyone, and some of your best hires will come to you exactly this way. But it should make you curious about who survives your process, and why.

Now think about a candidate who doesn't survive it. Say she's a software engineer who is good at her job, comfortably employed, and open to the right move without needing one. Her manager would fight to keep her. She isn't going to cancel a vacation to fit in a sixth interview, or wait two weeks for feedback on a case study. Her part in your process is voluntary, and it lasts only as long as the process seems worth what it costs her. Once it stops seeming worth it, she doesn't send a rejection. She just stops answering. For someone like her, a 40-day process usually crosses that line well before an offer shows up.

Put those two pictures side by side and you get something slightly uncomfortable. The longer a process runs, the more it favors candidates who didn't have better options at the time. That isn't the same as favoring worse candidates. But I think availability and market value pull in opposite directions often enough, across hundreds of hires, to matter. And because the people who left never show up as rejections, you won't see it in your offer acceptance rate. That number only measures the end of a process that has been sorting people the whole way through.

Where does the sorting start? Earlier than most people assume: in the gap between applying and the first real conversation. A candidate who applies and hears nothing for four business days has already formed a view of how fast your company moves, and that view affects how seriously they treat whatever you ask of them next.

That first gap is the one we built Asendia to close. It exists mostly because a recruiter can only make so many calls in a day, so new applicants sit in a queue until someone gets to them. Software doesn't have that limit. Asendia can call every applicant soon after they apply, however many arrive at once, and have a live conversation that adjusts to what they say. So instead of opening a queue, the recruiter opens a ranked shortlist, with qualification summaries and quotes from each candidate written into the ATS, and interviews can be booked for later that week.

Does that keep the engineer? Not always. But suppose she applied to six companies in the same week. At most of them she'd still be waiting for a first conversation on day twelve, which is about when people like her start to drift. At yours she'd have had one within a day. You're no longer racing to catch her attention before someone else does, because you already caught it.

A fair question is whether a faster process gets you better candidates or only the same candidates sooner. My answer is that speed changes who stays long enough to be evaluated, so it's partly both. The same thing shows up at the other end of the funnel, which I wrote about in a post on offer rejection rates and why they usually have more to do with timing than pay.

People normally talk about long hiring processes as an efficiency problem, measured in time to fill and recruiter hours. Those matter, but the larger cost doesn't appear in either number. It's the set of people who were in your pipeline in week one and gone by week four. If you want a rough sense of its size, take the candidates you rated highest after a first conversation last quarter and check how many of them made it to an offer.

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