Hiring Analytics
Time-to-Hire Is Not a Quality Metric
A fast hire can be a great hire. It can also be a terrible hire made very efficiently.
EuliAI · 10 min read
Time-to-Hire is one of the most commonly discussed metrics in recruiting. And for good reason: hiring processes that drag on create work, cost money and can lose candidates along the way.
But there is one thing Time-to-Hire cannot tell you: whether you made a good hiring decision.
A 23-day Time-to-Hire might mean you have built a focused, well-structured hiring process.
It might also mean you rushed through three interviews and hired the first person everyone liked.
The problem isn’t Time-to-Hire. The problem is asking one metric to answer a question it was never designed to answer.
So what does Time-to-Hire actually measure?
At its core, Time-to-Hire is a process metric. It measures how much time passes between a defined point in the candidate journey and the successful hire.
It can help you spot unnecessarily long processes, compare hiring cycles and identify opportunities to improve efficiency. That’s useful.
Time-to-Hire tells you how fast you hired.
It doesn’t tell you how well you hired.
To understand the health of a hiring process, we need more than one type of metric.
Quantitative metrics vs. qualitative metrics
Recruiting teams naturally gravitate towards things that are easy to count. Days. Candidates. Offers. Applications. Euros.
Those numbers matter. But hiring is ultimately a decision-making process about people, and some of its most important aspects cannot be understood through speed and conversion rates alone.
That’s where quantitative and qualitative metrics complement each other.
Quantitative metrics
How many? How fast? How much? Where?
- Time-to-Hire
- How quickly does a candidate move through the hiring process?
- Time-to-Fill
- How long does it take to fill an open position?
- Cost per Hire
- How much does the organisation spend to make a hire?
- Offer Acceptance Rate
- What percentage of offers are accepted?
- Funnel Conversion Rate
- How many candidates move from one hiring stage to the next?
- Candidate Drop-off
- Where are candidates leaving the process?
- Source of Hire
- Which channels ultimately produce hires?
These metrics can reveal bottlenecks and inefficiencies. What they usually can’t tell us on their own is why something happened or whether the underlying hiring decision was good.
Qualitative metrics
How well? Why? Based on what evidence?
- Candidate Experience
- Did candidates understand the role, process and expectations? Did the process feel transparent, relevant and fair?
- Evidence Quality
- Did interviews actually produce meaningful evidence against the competencies required for the role?
- Interview Consistency
- Were candidates assessed against comparable questions and criteria?
- Hiring Team Alignment
- Did the Recruiter and Hiring Manager agree on what “good” looked like before interviewing candidates?
- Decision Quality
- Can the hiring team explain why it recommends a candidate based on evidence rather than intuition?
- Assessment Relevance
- Did the practical assessment test something candidates would actually do in the job?
- Competency Coverage
- Did the hiring process actually assess the capabilities identified as important for the role?
These questions help us examine what happened in the process and the evidence behind the decision.
The distinction isn’t always perfectly clean. Candidate Experience, for example, can be explored through conversations and written feedback or quantified through surveys. Interview consistency can also be measured.
Ask what question a metric can actually answer, whether or not it has a number attached.
Four questions your hiring metrics should help answer
Look at the process through four different lenses. Each answers a useful question; none answers all of them.
1. Efficiency
Are we hiring efficiently?
- Time-to-Hire
- Time-to-Fill
- Cost per Hire
These help identify slow processes and unnecessary effort. But efficiency should not be confused with effectiveness.
A fast process isn’t automatically a good process.
2. Funnel
Where is the process working and where is it breaking?
- Funnel Conversion Rate
- Candidate Drop-off
- Offer Acceptance Rate
- Source of Hire
Imagine that 70% of candidates withdraw after the Hiring Manager interview. That’s important information. But the number itself doesn’t explain why.
- Was the interview poorly structured?
- Did candidates learn something about the role they disliked?
- Was the process too long?
- Was compensation misaligned?
The metric tells you where to look.
Investigation tells you why.
3. Experience
How is the hiring process experienced?
Quantitative and qualitative metrics overlap here. Consider:
- Candidate satisfaction surveys
- Withdrawal rates
- Candidate feedback
- Communication quality
- Process clarity
- Perceived fairness
A process can look fantastic on a dashboard while still being deeply frustrating for candidates.
A short Time-to-Hire doesn’t help much if candidates leave the process thinking: “What on earth just happened?”
4. Decision quality
Are we actually making evidence-based hiring decisions?
This is harder to capture in a dashboard. Ask about the evidence behind the decision:
- Did we assess the competencies required for the role?
- Did candidates receive comparable opportunities to demonstrate them?
- Did our interviews produce useful evidence?
- Were assessments relevant to the actual job?
- Can interviewers explain their recommendation?
- Did Recruiter and Hiring Manager agree beforehand on what “good” looks like?
Would another person looking at the same evidence understand why we made this hiring decision?
That is a very different question from: “How many days did it take?”
A scorecard gives that evidence a shared structure. Start with observable criteria and rating anchors, and use the Hiring Kick-off Checklist to agree on expectations before interviewing.
A 23-day Time-to-Hire tells you something.
It tells you that your hiring process took 23 days. That’s useful.
But it doesn’t tell you whether your interviews were structured.
It doesn’t tell you whether the practical assessment was job-relevant.
It doesn’t tell you whether candidates were evaluated consistently. And it certainly doesn’t tell you whether the person you hired was the right person.
Fast ≠ good.
Slow ≠ thorough.
A metric becomes useful when you understand what question it actually answers.
For a practical way to design that process, explore who should assess what across interviews and practical assessments.
When a useful KPI becomes a bullshit KPI
Most recruiting KPIs aren’t bullshit. The way we sometimes use them is.
“We reduced Time-to-Hire by 40%.”
- Compared with what?
- Over what period?
- For which roles?
- At what hiring volume?
- How many hires are we talking about?
- Did anything else change?
- Did we maintain the quality of the process while making it faster?
Without context, −40% is a very attractive percentage sign looking for a story.
“Our Offer Acceptance Rate is 100%.”
- How many offers?
- Over what period?
- Were withdrawn offers included?
- Were candidates effectively pre-closed before the formal offer?
A percentage without its denominator can make almost anything look impressive.
For more examples of numbers that need context, read Bullshit Hiring KPIs: When Recruiting Metrics Stop Meaning Anything.
The Euli Check
Before celebrating a recruiting number, ask:
- Compared with what?
- What is the baseline?
- Over what period?
- One month and three years tell very different stories.
- How large is the sample?
- 100% of three offers is not the same as 100% of 300.
- How was it measured?
- Definitions matter. A lot.
- What else changed?
- New Recruiter? Different roles? Hiring freeze? Salary increase? New process?
- What does this metric actually measure?
- And equally important: What does it NOT measure?
If you can’t answer those questions, don’t throw the metric away. Just don’t ask it to tell a bigger story than the data supports.
What about Quality of Hire?
Surely that solves the problem? Well… sort of.
Quality of Hire attempts to capture what happens after someone joins the organisation and may combine measures such as:
- Performance
- Retention
- Hiring-manager satisfaction
- Other relevant business or role outcomes
That can be useful. But there is no single universally applicable formula that magically tells you whether somebody was a “quality hire”.
The definition depends heavily on:
- Organisation
- Role
- Timeframe
- Outcomes being measured
Hiring does not happen in a vacuum. A person’s later performance can also be affected by:
- Onboarding
- Management
- Team dynamics
- Organisational change
- Working environment
Even Quality of Hire deserves the same treatment as every other metric:
Define it.
Understand it.
Add context.
Measure the process. Evaluate the evidence.
Recruiting analytics can tell you where your process is slow, expensive or leaky.
Qualitative metrics can help you understand whether the process is relevant, consistent and evidence-based.
Neither replaces the other. A strong hiring process needs both.
Because the ultimate goal of recruiting isn’t to produce the prettiest dashboard.
It’s to make better hiring decisions based on better evidence.