How AI Recruitment Agencies Reduce Time to Hire

Before you panic about your time to hire, it's worth checking whether it's actually a problem.

A 45-day hiring process feels agonising when you're the one waiting on a critical role to be filled. It also happens to be perfectly average for financial services. A 30-day process sounds admirably brisk until you realise you work in tech, where 30 days means you either got lucky or cut some corners you'll regret later.

Context matters enormously here. And yet most people benchmarking their time to hire are comparing themselves to a vague sense of "normal" rather than actual data for their sector.

So let's fix that.

This article pulls together the most recent benchmark data for average time to hire across industries in the UK and US. We'll look at what the numbers are, why they vary so dramatically between sectors, what counts as genuinely slow versus acceptably complex, and — because a benchmark is only useful if you do something with it.

(Also, if you're confused whether you should be tracking time to hire or time to fill, click here to read our comparison.)

What Is the Average Time to Hire Right Now?

Let's start with the headline figures, because they're more interesting than you'd expect — and they've been moving in a direction that should get HR leaders' attention.

LinkedIn's 2024–2025 recruitment data puts the average time to hire in the US at around 36 days from job posting to offer acceptance. Across the Atlantic, the average time to hire in the UK sits at 4.9 weeks across all industries, regions, and job functions — which works out to roughly 34 days, very slightly below the US figure.

Zoom out to a global view and the number climbs. Josh Bersin's research puts worldwide average hiring at 44 days.

Now here's the part that should make you sit up slightly. New research from Totaljobs found that the average time to hire in the UK stretched to eight weeks in 2025, up from 4.8 weeks in 2024, with larger organisations taking up to nine weeks. That's a significant jump. The slowdown reflects a more cautious approach to hiring amid rising costs, including increases to the national living wage and employer national insurance contributions.

In other words: the market got more expensive, employers got more careful, and the average time from application to hire went up considerably. Whether that caution is producing better hires or just slower ones is a separate question — and one worth asking.

What all of this tells us, before we get into the industry breakdown, is two things. First, there is no single universal benchmark. Second, the benchmarks themselves move, which means whatever number you saved from a 2022 report is probably no longer representative.

Average Time to Hire by Industry: UK Benchmarks

In the UK, the government and public sector has the longest average time to hire of any industry at around six weeks, likely due to the administrative processes involved — security clearances, compliance checks, multi-stage panel processes — that are difficult to compress without creating problems further down the line.

At the other end of the spectrum, hotel and catering has the shortest time to hire at approximately 3.9 weeks, which reflects the high proportion of temporary, seasonal, and volume roles in that sector.

For sectors in between, energy and defence sits at over 67 days — the longest of any UK sector — followed by professional services at around 47 days.

The median time to hire in the UK, according to SmartRecruiters' 2025 benchmarking report covering nearly 90 million applications across 95 countries, is 40 days — just above the global average.

Geography also plays a role within the UK. London has the longest regional average at 5.5 weeks, while Yorkshire and the Humber sits at just over 4 weeks — the fastest of any UK region. Whether that reflects a more competitive London talent market, more complex London roles, or simply that everything moves slower when it costs £4.50 for a coffee is open to interpretation.

Average Time to Hire by Industry: US Benchmarks

The US data from Workable, drawn from millions of anonymised hiring processes, gives a cleaner industry-by-industry breakdown.

Manufacturing comes in fastest at 30.7 days. Professional services sits at 31.2 days. Information roles average 33 days. Government roles average 40.9 days. Financial services is the slowest of the sectors tracked, at 44.7 days.

For technical roles, hiring for software and engineering positions typically takes between 40 and 50 days in the US. Healthcare and pharma runs longest of all, at between 49 and 67 days, driven by strict regulatory requirements and the need for licence and certification verification.

At the faster end, hospitality and retail regularly comes in under 30 days — not surprising given the volume-driven nature of hiring in those sectors and the relatively lower barrier to entry for most roles.

The broad patterns are consistent across both UK and US markets. The sectors with the longest time to hire share common characteristics: they involve regulatory compliance, technical specialisation, or multi-stakeholder decision-making. The sectors with the shortest time to hire tend to involve higher volume, lower specialisation, or both.

Why Does Time to Hire Vary So Much Between Sectors?

The differences between a 27-day retail hire and a 67-day healthcare hire aren't random. Each industry's average time to hire is shaped by a fairly logical set of factors.

‍

Regulatory requirements.

Healthcare, financial services, energy, and defence all involve background checks, licence verification, regulatory compliance, or security clearances that have a minimum processing time regardless of how efficiently everything else runs. You can't speed up a DBS check by scheduling more interviews. The clock has to run.

‍

Specialisation and candidate scarcity.

When the pool of qualified candidates is small — a niche engineering discipline, a rare clinical specialism, a senior technology leadership role — sourcing takes longer because the candidates simply aren't as plentiful. Time to hire in these areas reflects market reality as much as process efficiency. UK data from the CIPD shows 37% of employers currently have hard-to-fill vacancies, and the roles driving that figure are concentrated in exactly these high-specialisation sectors.

‍

Number of decision-makers.

Public sector and large enterprise roles frequently involve multiple hiring panels, committee sign-offs, and approval chains that private sector organisations at the same seniority level would handle with two or three people. More stakeholders means more scheduling, more deliberation, and more time.

‍

Seniority.

Executive and senior leadership roles routinely take 90 to 120 days, with director-level searches commonly running 60 to 90 days. This is true across virtually every sector, because senior hires involve higher stakes, more stakeholders, and often a longer notice period negotiation at the end.

‍

Market conditions.

Rising employment costs have made many UK employers more cautious about hiring decisions in 2025, with 56% of recruiters reporting difficulty securing sufficient recruitment budgets. When employers are more careful, they take longer. That caution isn't unreasonable. Whether it's producing better outcomes is a separate question.

What Is a Good Time to Hire Benchmark?

Here's the question lurking behind all of these numbers: what should you actually be aiming for?

The answer is almost certainly not "beat the industry average at all costs." That's a metric game, not a hiring strategy.

A genuinely useful time to hire benchmark has three characteristics.

‍

It's sector-appropriate.

A 50-day time to hire in tech is unremarkable. A 50-day time to hire in hospitality is a process problem. Use your industry average as the baseline, not a generic cross-sector figure.

‍

It's segmented by role type.

Your graduate scheme hires should have a different benchmark from your Director-level searches. Averaging them together produces a number that's not particularly useful for diagnosing anything specific. Knowing the average time to hire by business function in your region gives you a more meaningful basis for comparison than a single company-wide figure.

‍

It correlates with quality.

This is the check that most benchmarking conversations skip entirely. If your time to hire is five days below the industry average but your six-month retention rate has dropped, you haven't improved — you've just accelerated. The benchmark is only meaningful if the hires it's producing are actually good ones.

‍

A good time to hire benchmark, in other words, isn't the number itself. It's the number in context.

Average Time From Application to Hire: What Candidates Experience

Most benchmarks are calculated from the employer's side of the process. It's worth pausing to look at the same journey from a candidate's perspective, because that's where your employer brand gets made or broken.

From the moment a candidate submits an application to the moment they receive a formal offer, the experience typically includes several days of silence while the application is reviewed, a screening call, one or more interview stages, a deliberation period, a verbal offer, and a wait for written paperwork. At each gap, the candidate is deciding whether to keep waiting or accept something else.

The best candidates typically receive offers within ten days of entering a hiring process. That's not ten days to complete a process — that's ten days before an offer lands. Which means that if your process runs to five or six weeks, the strongest candidates in your pipeline have probably made a decision about their next role before you've reached your second interview stage.

One in three businesses have made a bad hire because of the need to fill a position quickly — which suggests that rushing is genuinely risky. But that pressure to rush often comes precisely because the preferred candidates didn't wait.

The answer isn't to rush the process. It's to eliminate the gaps — the dead time between stages where nothing is happening and candidates are deciding you're not the priority you claimed to be in the job ad.

When Your Time to Hire Is Above Benchmark

Being above your industry average on time to hire isn't automatically bad news. But it's worth investigating what's driving it, because the cause determines the response.

If the delay is in regulatory compliance or security clearance, there's a limit to what process optimisation can do. The constraint is external. What you can control is how well you communicate with candidates during the wait, and whether your offer is strong enough to be worth it.

If the delay is in sourcing — the pipeline is thin and it's taking weeks to find suitable candidates — the brief may be unrealistic for the available market, or your employer brand isn't attracting the right people. Neither is a scheduling problem.

If the delay is in decision-making — interviews are happening but offers aren't being made — you may have a brief alignment problem (nobody's quite sure what they're looking for, so they keep interviewing) or an internal approval problem (everyone's agreed but nothing can move without a sign-off that keeps being postponed).

