Why the Best Candidates Drop Out in the First Week

Two people apply for the same software engineering role on the same Monday. One has five years of relevant experience and is also talking to four other companies. The other has been looking for months and hasn't heard back from many places. Your recruiter is busy, and gets to both of them the following Monday. Which one picks up the phone?

Probably the second. By then the first has had calls with the companies that answered quickly, and may be in second rounds with some of them. They haven't withdrawn from your process. They might even take your call. But whatever interest they brought to the application is gone, and the conversation you have now is a much weaker one than you could have had a week earlier.

When someone applies, their interest in the job is at its highest. They've looked into the company, tailored their resume, maybe written a note, and they're watching their inbox. I don't think that state lasts long. Within a few days other applications, their current job, and the rest of life start to crowd it out. After a week of silence, your role sits in the same mental pile as every other company that hasn't replied.

So a slow first response doesn't treat all applicants the same. It filters them, and in the wrong direction. The people who can afford to wait a week are, more often than not, the ones with fewer alternatives. The ones with options go to the employers who called first.

Why the data doesn't show it

You'd expect a problem like this to be obvious in your numbers. It mostly isn't. When a recruiter calls on day eight and gets no answer, the ATS records "no response" or "withdrew," and the natural reading is that the candidate wasn't serious. The more accurate reading is that they stopped being serious days earlier, and you called after they'd already decided.

It gets more misleading. If your first contact is slow, the candidates who do answer are mostly the ones with fewer options and more patience. Many of them will be fine, and they'll advance past the screen at a decent rate. The pipeline looks healthy, maybe healthier than it should. Meanwhile the applicants you'd most have liked to hire went elsewhere, and nothing in your reports looks unusual.

The same thing leaks into later stages. Some offer rejections that get put down to compensation or competing timelines probably began in that first quiet week, when the candidate concluded your process wasn't going to move and never fully committed. If you're trying to work out why offers get declined, it's worth looking further upstream than the offer. I wrote about that connection between pipeline speed and offer outcomes in an earlier post.

Where the week goes

None of this means recruiters are slow. Picture one with 15 open reqs, a backlog of interview feedback to write, and a hiring manager chasing them about a finalist who stalled. A new role goes live and gets 200 applications in the first two days. Even someone who did nothing but make calls could only fit in a few dozen real conversations a day, and this person has other work. Most of those 200 people wait. The problem is one of timing: applicants are most engaged at the moment your team has the least time for them, and trying harder doesn't make those two moments line up.

This timing problem is the one we chose to work on. Asendia is software that phones applicants within hours of their applying, evenings and weekends included, and interviews them. The whole point is that the first conversation happens while the applicant still cares, so the recruiters start from people who have already been engaged instead of from a list of names.

What I find more interesting is what the early call does to the rest of the process. A candidate who had a real conversation a few hours after applying tends to be more committed from then on. They've told you specific things about their background and learned concrete things about the role, so there's a small relationship with your company that simply doesn't exist for someone who sent a PDF and heard nothing for eight days. To check whether that's happening in your own pipeline, this post on what to track in a post-AI recruiting world goes through which numbers tell you something and which only look reassuring.

A simple place to start is your own last few months of data. Line up how many days each applicant waited for a first real conversation against who later went silent or withdrew. I'd be surprised if the pattern weren't there.

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