How to Get Noticed by AI Recruitment Agencies

Here's a conversation that happens constantly.

A hiring manager has been through eight interviews. Their recruiter has sent over fifteen CVs. Three people made it to the final stage. None of them felt quite right. The role is still open. Everyone is tired. And somewhere in the background, the business is getting increasingly pointed about when this position is going to be filled.

So what went wrong?

Nine times out of ten, the answer isn't that the right candidates don't exist. It's that nobody clearly defined what "right" meant before the process started. The hiring manager had one version in their head. The job ad described a slightly different version. The recruiter was screening for a third version based on the job description from eighteen months ago that nobody had updated.

Three different targets. Fifteen CVs. Zero good matches.

Finding the right candidate for a job is not primarily a sourcing problem. It's a clarity problem. You cannot reliably find something you haven't precisely defined. And most hiring processes — if we're being honest — are built around a brief that's vague enough to mean almost anything, which is why they produce shortlists that feel almost right but not quite.

This is fixable. Let's get into it.

Step One: Define What "Right" Actually Means (Properly, Not Just on Paper)

Before you post a single job ad or brief a single recruiter, you need to answer a question that sounds simple and usually isn't.

What does success look like for this person in twelve months?

Not "what skills do they need." Not "what experience are we looking for." What does a good hire actually achieve in this role, by when, and against what standard?

If you can answer that question specifically — not "they'll manage the team well" but "they'll have reduced average response time from 4 days to 48 hours and have rebuilt the relationship with the three accounts that are currently at risk" — then you have a hiring brief. If you can't, you have a job description, which is a different thing.

Job descriptions describe the role. Hiring briefs describe success. The distinction matters enormously because it changes what you're assessing for. Competencies that look identical on a CV can produce radically different outcomes depending on which definition of success you're working from.

The brief also needs to cover the things that rarely appear in job descriptions: the team dynamics, the challenges the previous person struggled with, the cultural realities of the environment the new hire is walking into. A candidate who'd thrive in a highly structured, process-driven team might be genuinely miserable — and underperforming within six months — in a fast-moving, ambiguous startup environment. Same skills. Completely different outcome.

Spend two hours on the brief before you spend two months on the process.

Step Two: Understand Exactly Who You're Looking For (Not Just What)

Most job ads describe a set of requirements. The best hiring processes describe a person.

There's a difference. Requirements are a checklist. A person is a combination of skills, motivations, working style, and career trajectory that produces a specific type of outcome in a specific type of environment.

Think about the best hire you've ever made in a similar role. What made them excellent? Was it purely their technical skills, or was it how they applied them? Was it their experience level, or their attitude toward problems? Was it something on their CV, or something that only became clear in the first month?

Now think about a hire that didn't work out. What was the gap? Was it about capability — they couldn't do the job — or was it about fit, motivation, or values? Bad hires are more often the latter than the former. People are rarely hired into roles they can't technically perform. They're hired into roles that don't match who they are.

Define both dimensions. What does this person need to be able to do, and what kind of person thrives in this environment? The second question is harder to answer and more important than the first.