If the delay is in the gaps — things are moving but slowly, with multi-day silences between every stage — that's the most fixable version of the problem. Better scheduling, faster feedback turnaround, and pre-approved offer terms can compress this significantly without touching any assessment stage.

Knowing which of these is driving your number is far more valuable than knowing the number itself.

Learn more here on how to reduce your time to hire.

How SquareLogik Uses Benchmark Data

We use time to hire benchmarks the same way a good GP uses height and weight charts. Useful reference points. Not diagnoses.

When we're working on a role, the benchmark tells us what's reasonable to expect and what would represent a genuine problem. A tech hire running to 45 days is probably fine. The same tech hire running to 75 days is worth investigating — not because some chart said so, but because at that point we're almost certainly losing candidates to faster-moving employers and it's worth understanding why.

What we're more interested in than the headline benchmark is stage-level data: where is time accumulating, are candidates dropping out at a specific point, and is the process speed correlating with the quality of who we're eventually placing.

Because a benchmark that tells you you're average is only useful if average is good enough. For most of the HR managers we work with, it isn't.

If your time to hire is running above your industry average and you'd like a clearer picture of what's driving it, we're happy to have that conversation. No lengthy intake forms.

Frequently Asked Questions

What is the average time to hire in the UK?

Recent data puts the UK average at around 34 to 40 days across all industries, though this has shifted. Totaljobs' 2025 research found average time to hire stretching to eight weeks for larger organisations, reflecting more cautious hiring decisions in response to rising employment costs. The figure varies significantly by sector — government and public sector roles average around six weeks, while hospitality and catering comes in closer to four. Always benchmark against your specific sector rather than a cross-industry average.

‍

What is the average time to hire in tech?

Tech and engineering roles consistently sit at the longer end of the hiring spectrum. Current data suggests 40 to 50 days is typical for software, engineering, and technical roles in both the UK and US. The length reflects the scarcity of qualified candidates, the complexity of technical assessment, and the high number of competing offers candidates are typically fielding simultaneously. Processes that run beyond 50 days in tech risk losing shortlisted candidates to faster-moving employers.

‍

What is a good time to hire benchmark?

A good benchmark is one that's specific to your sector, segmented by role type, and read alongside quality of hire data rather than in isolation. Industry-wide, anything between 30 and 45 days is broadly typical for professional roles. But a 45-day hire in financial services is normal; a 45-day hire in hospitality is a process problem. Use your sector average as a reference point, track your own historical data, and treat significant deviations — in either direction — as signals worth investigating.

How long does it take from application to hire on average?

The average time from application to offer acceptance is roughly 34 to 44 days across most professional roles in the UK and US, though this varies significantly by sector. From a candidate's perspective, the experience typically involves several days of application review, a screening stage, one or more interview rounds, a deliberation period, and an offer stage. Research suggests the strongest candidates — those with multiple options — typically receive and consider offers within the first ten days of entering a process.

‍

Why does time to hire vary so much between industries?

The main drivers are regulatory requirements, candidate scarcity, and the number of decision-makers involved. Healthcare, financial services, energy, and defence involve background checks, licence verification, and compliance processes that have a minimum processing time regardless of how efficiently everything else runs. Sectors with high candidate scarcity — specialist tech roles, senior leadership — take longer because sourcing takes longer. Public sector roles involve more stakeholders and approval steps. High-volume sectors like hospitality and retail hire faster because the roles are less complex and the candidate pool is larger.

‍

Is a long time to hire always a problem?

Not always. A longer time to hire driven by thorough assessment of scarce specialist candidates is a very different situation from a long time to hire caused by scheduling delays and slow feedback loops. The question is what's driving the length. If the time is being spent on genuine assessment, it may be justified. If it's being spent waiting for people to respond to emails, that's a problem regardless of whether the end result is within industry benchmarks.

‍

How does time to hire affect the candidate experience?

Significantly. Candidates don't experience your process as a series of stages — they experience it as a sequence of communication and silence. Long gaps between stages, slow feedback, and delays at the offer stage all signal disorganisation and indifference, regardless of how rigorous the actual assessment is. The best candidates, who have other options, are most sensitive to this. A process that runs to industry-average length but communicates well throughout will outperform a faster process that leaves candidates in silence for days at a time.

Let's start with a confession.

Time to hire is one of the most widely tracked metrics in recruitment. It's on dashboards everywhere. Hiring managers ask about it. Leadership teams report it to boards. And a surprising number of the people tracking it are calculating it differently from the people sitting next to them.

Same metric. Different definitions. Different start dates. Different interpretations of what "hired" actually means. And therefore different numbers that are confidently presented as if they mean the same thing.

This matters more than it might seem. If you're benchmarking your time to hire against industry data, but your calculation starts from a different point than the benchmark does, you're not comparing like with like. If two teams in the same organisation are measuring differently, you can't compare their performance. And if your definition shifts — even slightly — between reporting periods, your trend data becomes meaningless.

So before we get into what a good time to hire metric looks like, let's get the formula right. All of it. Including the bits that seem obvious but turn out not to be.

The Time to Hire Formula

The basic formula is straightforward.

Time to Hire = Date of Offer Acceptance − Date Candidate Entered Pipeline

That's it. The number of calendar days between a candidate first appearing in your recruitment process and that candidate accepting an offer.

If a candidate applied on the 1st of March and accepted an offer on the 22nd of March, their time to hire is 21 days.

To calculate average time to hire across multiple roles, you add up the individual time to hire figures and divide by the number of hires.

Average Time to Hire = Sum of All Individual Times to Hire ÷ Number of Hires

So if three hires had time to hire figures of 21 days, 34 days, and 28 days, your average is 27.6 days.

Simple. And yet here's where it immediately gets complicated.

The Definitions You Need to Agree Before the Formula Means Anything

The formula has two variables. Both of them sound obvious. Neither of them is.

You may also want to click here to compare time to hire vs. time to fill.

What counts as "entering the pipeline"?

This is the one that trips up most teams, because there are at least four reasonable options — and the one you choose significantly affects your number.

Option 1: Application date. The candidate submits an application. The clock starts. Clean, simple, easy to pull from an ATS. The problem is that it includes time spent in the inbox before anyone looked at the application — which is real time, but it measures how quickly you reviewed applications rather than how quickly you processed a known candidate.

Option 2: Application reviewed / shortlisted. The clock starts when a recruiter actively engages with the application — either marking it for review or moving it to shortlist. This removes inbox waiting time, which some teams argue is a sourcing problem rather than a process problem. The counter-argument is that a candidate doesn't experience it that way. They submitted an application. Time started for them.

Option 3: First contact made. The clock starts when the recruiter first reaches out to the candidate — whether that's a screening call invite, an email, or a LinkedIn message to a sourced candidate. This is often used by teams doing proactive sourcing where "applying" isn't the entry point.

Option 4: Screening call or first interview completed. Some organisations start the clock at the first substantive interaction. This dramatically compresses the headline metric and also, frankly, flatters it. We'd suggest this is the least defensible option if you're trying to give candidates or leadership an honest picture of process speed.

There's no single correct answer. The right choice depends on your process and what you're actually trying to measure. But you have to pick one, write it down, and apply it consistently. Anything else produces numbers that can't be tracked over time or compared across teams.

What counts as "offer accepted"?

This one seems more obvious and is slightly less contentious — but still worth nailing down.

Is it the date the verbal offer was made? The date the candidate verbally accepted? The date the written offer was sent? The date the signed contract was returned?

Most teams use verbal offer acceptance, which represents the point at which the candidate has committed and the hiring decision is effectively made. Using signed contract returns adds days that are largely outside your control — depending on notice periods, candidate circumstances, and how long your HR team takes to generate paperwork.

Pick a definition, document it, stick to it.

How Is Time to Hire Measured in Practice?

In theory, it's pulled automatically from your ATS. Most modern applicant tracking systems log timestamps at every pipeline stage, which means the raw data for calculating time to hire and average time to hire should be sitting there already.

In practice, the data is often a mess.

Here's what tends to go wrong.

Inconsistent stage entry.

