Fix the Parts of Hiring You Control

Most recruiting dashboards are really dashboards about recruiters. They track time to source, time to screen, submittals per role, and response rates on outreach. What they almost never track is how long a candidate sits with the hiring manager at each step. That gap suits nearly everyone involved except the candidate.

It matters because when people talk about a hiring bottleneck, they usually mean recruiter capacity: screening bandwidth, sourcing speed, a queue nobody has gotten to. In most pipelines I'd argue the slower part is the hiring manager, the person who owns the role and whose calendar decides how fast things move between the first interview and a signed offer. Scheduling the first interview, coordinating a panel, turning around feedback, and making the final call all wait on them.

Because TA leaders are mostly judged on recruiter metrics, the manager's delays stay out of view. They show up only when a candidate withdraws or takes another offer, and by then nothing in the data shows where the time went. If you're rethinking which numbers deserve a place on that dashboard, the post on what to track instead of time-to-hire is worth reading alongside this one.

Hiring managers aren't indifferent. Most care a great deal. The trouble is that for most managers, hiring is an interruption. It competes with their real work, and nothing they're measured on rewards them for moving a candidate along quickly. A candidate waiting for an interview slot is out of sight until the recruiter's follow-up email brings them back to mind.

So the delays pile up, and each one looks reasonable on its own. The first interview slot is eight or nine days away. Feedback takes four business days instead of one. The final decision meeting slips from Thursday to the following Tuesday because two stakeholders couldn't line up their calendars. Together they can stretch a hiring process to 40 days, and some candidates drop out along the way. Many of them haven't found a better offer, only a faster process.

Think about what that does to the person on the other side. A candidate who first meets the hiring manager on day 18 applied 18 days ago. In that time they've probably had first-round interviews elsewhere, maybe a panel or two. The interest they felt when they applied has cooled into curiosity, and the manager ends up meeting a less invested version of the person who applied.

This leaves TA in an awkward spot. If the manager is the bottleneck, the obvious fix is to speed up the manager. But in most organizations managers report to a business line and not to talent acquisition, so TA can nudge and remind and not much more. Training sessions, better feedback templates, and more reminder emails from the ATS won't fix it, because the cause is a real conflict of priorities, and that isn't going away.

What TA can control is everything before the manager gets involved, and there's usually a lot of slack there. Take a fairly ordinary timeline. Applications get reviewed within two or three days. Scheduling a screen takes another two or three days of back-and-forth. The screening call happens around day five or six, the shortlist goes to the manager around day eight to ten, and the manager schedules for somewhere between day 12 and 16. Almost none of the time before the manager is spent judging anyone. It's logistics, which means most of it can be removed.

Suppose it were removed, and the shortlist reached the manager within two days of the application. The manager is exactly as slow as before, say ten days to find a slot. But the candidate they meet applied about 12 days ago instead of three weeks or more. They're more likely to still be actively interested, and competing processes have had less time to get ahead. You haven't made the bottleneck any faster, but you've made sure the candidate is still around when it clears.

That's the job we built Asendia to do. In the timeline above, an application waits in a queue until someone reviews it, then waits again while a screen gets scheduled. Asendia removes both waits. It phones the applicant within hours of their application, evenings and weekends included, and has a spoken screening conversation that adapts to what they say, measured against a structured rubric for that particular role. The five or six days of review and scheduling shrink to a few hours, and by the next morning there's a ranked shortlist with structured summaries in the ATS, so there's no new dashboard to watch. The recruiter's first job with that candidate is to review them and send them on to the hiring manager.

I'd expect the benefit to show up after the offer too, since a candidate who hasn't spent three weeks waiting is less likely to have mentally checked out by the time you make one. The post on offer rejection rates goes into why process delays sit near the center of why more offers get declined.

The manager's calendar will probably stay as full as it is, and TA can't do much about that. What it can do is make the stages it controls short enough that even a slow manager doesn't push candidates into someone else's process. Then, when the manager finally has the conversation, the candidate still wants to be there.

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