Why the Recruiter Gets Blamed for the Hiring Manager's Calendar

When a hire takes six weeks, people ask the recruiter why. That seems fair on the surface. The recruiter runs the process, sends the updates, and answers for the dates. But try going back through a slow search and asking, at every point where it stalled, who it was waiting on. In a lot of cases the answer is someone else: a hiring manager with a dozen other things on their calendar that week.

I don't think this is anyone being lazy. A hiring manager is a manager first. Interviewing is something they fit in around the job they were actually hired to do, so a candidate who needs 45 minutes of their time is competing with everything else that needs 45 minutes of their time. The requests wait.

What's odd is how little attention the waiting gets. Recruiting teams have spent years speeding up the stages they own: posting jobs, sourcing, moving applications through the ATS. The tools got better and those stages got faster. The stretch between sending a shortlist and getting the first interview booked did not. One set of enterprise hiring data from 2025 put the average hiring manager response time at 4.7 days. Nobody on the recruiting side controls that number, and in most teams I doubt anyone tracks it.

Now add interview rounds. Suppose a role has four of them, and each one sits for four days while the hiring manager finds a slot. That's 16 days spent waiting on one person's calendar, before you count a single delay from the recruiter or the candidate. And none of it feels like delay while it's happening. Each wait is only a few days, which seems normal. It's the total that hurts.

This is why the blame lands where it does. When a VP asks why the SDR hire is taking five weeks, the recruiting team points out how fast they produced the shortlist, and the hiring manager nods along. Nobody mentions the four-day gaps that repeated in every round, because nobody measured them. The recruiter is the person everyone can see. The calendar is not.

Most of the AI that has come into recruiting went into the recruiter's stages as well: writing job descriptions, scoring resumes, automating outreach. Those are real improvements. But they make an already quick part of the process quicker and leave the slowest part where it was. No software is going to free up a VP's Thursday afternoon.

There is an indirect way in, though. Think about what the recruiter's screening call is for. Part of it is getting to know the candidate, but a large part is protecting the hiring manager, making sure that whoever reaches the interview is worth an hour of their time. When screening is thin, the hiring manager ends up doing the filtering inside the interview, and every weak candidate who slips through takes a slot that didn't need to be given.

So if you can't give the hiring manager more hours, you can ask less of the ones they have. If everyone who reaches them has already been properly spoken to, they can see fewer people. Fewer meetings are easier to fit in, so they happen sooner. I'd expect the teams that cut time-to-hire the most to be the ones that need fewer hiring manager touchpoints per hire and make each one worth having.

That handoff is the part of the problem we built Asendia around. It's software that phones applicants and interviews them against the criteria for the role, so by the time a recruiter looks, each person has already been screened and summarized in the ATS. The recruiter's job changes from filtering a raw queue to confirming and scheduling people who have already been talked to.

The hiring manager's calendar is still the constraint. What changes is what fills it. Suppose a queue of 200 applications turns into a shortlist of 15 people who have actually been screened, and the hiring manager needs six interviews instead of twelve. Six slots are much easier to find than twelve, and the decision comes sooner. Resume scoring can't get you there, because a well-scored resume still belongs to someone nobody has talked to. (There's a longer argument about why most ATS setups work more like a filing cabinet than a recruiting tool, and why that makes the scheduling problem worse.)

To check whether this applies to your team, take your last few slow hires and, for every gap longer than a day, write down who the process was waiting on. My guess is that the hiring manager's name comes up more often than the recruiter's.

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