Some recruiters update candidate stages in real time. Others do it in batches at the end of the week. Some forget until someone asks for a report. The timestamps in the ATS reflect when the system was updated, not when the event actually happened — and those two things are often days apart.

‍

Sourced candidates logged late.

When a recruiter sources a candidate proactively — via LinkedIn, a referral, an event — that candidate often gets added to the ATS at a later stage than they were actually first contacted. The clock starts later than it should, which flatters the metric.

‍

Withdrawn candidates excluded by default.

Most ATS reporting on time to hire only covers candidates who were hired. Candidates who withdrew during the process — often the most important signal about candidate experience — don't appear in the calculation at all. Your average looks better than it is because it's averaging only the outcomes that reached a conclusion.

‍

Multiple roles conflated.

If you're averaging time to hire across a graduate entry-level role and a Chief Technology Officer search in the same number, the average is technically correct and practically useless.

‍

None of this means the data isn't worth collecting. It means it needs auditing before it's trusted, and that someone needs to own data quality in the ATS rather than assuming the system is taking care of it.

What Is a Good Time to Hire Metric?

The honest answer: it depends on the role, the sector, and the labour market at the time you're hiring.

The slightly more useful answer: here's the context you need to interpret it.

LinkedIn's data consistently puts average time to hire across professional roles at somewhere between 28 and 42 days, with meaningful variation by sector and seniority. Technology, engineering, and senior leadership roles skew higher — 45 to 70 days is not unusual. High-volume, entry-level roles in retail or hospitality can move in under two weeks.

Industry benchmarks for time to hire are a starting point, not a standard. Here's what a good time to hire metric actually looks like in practice.

‍

It's consistent with your own historical average.

More useful than any external benchmark is knowing whether your own number is improving, static, or getting worse over time. Directional movement tells you whether your process changes are working.

‍

It varies sensibly by role type.

A single company-wide average that blends graduate hires with senior appointments tells you almost nothing. Segment by level, by function, by hiring manager. That's where the actionable insight lives.

‍

It's correlated with quality of hire.

This is the check that most teams skip. If your time to hire dropped by ten days last quarter, that's good. If your quality of hire also dropped, your speed improvement came at a cost. If quality held or improved, you've actually made progress.

‍

It reflects completed processes, not abandoned ones.

If a string of roles are taking 70+ days because candidates are dropping out and you're restarting from scratch, your average time to hire might still look reasonable while the process is quietly broken. Track restarts and withdrawals separately.

‍

A good time to hire metric is one that's consistently defined, segmented meaningfully, and read alongside quality indicators rather than in isolation. A single average figure, reported quarterly, without any of that context, is a number that makes the dashboard look tidy without telling you anything particularly useful.

Calculating Time to Hire Across Multiple Hires

If you want your average time to hire to be genuinely meaningful — the kind that surfaces real problems and tracks real improvement — here's a more robust approach than a simple mean average.

Segment before you average.

Calculate separate averages for different role types, seniority bands, business functions, and hiring managers. The differences between these segments are usually more informative than the overall number.

‍

Track median alongside mean.

A single slow hire — a six-month search for a rare specialist, say — can pull your mean average significantly higher without reflecting typical process performance. The median (the middle value in your dataset) is less sensitive to outliers and often gives a better picture of what's normal.

‍

Track time spent at each stage, not just end-to-end.

Most ATS tools can give you this breakdown. Stage-level data tells you whether delay is concentrated at a specific point in the process — offer stage, second interview scheduling, feedback loop — rather than spread evenly across everything. That's the data that enables targeted fixes rather than vague process reviews.

‍

Include withdrawals in your analysis, even if not in the headline metric.

Track at which stage candidates are withdrawing, and how long they'd been in the process when they did. Candidates who withdraw after 25 days of silence between stages are telling you something that your average time to hire won't.

How SquareLogik Handles Time to Hire Data

We think about time to hire as a diagnostic tool rather than a reporting metric.

A number on a dashboard is only useful if it tells you something you can act on. Which means we're less interested in what the average is and more interested in where time is accumulating, whether candidates are having a smooth experience while it does, and whether the speed of the process is correlating with the quality of the outcomes.

In practice, that means we agree definitions upfront with clients — exactly when the clock starts, exactly what counts as an offer acceptance, exactly how we'll segment and review the data — before we start tracking anything. Because a metric built on inconsistent definitions is just decoration.

We also track alongside quality of hire, so that any improvement in time to hire can be evaluated for what it actually produced, not just how fast it happened.

If you're finding that your time to hire data is difficult to interpret, inconsistent across teams, or hard to connect to any meaningful outcome — that's a fairly common situation, and it's usually more fixable than it looks.

Connect with us to learn more.

Frequently Asked Questions

What is the formula for time to hire?

Time to hire equals the date of offer acceptance minus the date the candidate entered the recruitment pipeline, measured in calendar days. To calculate average time to hire, add up the individual time to hire figures for all hires in a given period and divide by the total number of hires. The formula itself is simple — the complexity lies in agreeing a consistent definition of when the pipeline starts, which affects your number significantly.

‍

How is time to hire different from time to fill?

Time to hire starts when a specific candidate enters your recruitment pipeline and ends when they accept an offer. Time to fill starts when the job requisition is opened — before any candidate exists — and ends at the same point. Time to fill is always longer because it includes the pre-pipeline period: job approval, writing and posting the role, and waiting for applications. Time to hire measures process efficiency. Time to fill measures total vacancy cost and workforce planning accuracy.

‍

What is a good time to hire metric?

For most professional roles, 28 to 42 days is broadly typical, though this varies significantly by sector, seniority, and current labour market conditions. Technical and senior roles routinely run longer. More important than hitting an industry benchmark is whether your own metric is improving over time, whether it varies sensibly across role types, and whether it correlates with quality of hire. A falling time to hire that's accompanied by falling quality of hire isn't progress — it's just faster mistakes.

‍

What should I include in the time to hire calculation?

Calendar days from when a candidate first enters your pipeline to when they accept an offer. The key decisions are: what counts as entering the pipeline (application date, first contact, first interview) and what counts as acceptance (verbal or signed contract). Both need a clear, documented definition applied consistently across every hire. If different teams are using different definitions, your company-wide average is an average of incomparable numbers, which is less useful than it sounds.

‍

Why does my time to hire data look inconsistent?

Usually one of three reasons. First, inconsistent stage updates in the ATS — recruiters logging events at different times creates timestamp errors. Second, sourced candidates being added to the system later than they were first contacted, which shortens the apparent pipeline time for those hires. Third, different teams using different definitions for when the clock starts. An ATS audit and a shared, written definition of the metric will fix most of this.

‍

Should I use mean or median to report average time to hire?

Both, ideally. The mean average is more commonly reported but sensitive to outliers — one unusually long search can inflate it significantly. The median (the middle value in your dataset) gives a better picture of what's typical for most hires. For meaningful benchmarking, report both and note when the gap between them is large, which usually signals that a small number of slow or unusual searches are distorting the overall picture.

‍

How does time to hire affect candidate experience?

Significantly. From a candidate's perspective, the clock starts the moment they apply or are contacted. Long gaps between stages — even if the total process is within a reasonable range — signal disorganisation, poor communication, or indifference. The best candidates, who typically have multiple options, are most sensitive to this. Tracking time to hire at the stage level, rather than just end-to-end, helps identify where the candidate experience is breaking down before it starts costing you the people you actually wanted.

Every week, somewhere, a great candidate accepts a job offer.

Not yours. Someone else's. Because yours took 11 days longer to arrive.

The hiring manager is frustrated. The recruiter is frustrated. And somewhere, a candidate who would have been excellent is now onboarding at a competitor, relieved they didn't have to sit through a fifth interview round to find out if they got the job.

This is not a rare edge case. It's one of the most common and most preventable ways organisations lose the people they actually want.

But most slow hiring processes aren't slow because of anything particularly difficult.

They're slow because of a collection of small, fixable inefficiencies that nobody has ever sat down and properly examined.  

• A week lost here waiting for a hiring manager to review CVs.  
• Three days there because nobody could agree on an interview slot.  
• A fortnight at the offer stage because three people needed to sign something and one of them was in Singapore.

None of that is assessment. All of it is delay.

This article is about telling the difference — and fixing the delays without gutting the rigour that makes a hire actually good.

First, Understand Where Your Time Is Actually Going

Before you can reduce your average time to hire, you need to calculate time to hire to know where it's being spent. And most organisations genuinely don't know.