Step Three: Look in the Right Places (Which Might Not Be Where You're Currently Looking)

Once you know who you're looking for, the question of where to find them becomes much easier to answer — because different candidate pools live in very different places.

Posting on a general job board and hoping the right candidate applies is a bit like opening your front door and hoping the person you're looking for happens to be walking past. It works occasionally. It's not a strategy.

Active vs passive candidates. The candidates who apply to your job ad are actively looking. That's a subset of the people who might be right for your role. Often not the most interesting subset. The best candidates for many roles are currently employed, performing well, not looking, and therefore not seeing your ad. Reaching them requires proactive sourcing — direct outreach, recruiter networks, professional communities — rather than waiting for inbound applications.

Where your candidates actually spend their time. A software engineer is probably findable on GitHub and specialist tech communities. A senior finance professional is more likely to respond to a warm introduction from a trusted contact than to a cold LinkedIn message. A specialist in a niche technical field might be best reached through a professional association, a conference, or a university department. The right sourcing channel depends on who you're trying to reach, not on which channels are easiest to use.

Your own network and previous pipelines. One of the most underused sources of strong candidates is the people who almost got the last job. Strong candidates who were a close second for a role three months ago. Previous employees who left on good terms. Referrals from high performers in your team who know the field well. These people are warm — they're already familiar with your organisation, and the qualification barrier has partly been cleared.

A good recruitment agency earns its fee primarily in this area — not by posting your job to the same boards you could post it to yourself, but by maintaining relationships with passive candidates who aren't findable through standard channels and who are credible because the agency already knows their work.

Step Four: Write a Job Ad That Attracts the Right Person, Not Just the Most People

Volume is not the goal. Relevance is.

A job ad that generates 200 applications, 180 of which are irrelevant, has not done its job well. It has created work. A job ad that generates 30 applications, 25 of which are worth reading, is worth considerably more — even though it looks worse on an applications dashboard.

The way to attract relevant candidates is to be specific and honest about what the role actually involves. Not aspirationally vague. Not a list of every possible desirable quality. Specific and honest.

What does a typical week look like? What are the hard parts of the job — the bits that aren't glamorous, the challenges the team is currently facing, the aspects that have tripped people up before? What does the culture actually feel like to work in, not what does the culture page on the website claim?

Counterintuitively, the things that might put some candidates off — "this is a high-pressure role with significant ambiguity," "the team is going through a period of change," "this requires someone who's comfortable working without much structure" — are precisely the things worth including. They filter out the candidates who'd struggle and attract the candidates who'd thrive.

The candidates you want are the ones who read a genuine description of the role and think yes, that's exactly what I'm looking for. You're not going to reach them with corporate language and a list of buzzword competencies.

Step Five: Screen for Signal, Not Just Suitability

Most CV screening is filtering for absence of red flags. That's not the same as finding the right person.

A CV tells you whether someone has broadly done similar things before. It doesn't tell you how well they did them, why they made the choices they made, how they handled the difficult parts, or whether the version of the role they performed previously matches the version you're hiring for now.

Screen for signal. What in this candidate's background actually suggests they'd be excellent at this specific role, rather than merely eligible for it? Is there evidence of the outcomes you care about, not just the activities? Does the career trajectory suggest someone who's genuinely motivated by this type of work, or someone who's applying broadly and your role happens to fit their search criteria?

Structured screening calls — fifteen to twenty minutes, consistent questions, scored against the same criteria for every candidate — are faster and more accurate than either CV review alone or unstructured "get to know you" conversations. They also make it much easier to compare candidates fairly, because you're comparing responses to the same questions rather than impressions from conversations that went in completely different directions.

What you're listening for in a screening call: specificity. Candidates who can speak precisely about what they achieved, how they did it, and what they'd do differently tell you something useful. Candidates who speak in generalities about "driving results" and "leading teams through change" are giving you the language of a CV, not the substance of an actual track record.

Step Six: Assess What the Role Actually Requires

The most common assessment failure in hiring isn't asking the wrong questions. It's assessing the wrong things entirely.

Most interview processes measure how well a candidate can talk about their experience. That's a useful signal, but it's not the same as measuring how well they'd do the job. And for many roles, the gap between the two is significant.

The question to ask about every assessment stage is: does this test what the role actually requires? If the role requires analytical thinking under pressure, does your interview process include anything that assesses analytical thinking under pressure — or does it ask candidates to describe a time they demonstrated analytical thinking, which is a different thing entirely?

Practical assessments, case studies, work samples, and structured simulations — done proportionately and with respect for candidates' time — consistently outperform interview-only processes on predictive accuracy. They're also fairer, because they give candidates who are less polished in interview settings an opportunity to demonstrate capability rather than just poise.

The caveat is that assessments need to be role-relevant and reasonable in scope. A three-hour unpaid case study for a £30,000 role is not a great look for your employer brand and will lose you good candidates who are fielding multiple offers. Keep assessments proportionate to the seniority and complexity of the role.

Step Seven: Move Decisively When You Find Them

Here's a mistake that happens more than it should.

A strong candidate goes through a well-designed process. Everyone thinks they're excellent. The hiring manager takes a fortnight to confirm. The offer takes another week to generate. By the time it arrives, the candidate has accepted something else.

The right candidate is rarely only talking to you. If they're strong enough for you to want, they're probably strong enough for two or three other employers to want as well. And those employers may be moving faster.

Decision-making speed at the end of a process is not the same as rushing the process. It's the natural conclusion of having done the front-end work properly. If you've defined success clearly, assessed rigorously, and reached genuine agreement that this is the right person — the offer should follow within 24 to 48 hours of that decision, not drift into the following fortnight while sign-offs are obtained.

Pre-approved salary bands and standard contract templates exist precisely for this purpose. Use them.

The Pattern Behind Failed Hires

Before we wrap up, it's worth naming the pattern that sits behind most of the "we hired the wrong person" conversations we have.

It's rarely that the candidate was dishonest or that the recruiter was careless. It's almost always that the brief was fuzzy, the assessment tested the wrong things, and the warning signs that did appear were rationalised away because the timeline pressure was significant and this candidate was, at least, not obviously wrong.

Finding the right candidate is not about finding someone who clears every bar. It's about being clear enough on what the bar is that you'd recognise the right person if they were standing in front of you — and confident enough in the process that you don't second-guess it when they are.

How Squarelogik Approaches Finding the Right Candidate

We're going to be honest: we've seen all of the failure modes above, including in our own processes.

A vague brief that generated a great-looking pipeline of mediocre matches. An assessment process that everyone felt good about right up until the six-month performance review. A strong candidate lost to a competitor offer because an internal approval took nine days to materialise.

What we try to do differently is treat the brief as the most important part of the process — not the admin that happens before recruitment starts, but the foundation everything else is built on. We spend real time on it. We push back when success criteria are vague. We ask the uncomfortable questions about what went wrong with previous hires before we start trying to find a better one.

We use AI to find candidates who aren't in the active market, and human judgement to decide whether those candidates are actually right for the specific environment they'd be walking into. Both parts matter.

And we follow up after placement, because the only reliable way to know whether we found the right candidate is to check.

If you're finding that your process is generating lots of candidates but not the right ones — or not enough candidates at all — we're worth talking to. The first conversation is just a conversation.

FAQs

How do you find the right candidate for a job?

Start with a precise definition of what success looks like in the role — not just skills and experience, but what a good hire would actually achieve in the first twelve months. Then source in the places where your ideal candidates actually spend their time, which often means proactive outreach to passive candidates rather than waiting for inbound applications. Assess against role-relevant criteria, not just interview performance. And when you find the right person, move quickly — the candidates worth hiring are rarely only talking to you.

‍

What makes someone the right candidate for a role?

The right candidate has both the capability to do the job and the characteristics to thrive in the specific environment it exists in. Skills and experience matter, but fit — with the team dynamic, the working style the role demands, the culture of the organisation — is what separates a hire that works from a hire that looked good on paper. Most failed hires are not capability failures. They're fit failures that were visible in the assessment process and rationalised away under time pressure.

‍

How do you attract the right candidates for a job?

Write job ads that are specific and honest about what the role actually involves — including the hard parts. Vague aspirational language attracts everyone and filters nobody. Specific, accurate descriptions attract candidates who are genuinely motivated by what the role requires and filter out those who wouldn't enjoy it. The volume of applications may fall. The relevance of those applications will rise, which is the metric that actually matters.

‍

How important is the job brief when looking for candidates?

It's the most important part of the process, and the most commonly skipped. A vague brief means everyone involved in the process — recruiter, hiring manager, interviewer — is looking for something slightly different. That produces shortlists that feel close but not right, decisions that get delayed, and hires that disappoint. A precise brief that defines success criteria before sourcing begins compresses timelines, improves shortlist quality, and makes the final decision substantially easier.

‍

Should you use a recruitment agency to find the right candidate?

‍For roles where the right candidate is likely to be passive — currently employed and not actively looking — a good recruitment agency adds significant value because it has relationships with those candidates and can make a credible approach. For roles where the right candidate is easily findable through standard channels, the value is more in process management than sourcing. The question worth asking any agency is not "can you find candidates" but "do you have relationships with the specific type of candidate we need, and how will you know if someone is right rather than just eligible?"

‍

How do you assess whether a candidate is right for a job?

Structured interviews with consistent, scored questions are more predictive than unstructured conversations. Practical assessments that mirror actual job tasks — case studies, work samples, simulations — are more predictive than interview performance alone. Reference calls that go beyond "did they work here" to ask specific questions about how they worked and what they found challenging are consistently underused and consistently valuable. The goal is to test capability in the way the role actually requires it, not to test how well someone can describe their past experience.

‍

What are the most common reasons the wrong candidate gets hired?

Usually a combination of: an unclear brief that meant nobody was assessing against the same standard; timeline pressure that led to a "good enough" decision rather than the right one; an assessment process that measured presentability rather than capability; and warning signs that were visible but rationalised away. The decisions that produce bad hires rarely feel like bad decisions at the time. Which is precisely why the brief, the assessment framework, and the decision criteria need to be established before the pressure to fill the role sets in.

‍

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 — what to do when yours is out of range.

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.

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. Ironically.

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.

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 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.

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.