They have a headline number. They might know it's 38 days, or 52 days, or an embarrassing 74 days for that one role that shall not be named.  

What they often don't have is a breakdown of what happened during those days.

Was the time spent on genuine assessment — interviewing candidates, deliberating thoughtfully, making good decisions?  

Or was it spent waiting? Waiting for a hiring manager to respond to an email. Waiting for a calendar to open up. Waiting for a verbal offer to become a written one. Waiting for an approval chain that nobody has questioned in six years.

Pull your ATS data and map it by stage. Where are candidates spending the most time? Where are they dropping out? Where does the clock just... run, with no meaningful activity attached to it?

That map is where your time to hire improvement plan starts.  

Not in adding an AI tool or redesigning your careers page, but in understanding the specific places where your process currently grinds to a halt and asking, quite simply, why.

The Brief Problem, In Brief

Here's a reason hiring is slow that rarely makes it onto any list of time to hire tips: the brief is wrong.

Not wrong in an obvious way. Wrong in a subtle, nobody's-quite-noticed way.  

The job description was written months ago for a slightly different version of the role. The hiring manager wants one thing, the job ad is promising another, and the recruiter is screening for a third. Candidates who look great on paper get to interview stage and turn out not to be what anyone had in mind.

So the pipeline stalls. More candidates are sourced. More first interviews happen. Time passes.

A sharp, specific, genuinely agreed brief — one that defines not just skills and experience but what success looks like in the first six months — compresses hiring timelines faster than almost anything else. Because when everyone knows what they're looking for, decisions get made faster, candidates get assessed against the right criteria, and fewer people make it to the final stage only to be rejected for reasons that should have been screened for at the start.

It takes maybe two hours of proper upfront conversation to nail a brief. Most organisations skip it and spend six weeks compensating.

How to Improve Time to Hire: Fix the Gaps, Not the Stages

Most advice on reducing time to hire focuses on the stages — reduce the number of interview rounds, streamline your assessment, move faster through the funnel. And yes, there's something to that.

But in most hiring processes, the stages aren't the problem. The gaps between them are.

Consider a fairly typical process: application review, screening call, first interview, second interview, offer. Five steps. On paper, that's not excessive. Now consider what typically happens between each of those steps.

The application sits in an inbox for four days before anyone reviews it. The screening call is booked for six days after the application is approved because the recruiter's calendar is full. Feedback from the first interview takes three days to compile because the hiring manager is travelling. The second interview takes another ten days to schedule because it involves three people who are never free at the same time. The offer takes a week to generate because it needs finance sign-off.

That's a five-stage process that runs to 45 days — not because any single stage is bloated, but because the spaces between them are full of entirely avoidable waiting.

Fix the gaps. Set internal SLAs for feedback turnaround — 24 to 48 hours after an interview, not whenever feels convenient. Block hiring manager time for interviews in advance rather than scheduling reactively. Have offer templates ready so that a verbal yes can become a written offer within 24 hours.

None of this requires fewer interviews. None of it compromises assessment quality. It just eliminates the dead time that's currently making your candidates feel like they've applied to the Bermuda Triangle.

The Feedback Loop Problem

Slow feedback kills more hiring processes than bad candidates do.

When a candidate attends an interview and then hears nothing for a week, two things happen. First, they assume the answer is no and start warming up their other options. Second, even if they're still interested, their enthusiasm has taken a hit. The employer who was exciting two weeks ago is now the employer that leaves people hanging.

Good candidates — the ones who are currently employed and performing well, the ones with other offers on the table — do not wait indefinitely for news. They move. And they tell people about the experience, which has its own long-term cost to your employer brand.

The fix is mundanely simple: set a maximum feedback window and stick to it. 48 hours after every interview stage. Positive or negative, substantive or brief, the candidate hears something. Even "we're still deliberating and expect to have an update by Thursday" is infinitely better than silence.

This doesn't require extra headcount or a new system. It requires someone owning the communication and it being treated as non-negotiable rather than best-efforts.

Structured Interviews: Faster Decisions, Better Outcomes

One of the quieter contributors to inflated time to hire is decision-making that goes in circles.

It usually goes like this. Three people interview a candidate. Each of them had a slightly different idea of what they were assessing. Nobody used a consistent scoring framework. Post-interview, one person loved the candidate, one is lukewarm, and one has concerns that turn out to be about something the other two didn't even ask about. A follow-up conversation is needed. Maybe a third interview. Time passes.

Structured interviews — where every candidate is asked the same core questions, evaluated against the same criteria, and scored before the debrief conversation — don't just improve quality of hire. They dramatically speed up decision-making.

When everyone is evaluating against the same framework, debriefs are shorter. Disagreements are productive rather than circular. Decisions happen faster because there's an agreed basis for making them.

Setting up a structured interview framework for a role takes a few hours. It then saves time on every single hire. The maths is fairly compelling.

Reducing Interview Stages without Overcorrecting

Right, let's talk about interview stages, because this is where people tend to go immediately — and also where they tend to overcorrect.

More stages does not mean more rigour. It often means more opportunity for scheduling delays, more chances for a good candidate to have an off day, and a growing suspicion from candidates that your organisation struggles to make decisions.

The question to ask about every stage in your process is: what information does this give us that we don't already have? If the answer is "roughly the same information as the previous stage, but slightly different people were in the room," that stage is not earning its place.

A well-designed three-stage process — screening, structured competency interview, hiring manager conversation — will outperform a five-stage process built by accumulation over the years, where each stage was added for a reason that may or may not still exist.

Audit your stages. For each one, write down what it's supposed to assess. If you can't articulate a clear answer, the stage is probably doing more to inflate your time to hire than to protect your quality of hire.

Using AI and Automation for the Repetitive Parts

Let's be direct about what AI recruitment tools are actually good at.

• They are good at processing high volumes of applications quickly and consistently.  
• They are good at scheduling.  
• They are good at sending timely communications so candidates don't feel like their application has vanished into a void.  
• They are good at surfacing candidates who match a defined profile from a large pool, without the fatigue-related inconsistency that comes from a human reviewing CV number 73 on a Tuesday afternoon.

They are not, currently, good at the parts of hiring that require genuine contextual judgement.  

• Assessing whether someone's experience translates to a different industry.  
• Reading the room in a complex interview.  
• Deciding whether a candidate's unconventional background is a risk or an advantage.  
• Making the kind of holistic call that experienced recruiters make — and sometimes get wrong, but make with a quality of reasoning that no algorithm currently replicates.

The practical implication for reducing time to hire is this: use AI and automation to compress the stages where volume and consistency matter. Initial screening, first-pass matching, scheduling, candidate communications, interview reminders.  

This can realistically take two to three weeks off a typical process, purely by eliminating the administrative drag at the top of the funnel.

That's time reclaimed without compromising a single assessment stage. Which is, to be honest, where you want the time saving to come from.

Pre-Approved Offers and Internal Sign-Off

You've run a great process. Your preferred candidate is ready to say yes. And then the offer takes ten days to materialise because finance needs to approve the salary, legal needs to check the contract, and someone senior who wasn't involved in the process needs to review the whole thing before it goes out.

This is one of the most frustrating and most preventable sources of delay in the entire hiring process. And it happens after all the actual recruitment work is done.

The fix is boring but effective: agree salary bands, notice period expectations, and standard contract terms in advance, before the process begins.  

If an offer falls within pre-approved parameters, it should be signable within 24 to 48 hours of a verbal acceptance. Anything that routinely requires additional sign-off needs either a faster sign-off chain or a reconsideration of who has approval authority.

Candidates who've said yes verbally and then wait ten days for paperwork occasionally change their minds. Not often. Often enough.

Build Talent Pipelines Before You Need Them

Here's the most effective way to reduce average time to hire, and also the one that requires the most patience to implement: stop starting from zero every time a role opens.

When a vacancy opens and the sourcing starts at that moment, the time to fill clock starts running before a single candidate is in the pipeline. Depending on the role, it might be weeks before a qualified shortlist exists.

Organisations that maintain warm talent pipelines — pools of previously assessed or engaged candidates who have expressed interest in the organisation — can compress this entirely. When the role opens, the first outreach goes to people who already know you, who've already been through some level of assessment, and who may be ready to move.

This isn't about keeping people on the hook indefinitely. It's about building genuine relationships with candidates who might be right for future roles — through employer brand content, recruiter relationships, alumni networks, and staying in touch with strong candidates who weren't quite right for the last role but might be exactly right for the next one.

For high-frequency or business-critical roles especially, a maintained talent pipeline is worth more than any process optimisation. It turns weeks of sourcing into days.

How SquareLogik Approaches Time to Hire

We've seen all of these problems from the inside.

• Unclear briefs that sent sourcing in the wrong direction for three weeks.  
• Feedback loops that stretched to double digits.  
• Offer sign-off chains that were added for good reason years ago and never removed when circumstances changed.
• Excellent candidates who accepted somewhere else on day 28 of a process that eventually produced an offer on day 36.

What we try to do is treat time to hire as a diagnostic rather than just a metric.  

We want to know what's driving the number — because a 45-day time to hire caused by a complex, well-designed assessment process is a very different thing from a 45-day time to hire caused by a hiring manager who hasn't prioritised it.

In practice, that means starting every engagement with a proper brief, building in communication SLAs from day one, using AI to compress the administrative drag at the top of the funnel, and staying close enough to the process to catch the gaps before they become problems.

If your hiring is slower than it should be and you'd like a second pair of eyes on where the time is going, we're happy to have that conversation. Click here to connect with us.

Frequently Answered Questions

What is the fastest way to reduce time to hire?  

Fix the gaps between stages before touching the stages themselves. Most inflated time to hire comes from delays in feedback, interview scheduling, and offer generation — not from having too many assessment steps. Setting 48-hour feedback SLAs, pre-blocking hiring manager interview availability, and having offer templates ready for pre-approved roles can realistically compress time to hire by one to two weeks without removing a single assessment stage or increasing hiring risk.

‍

Does reducing time to hire affect quality of hire?  

It can, but it doesn't have to. Hiring quickly by compressing or skipping assessment stages is a false economy — it saves weeks and costs months in underperformance and re-hiring. But hiring quickly by eliminating administrative delays, speeding up feedback loops, and improving scheduling efficiency saves time without affecting quality at all. The difference is in where the speed comes from. Compress the waiting. Protect the assessment.

‍

How many interview rounds is too many?  

There's no universal answer, but a useful rule is that every stage should produce information you don't already have. If a third or fourth round is assessing largely the same competencies as earlier stages, it's adding delay without adding insight. Most professional roles can be thoroughly assessed in two to three well-structured stages. Beyond that, additional rounds tend to reflect decision-making anxiety rather than genuine assessment need — and they cost you candidates who won't wait that long.

‍

How do talent pipelines help reduce time to hire?  

A warm talent pipeline means you're not starting from zero when a role opens. If you've maintained relationships with previously assessed candidates who've expressed interest in your organisation, the sourcing phase — which can account for two to four weeks of total time to fill — is either compressed or eliminated entirely. For high-frequency or business-critical roles, proactive pipelining is one of the highest-return investments a talent acquisition team can make.

‍

How can AI help reduce time to hire?  

AI is most effective at compressing the administrative stages of recruitment — initial CV screening, candidate matching, interview scheduling, and automated communications. These stages can account for a significant portion of total time to hire, particularly for high-volume roles. Used well, AI can take two to three weeks off a typical process without touching any of the human assessment stages. The caveat is that AI tools require a clear, well-defined brief to work from — automate a vague process and you'll just produce vague results faster.

A business complains that hiring is taking too long.  

You pull the data.

The numbers look reasonable — average time to fill is sitting around 35 days, which is broadly in line with industry benchmarks. You report back. Everyone nods. The problem is apparently not that bad.

And yet. The engineering team is still waiting on someone they needed six weeks ago. Three candidates dropped out mid-process last month. The offer that finally went out last Tuesday took nine days to get sign-off on.

Something is wrong. The metrics say otherwise. And the disconnect is quietly driving everyone mad.

This is often what happens when time to hire and time to fill get used interchangeably. They sound like the same thing. They measure different things. And if you're tracking one when you should be tracking the other — or tracking both but not understanding what each one means — you end up optimising for a number that isn't telling you what you think it is.

Let's sort this out.

What Is Time to Fill?

Time to fill measures the number of days between a job requisition being opened and an offer being accepted.

It starts the moment someone officially approves the need to hire — the job requirement is signed off, the headcount is confirmed, the vacancy is open. It ends when a candidate accepts an offer.

Everything in between counts. The time it takes to write and post the job. The time before the first applications come in. Every stage of the interview process. The time spent deliberating. The offer stage. All of it.

Time to fill is a business planning metric. It answers the question: from the moment we decided we needed someone, how long until we had someone?

That's useful for workforce planning, for setting expectations with hiring managers, and for calculating the true cost of a vacancy. If you need to hire a Head of Finance and you know your average time to fill for senior roles is 60 days, you can plan accordingly. Or at least stop promising the CFO that it'll be wrapped up by end of month.

What Is Time to Hire?

The calculation for time to hire measures the number of days between a specific candidate entering your recruitment pipeline and that candidate accepting an offer.

Same endpoint. Very different starting line.

Time to hire doesn't care when the job was posted or how long the vacancy sat open before the first decent application came in. It starts the clock on a specific person — typically from the moment they applied, or were sourced, or made first contact with your process. It ends when they say yes.

Time to hire is a candidate experience metric and a process efficiency metric. It answers a different question: once we had a good candidate in the pipeline, how quickly and smoothly did we move them through?

That's useful for diagnosing where your process loses people, how competitive you are on speed relative to other employers those candidates are talking to, and whether your assessment stages are proportionate or padded.

Why the Difference Actually Matters

If time to fill is slow, the problem might have nothing to do with your recruitment process.

• Maybe the headcount approval took three weeks because two senior leaders were on holiday.  
• Maybe the job description sat in a queue waiting for sign-off before it could be posted.  
• Maybe the role had budget uncertainty that delayed the official open date by a fortnight.  None of that is a recruitment problem. It's an internal governance problem. And no amount of streamlining your interview process will fix it.

If time to hire is slow, the problem is almost certainly inside the process.  

• Scheduling delays.  
• Slow feedback loops between stages.  
• Too many interview rounds.  
• An offer that takes a week to generate and another week to get approved.  

These are things you can actually fix.

The reason it matters to separate them is that they point at completely different root causes. Conflating them means you end up auditing your interview process when the real blockage is a two-week approval chain that nobody has ever questioned. Or the reverse — you renegotiate headcount approval timelines while your candidates are dropping out mid-process because nobody's following up between stages.

Fix the right thing. Use the right metric.

The Hidden Time That Neither Metric Captures

Both metrics have a blind spot. Neither of them tells you what's happening in the gaps.

Time to fill captures the full elapsed period but doesn't tell you which parts of that period involved meaningful activity and which parts were just... waiting. Time to hire captures process speed but only for the candidates you actually tracked properly — which, in most ATS systems, means the ones who made it far enough into the pipeline to have a proper record.

The gaps are where the real problems hide.

• The three days between an interview and the feedback being shared with the candidate.  
• The week where the hiring manager was travelling and nothing moved.  
• The fortnight between the verbal offer and the written contract.  
• The candidates who withdrew before hitting any formal stage because nobody followed up after the screening call.

These gaps inflate both metrics without appearing in either one's narrative. And they're the most fixable part of the process, because they're usually not about assessment quality at all. They're about communication, scheduling, and internal accountability.

If you want to genuinely improve your hiring metrics, map the gaps. Not just the stages.

Time to Hire vs Time to Fill: How They Relate

Think of it like this.

Time to fill is the whole journey from "we need someone" to "we have someone." Time to hire is the sprint at the end — from "here's a candidate" to "they've accepted."

The difference between those two numbers is the time your process spent before a suitable candidate even appeared. That pre-pipeline period — job approval, job posting, waiting for applications, early-stage sifting — isn't captured by time to hire at all. It can represent days, weeks, or in some cases an embarrassingly large fraction of the total time to fill.

For most organisations, that pre-pipeline gap is one of the biggest drags on total time to fill. And it's almost entirely invisible if you're only tracking time to hire.

Meanwhile, time to hire on its own can look perfectly healthy even when candidates are having a genuinely poor experience — if you're only measuring the candidates who stayed in the process long enough to be tracked, you're missing the ones who dropped out or withdrew, who are arguably the most important signal of all.

Used together, the two metrics give you something neither can give you alone: a picture of where time is going across the whole hiring journey, not just the part that feels most like "recruiting."

What Good Looks Like for Each Metric

Benchmarks are tricky because they vary significantly by industry, seniority, and the labour market conditions at any given time. Anyone claiming a single universal benchmark for either metric is probably simplifying more than is useful.

That said, here's a rough orientation.

For time to fill, most professional roles across sectors average somewhere between 30 and 45 days. Technical and senior roles regularly run longer — 60 to 90 days isn't unusual for a Director-level hire or a specialist engineering role. If you're consistently above those ranges, it's worth investigating whether the delay is in the pre-pipeline phase or the process itself.

For time to hire, the picture is more compressed. Once a strong candidate is in your pipeline, most competitive processes move to offer acceptance within two to four weeks. Beyond that, you're testing the patience of candidates who have other options — and statistically, the ones with the most options are the ones most likely to quietly disappear.

For more information on time to hire benchmarks, click here to read the full report.

The more useful benchmark than any industry average, though, is your own historical data. Are your metrics improving? Are they consistent across teams and roles? Are there outliers that suggest specific problems rather than systemic ones? That's where the actionable insight lives.

Practical Ways to Track Time to Hire and Time to Fill

You don't need a sophisticated people analytics platform to track these properly. You need clear definitions and consistent data entry.

Start by agreeing what triggers the start of each metric in your organisation.  

• When exactly does the clock start for time to fill — requisition approval, budget sign-off, or job posting?  
• When does time to hire begin — application received, screening call completed, or first interview scheduled?  

There's no universally correct answer, but there needs to be a consistent one, applied across every hire, or the numbers aren't comparable.

Then track the stages between. Most ATS systems will log timestamps at each stage if your team is entering data consistently, which is a big if, but worth enforcing. The goal isn't just an end-to-end number — it's being able to see where time accumulates so you can do something about it.

Review both metrics together, by team, by role type, and by hiring manager. Patterns at that level of granularity are far more useful than company averages. If one hiring manager's roles consistently show inflated time to hire, that's a different conversation than if one department's time to fill is long because headcount approval always stalls at the same sign-off level.

You may also want to check out our tips to reduce time to hire. Click here to read the full article.

How Squarelogik Looks at Both

When we work with a new client, one of the first things we try to understand is where their time is actually going.

Not just the headline numbers — those are useful context but rarely diagnostic on their own. We want to know whether delay is accumulating before the pipeline exists or inside it. Whether candidates are withdrawing at a particular stage. Whether offers are being extended at a speed that's competitive for the market and the role. Whether the gap between "verbal yes" and "signed contract" is adding unnecessary risk at the end of an otherwise efficient process.

Both metrics together, tracked at the stage level, give you an honest map of your hiring process — not just how long it takes, but where it's working and where it isn't.

If you're finding that your numbers look fine on paper but hiring still feels like it takes forever, that's usually a sign that the right metrics aren't being tracked, or that something significant is happening in the gaps between them.

That's a solvable problem. And it's usually a more interesting conversation than the headline numbers suggest.

Frequently Asked Questions

What is the difference between time to hire and time to fill?

Time to fill measures the days between opening a job requisition and a candidate accepting an offer — it covers the entire hiring journey including pre-recruitment delays. Time to hire measures the days between a specific candidate entering your pipeline and accepting an offer. Same endpoint, different starting point. Time to fill tells you about business planning efficiency. Time to hire tells you about process efficiency and candidate experience. You need both to understand where your hiring is losing time.

‍

Which is more important: time to hire or time to fill?

Neither is more important — they answer different questions. Time to fill matters more for workforce planning and understanding the true cost of vacancies. Time to hire matters more for diagnosing process bottlenecks and candidate drop-off. If you're only tracking one, you're likely misidentifying where problems originate. An organisation with a slow time to fill but healthy time to hire probably has an internal approval or job-posting problem, not a recruitment process problem.

‍

What is a good time to fill benchmark?

For most professional roles, 30–45 days is broadly typical, though this varies significantly by sector, seniority, and current labour market conditions. Technical and leadership roles regularly run 60–90 days. The more useful comparison is your own historical data — whether your numbers are improving, and whether there are meaningful differences between teams, roles, or hiring managers that suggest specific rather than systemic problems.

‍

What is a good time to hire benchmark?

Once a strong candidate is in your pipeline, most competitive processes move to offer acceptance within two to four weeks. Beyond that, you risk losing candidates to employers who move faster. The most relevant benchmark is how quickly your competitors are moving for the same candidate profiles — which varies by market and role type. Consistent tracking of your own data over time is more useful than chasing an industry average.

‍

Why do candidates drop out during the hiring process?

Usually one of three things: they received and accepted another offer, the process took longer than their patience allowed, or something in the experience made the employer less attractive than it seemed at the start. Time to hire is the most direct lever here — the longer candidates wait between stages, the more likely they are to accept something else. But communication matters too. A fast process with poor communication can lose candidates just as effectively as a slow one.

‍

Can you track time to hire and time to fill in an ATS?

Yes, most modern applicant tracking systems log timestamps at each pipeline stage and can report on both metrics. The challenge is data quality — the system can only report accurately if your team is entering data consistently, using agreed definitions for when each metric starts and ends. Before pulling reports, it's worth auditing whether your ATS data is actually reliable, particularly for candidates who withdrew early or were sourced rather than applied directly.

Most companies have no idea whether their hiring is actually working.

They know how long it takes. They know what it costs. They might even know how many people left in the first year, if someone remembered to write it down.

But whether the people they hired were actually good? Whether those hires moved the needle, built something, made the team better? That part tends to live in a vague, untracked space between "seemed fine in the interview" and "we'll review it at the end of the year."

That space has a name. It's called quality of hire. And it's arguably the most important metric in recruitment.

But quality of hire is also one of the hardest metrics to measure well. Which is probably why most companies avoid measuring it at all, and instead optimise for things that are easier to count.

This guide is about fixing that.

So What Does "Quality of Hire" Actually Mean?

Quality of hire measures how much value a new employee adds to your organisation relative to what you expected when you hired them.

That's the simple version.  

The slightly more complicated version is this: quality of hire tells you whether the people you're selecting are actually performing the way you thought they would when you decided to hire them.

High quality of hire means your new employees hit the ground running, stick around, earn the respect of their managers, and do what the job actually requires.  

Low quality of hire means you're spending months managing underperformance, backfilling roles that should've been filled right the first time, and having awkward conversations about "fit" that nobody enjoys.

It sounds obvious when you put it like that. And yet.

Why Quality of Hire Is So Difficult to Track

Because it involves things that are genuinely hard to quantify.

Performance is subjective. Different managers have different standards. What counts as "exceeding expectations" in one team is table stakes in another.  

And without a consistent framework for measuring it, you end up comparing feelings rather than data.

There's also a time problem. You often don't know whether a hire was a good one until six, twelve, sometimes eighteen months after they've started. By which point the hiring manager has moved on, the original brief has been rewritten twice, and nobody can quite remember what "good" was supposed to look like in the first place.

And then there's the attribution problem. Was the hire underperforming...  

• Because you recruited the wrong person?  
• Because the onboarding was poor?  
• Because the role changed and nobody told them?
• Because their manager is, diplomatically, not great at managing people?  

Quality of hire sits at the intersection of all of these things, which makes it easy to dispute and easy to ignore.

None of this means you shouldn't try. It just means you need to be honest about what you're measuring and why.

The Quality of Hire Formula

There isn't one universally agreed quality of hire formula, which tells you something about the state of the field.

The most commonly used approach combines several indicators into a single score. A popular version looks something like this:

Quality of Hire = (Performance Score + Retention Rate + Hiring Manager Satisfaction) ÷ Number of Indicators

So if a hire scores 80% on performance, 90% on retention probability, and 70% on hiring manager satisfaction, their quality of hire score is roughly 80%.

Simple enough.  

The challenge is that each of those component scores needs its own measurement system, its own cadence, and its own definition of what "good" means before you can plug anything into the formula.

Which means the formula is only as useful as the inputs you put into it. Garbage in, a suspiciously clean-looking number out.

Some organisations add further components:  

• Speed to productivity (how long did it take for them to become fully effective?)
• Cultural contribution (harder to measure, but real)
• 360 feedback scores.  

The more components you include, the more complete the picture — and the more work it takes to maintain.

What Metrics Make Up Quality of Hire?

Let's go through the main ones and discuss what each of them does and doesn't tell you.

‍

Job Performance Ratings

This is the obvious one. How is the employee actually performing in their role?

The problem is that performance ratings are often inconsistent, infrequent, or both.  

• Annual reviews are too slow to catch early warning signs.  
• Manager bias is real and rarely controlled for.  
• And if you don't have a structured performance framework before someone starts, you're rating them against a standard you invented after the fact.

Done well, performance data is the most direct measure of hiring quality. Done badly — which is most of the time — it's anecdotal with a number attached.

‍

Retention and Early Attrition

If someone leaves within the first year, that's a signal. It might be a signal about the hire, about the onboarding, about the role itself, or about the manager.  

You need to know which.

Tracking first-year attrition by hiring source, hiring manager, and role type gives you patterns that individual exit interviews rarely surface.  

If one department consistently loses people in months three to six, that's a process problem, not a person problem.

‍

Time to Productivity

How long does it take a new hire to reach full effectiveness in their role?  

This varies enormously by role complexity, but setting a baseline expectation — and then tracking whether hires hit it — tells you something about both the quality of the hire and the quality of the onboarding.

A great hire in a badly structured onboarding process will still take longer than necessary to become productive. Time to productivity captures both factors, which means you need to control for onboarding quality before blaming the hire.

‍

Hiring Manager Satisfaction

Structured surveys at 30, 60, and 90 days. Simple questions:  

• Is this person meeting your expectations?  
• Are they performing at the level you anticipated?  
• Would you hire from this source again?

Hiring manager satisfaction is fast, cheap, and surprisingly predictive. The catch is that it needs to be structured and consistent — not a casual corridor conversation — or it becomes a measure of whether the hiring manager is having a good week.

‍

Offer Acceptance Rate and Candidate Quality

This one sits slightly upstream of the others.  

If you're consistently losing your preferred candidates before an offer is accepted, that affects your eventual quality of hire whether you track it or not. You're hiring from a pool that your first-choice candidates opted out of.

Tracking offer acceptance by candidate rank — whether the person who accepted was your first, second, or third choice — gives you an honest measure of whether your process is securing the candidates you actually want.

What a "Good" Quality of Hire Score Looks Like

Quality of hire scores are only meaningful relative to your own baseline. A score of 75% means nothing without knowing whether that's better or worse than your historical average, and whether it varies by role, team, or hiring source.

What you're looking for is directional improvement over time, and meaningful differences between segments.  

• If hires sourced through one channel consistently outperform hires from another, that's actionable.  
• If hires into one team consistently underperform, that's a conversation to have with that team's manager.  
• If quality of hire collapsed after a particular process change, that's a data point worth investigating.

The goal isn't a single impressive number. It's a feedback loop that makes each cohort of hires a little better than the last.

Why Most Companies Measure the Wrong Things Instead

This is the part where we have to be a bit direct.

Most companies measure time to fill and cost per hire because those metrics are easy to pull from an ATS and they make the recruitment function look busy and accountable.  

• They measure volume.  
• They measure speed.  
• They measure spend.

None of those things tell you whether your hiring is actually producing people who are good at their jobs and who stay.

The reason quality of hire gets deprioritised isn't that people don't value it. It's that measuring it requires coordination between recruitment, HR, and line management — three functions that, in many organisations, operate in near-complete isolation from each other:

• Recruitment closes the vacancy and hands over.  
• HR runs the contract and onboarding.  
• The line manager takes over.  

Nobody maintains a thread between those stages that connects back to what the hiring decision was and whether it was right.

Until you build that thread, quality of hire remains a thing that everyone agrees is important and nobody systematically tracks.

How to Actually Start Measuring Quality of Hire

You don't have to build Rome in a day. You also don't have to have a perfect system before you start.

But here's a sensible starting point.

Pick three metrics:  

• Performance rating at six months
• First-year retention
• Hiring manager satisfaction at 90 days.  

Define what "good" looks like for each before the person starts, not after. Track consistently for every new hire across a meaningful period — ideally twelve months minimum before drawing conclusions. Then look for patterns.

That's it. Three data points, collected consistently, reviewed honestly.  

It's not glamorous. But it is useful.

As your measurement improves, you can layer in time to productivity, offer acceptance rate by candidate rank, and whatever additional dimensions are relevant to your organisation.  

But start with something you can actually sustain, because an abandoned measurement system is worse than no measurement system at all. It just creates the illusion of rigour.

How AI Is Changing Quality of Hire Measurement

AI tools are increasingly being used to predict quality of hire before it happens — matching candidate profiles to high-performing employee data, flagging patterns in CVs and interview responses that correlate with retention and performance.

This is useful, but also limited.

Predictive tools can surface patterns that human screeners miss. They can process more data more consistently than any panel of interviewers. They can reduce certain kinds of bias, while introducing others if the training data reflects historical hiring decisions that were themselves biased.

The honest position is that AI improves the quality of the information available at the point of hiring. It doesn't replace the judgement call. And it doesn't remove the need to measure what actually happens after someone starts.

Quality of hire, ultimately, is a retrospective metric.  

You can use AI to make better predictions going in. But the measure itself requires looking back. Which means the infrastructure for collecting and acting on post-hire data isn't optional, even in a fully AI-assisted process.

How Squarelogik Approaches Quality of Hire

In our AI-powered recruitment process, we treat quality of hire as the whole point of the process, rather than the thing we'll check on eventually.

That means we define success criteria before we source — working with hiring managers to establish what a good hire actually looks like at three months, six months, and a year.  

It means we track post-placement data systematically, following up with both hiring managers and placed candidates at structured intervals.  

And it means we feed that data back into how we approach future roles, so that a bad outcome doesn't just disappear into the general noise.

When we're doing this well, the result is a process where the hiring brief, the sourcing strategy, the assessment, and the post-hire measurement are all pulling in the same direction.  

If your organisation is trying to get a handle on quality of hire and finding it harder than it should be, we're happy to talk through it. Connect with us today for free.

Frequently Asked Questions

What is quality of hire in simple terms?  

Quality of hire measures how good a new employee turns out to be relative to what you expected when you hired them. It combines factors like job performance, how long they stay, how quickly they become effective, and how satisfied their manager is. It's essentially your hiring process's report card — and unlike cost per hire or time to fill, it tells you whether all that effort and money actually produced the right person for the role.

‍

How do you calculate quality of hire?  

The most common approach averages several component scores — typically job performance rating, retention likelihood, and hiring manager satisfaction — into a single percentage. For example: (performance score + retention score + hiring manager satisfaction) ÷ 3. The formula varies by organisation, and the result is only as meaningful as the data going in. The real challenge isn't the maths — it's building consistent processes for collecting reliable performance and satisfaction data in the first place.

‍

What is a good quality of hire score?  

There's no universal benchmark because quality of hire scores are highly context-dependent. A score of 80% means very little without knowing your own historical average and how it varies across roles, teams, and hiring sources. What matters is directional improvement over time and meaningful differences between segments — which hires are performing better, from which sources, into which teams. Use your own data as the baseline rather than chasing an industry number.

‍

Why is quality of hire so difficult to measure?  

Three main reasons. First, the data takes time — you often don't know if a hire was good until six to twelve months in. Second, performance measurement is inconsistent in most organisations, making comparisons unreliable. Third, measuring quality of hire requires coordination between recruitment, HR, and line management — functions that often operate separately. It's not technically hard. It's organisationally awkward. Which is why most companies skip it and measure cost per hire instead.

‍

Can AI improve quality of hire?  

Yes, with caveats. AI tools can improve quality of hire by screening more consistently, surfacing patterns that predict performance, and reducing certain types of bias in early-stage assessment. What AI cannot do is measure quality of hire retrospectively — that still requires structured post-hire data collection. And AI predictions are only as good as the data they're trained on. If your historical hires reflected biased decisions, an AI trained on that data will replicate those patterns more efficiently. Human oversight remains essential.

There's a particular kind of meeting that HR managers know well.

Someone from the senior leadership team pops their head in — or, more likely, fires off an email at 7:43am — to ask why a particular role still hasn't been filled.  

The tone implies that hiring, like ordering a takeaway, should really only take twenty minutes. And the subtext is clear: go faster.

The problem is that the same organisation tracking time to hire as a key metric is also tracking quality of hire. And if you've spent any time in talent acquisition, you'll already know the truth lurking at the intersection of those two dashboards:  

When you rush, you regret.

But here's where it gets interesting — and where the received wisdom starts to fall apart. Hiring slowly doesn't automatically produce better hires either.  

In fact, a bloated, multi-stage, committee-by-committee process has its own spectacular failure modes. The best candidates accept other offers. Hiring managers lose enthusiasm. And by the time someone actually starts, the role has subtly changed and nobody's told the recruiter.

So the real question isn't "fast or slow?" It's "what's actually driving your hiring timeline, and what is that doing to the quality of the people you bring in?"

What Time to Hire Actually Measures (And What It Doesn't)

Before we can talk about the relationship between time to hire and quality of hire, it helps to be precise about what time to hire is actually measuring.

Most organisations define it as the number of days between a candidate entering the pipeline — usually by applying or being sourced — and accepting an offer.  

Some companies measure time to fill instead, which starts the clock from when the vacancy opens, and captures the delay before any recruitment activity even begins. These are different things, and conflating them leads to fixing the wrong part of the process.

What time to hire doesn't tell you is anything about the quality of what happened during that period.  

You could move a candidate through six stages in fourteen days and make an excellent hire. You could drag someone through the same six stages over three months and make the same hire, or a worse one. The clock is running either way, and it's not judging you.

That's worth keeping in mind. Time to hire is a proxy metric. It gestures at efficiency. What it cannot tell you is whether your efficiency is producing the right outcomes.

Hiring Fast: The Rush-to-Hire Problem

Here's a scenario that will be familiar to anyone who has sat in a post-mortem meeting for a failed hire.

A role has been open for six weeks. The business is restless. There have been three rounds of interviews. The two strongest candidates both accepted offers elsewhere during the second week of deliberation. The remaining shortlist is fine. Nothing exceptional, nothing disqualifying. And so, under pressure to close the vacancy, an offer goes out to the most acceptable option.

Six months later, performance issues emerge. Or the person leaves. Or, worst of all, they stay and quietly underperform in ways that are just below the threshold for action.

This is not a story about hiring quickly per se.  

It's a story about what happens when timeline pressure overrides judgement at the decision-making stage. The hire was rushed, but the rush happened at the wrong moment — at the point where rigour matters most.

Genuinely rushed hiring tends to manifest in a few specific ways:

• Assessment stages get compressed or dropped.  
• Reference checking becomes perfunctory.  
• The brief isn't revisited even when it's clearly not matching the available market.  
• Interviewers haven't calibrated on what "good" looks like, so they're essentially voting on gut feel with a time limit attached.

The consequence isn't always immediate. Occasionally, a fast hire works out brilliantly. But the risk profile is poor, and over a portfolio of hires, the pattern is consistent: compress the quality of the process and you compress the quality of the outcome.

Hiring Slow: The Other Side of the Problem

Now, in the spirit of balance — and because it's true — let's talk about the opposite failure.

Long hiring processes are not automatically thorough hiring processes. They are often merely slow ones.

A four-month time to hire, with five interview stages, a take-home task, a panel presentation, and a psychometric assessment, can still produce a terrible hire. It can also  cause you to lose excellent candidates who simply can't or won't wait.

The best candidates, statistically speaking, are usually candidates who are already employed and performing well. They are not, as a rule, sitting by the phone in breathless anticipation of your third interview invitation. They have leverage, options, and a reasonable limit to their patience.  

And then there's the question of what all those extra stages are actually measuring. Research on structured interviewing is fairly clear that beyond a certain number of well-designed interview stages, additional rounds add noise rather than signal.  

More stages don't necessarily mean better decisions.  

They can mean more opportunity for biases to compound, more chances for a candidate to have a bad day, and more data points that contradict each other unproductively.

Finding the Sweet Spot to Improve Quality of Hire

The honest answer here is that there is no universal optimal time to hire that applies across all roles, industries, and organisations.  

What the research does consistently show is that there tends to be a U-shaped risk curve.

• Hires made very quickly — particularly those where the process was compressed under duress — show higher rates of early attrition and underperformance.  
• Hires made after very lengthy processes show elevated rates of candidate drop-off and increased likelihood that the eventual hire was not the strongest available option, simply the most persistent.
• The middle ground — which for most professional roles sits somewhere between three and six weeks of active process — tends to produce better outcomes because a well-designed process of that length allows enough time to assess candidates properly without giving the best of them a reason to accept something else.

What matters more than the absolute number, though, is the internal structure of the time.

Delays caused by scheduling difficulties, slow feedback loops, or waiting for a hiring manager who's travelling are not the same as time spent in meaningful assessment. The clock is ticking either way, but the candidate's experience — and the quality of your decision — is very different.

How AI Changes the Speed-Quality Equation

This is where it gets useful.

The reason the speed-quality trade-off exists in most traditional recruitment processes is that quality assessment takes human time. Screening CVs, conducting screening calls, scheduling interviews, gathering feedback — all of this creates friction, and that friction creates the delay.

AI-assisted recruitment doesn't eliminate this trade-off, but it changes where the friction sits.  

The parts of the process that exist mainly to gather basic information can be handled faster and more consistently with AI tools than through manual screening.

This means that the human time in the process can be redirected toward the parts where human judgement genuinely matters: evaluating cultural fit, assessing potential, asking the questions that don't have a template answer, and making the kind of contextual judgement calls that no algorithm is well-placed to make.

The practical effect, in a well-designed AI-assisted process, is that time to hire can be reduced without compressing the stages that protect quality.  

You're not rushing the assessment — you're automating the administration. These are not the same thing, even though they can look similar on a timeline.

How We Approach the Recruitment Time-Quality Balance

What we do is address the specific points in the process where time-to-hire pressure most commonly damages quality of hire outcomes.

That starts with the brief. Before any sourcing or screening begins, we spend meaningful time with hiring managers on what the role actually requires and what success looks like — not just the job description, but the practical reality of the team, the context, and the standards against which the hire will ultimately be judged. A sharp brief is the thing that allows a fast process to also be a good one.

We use AI to accelerate the parts of the process that don't require human insight: initial screening, CV matching, scheduling, and early-stage sift. This compresses time to hire at the low-risk end of the pipeline, which preserves time for the stages that actually matter.

We also track quality of hire systematically after placements are made. That means following up at the three- and six-month marks, gathering structured feedback, and feeding that data back into how we approach future briefs. It's not glamorous, but it's the only reliable way to know whether a fast hire was also a good one — and to get better over time at the ones that weren't.

If any of that sounds like the kind of approach you've been looking for, we're easy to find. No automated enquiry forms, no twelve-week wait. We’ll send you shortlisted candidates within a few days.

Frequently Asked Questions

What is the relationship between time to hire and quality of hire?  

Time to hire and quality of hire are connected but not in a simple "faster equals worse" or "slower equals better" way. Hiring under time pressure often compresses assessment stages and forces decisions before the best candidates have been properly evaluated. But very long processes cause top candidates to drop out and can introduce additional bias through accumulated inconsistency. The relationship is non-linear: there tends to be a middle range — usually three to six weeks of active process for most professional roles — that produces better outcomes than either extreme.

Does a faster time to hire mean lower quality hires?  

Not automatically, but it often correlates with lower quality when speed is achieved by cutting assessment stages rather than by improving process efficiency. A fast hire made through better screening tools, clearer briefs, and more decisive internal decision-making is very different from a fast hire made because the business ran out of patience. The cause of the speed matters as much as the speed itself.

How does a slow hiring process affect candidate quality?  

A slow process disproportionately filters out candidates who are currently employed and performing well, because those candidates have options and won't wait indefinitely. They tend to accept other offers during prolonged silences. This means that a slow process, over time, systematically selects against the strongest candidates and in favour of those with fewer alternatives or greater patience — which isn't necessarily the same group.

Can AI recruitment improve both speed and quality of hire simultaneously?  

Yes, within limits. AI tools can accelerate the parts of the process that don't require human judgement — initial CV screening, threshold criteria matching, scheduling — without compromising the stages where quality assessment actually happens. The result is a reduced time to hire that doesn't come at the cost of rigour. The important caveat is that AI is only as good as the criteria it's given; a fast AI-assisted process built on a poorly defined brief will produce consistently mediocre results more efficiently.

How should HR teams balance time to hire KPIs with quality of hire targets?  

The most effective approach is to measure both consistently and look at them in relation to each other rather than optimising one in isolation. Track time to hire by stage rather than just end-to-end, so you can identify where delays are occurring. Measure quality of hire at the three- and six-month marks using performance, retention, and hiring manager satisfaction data. Then use that data to identify which parts of the process are adding genuine value versus consuming time without improving outcomes.