Picture a talent acquisition team that’s smashing every deadline. Roles get filled fast, requisitions close on schedule, time to fill looks great on the dashboard. Then six months later, several of those hires quietly aren’t working out, and nobody flagged it early, because the only thing anyone was tracking was how fast the seat got filled.
I question any organisation that is fully focused on time to fill, or KPIs or numbers. Obviously requisitions have to be filled; I get that, but if that’s all you’re focused on, you’re going to lose people anyway. I also question any outsourced organisation, us included, or any recruitment agency, that’s just filling roles for the sake of filling roles. We’re not understanding what the purpose is. Finding the right candidate, finding the right fit, that’s the point.
So why does time to hire get tracked so religiously while quality of hire almost never does? I think it comes down to visibility. Time to fill, speed of hire, is an internal thing. The market’s not exposed to it. Candidates don’t care. Other organisations don’t have any visibility on what those KPIs are internally. It matters to leadership, it matters to heads of talent acquisition, because they’re seeing that as an efficient process, and there’s a cost to a role not being filled. So from a leadership and finance perspective, that looks good on paper. But the quality of hire that comes out into the market. That’s your reputation. Candidates who leave an organisation might say something about their previous employer, and that trickles out.
Key takeaway: Quality of hire is a measure of whether a new employee delivers real, lasting value through performance, cultural fit, and retention, rather than simply how quickly the seat got filled. Time to hire is an internal efficiency metric. Quality of hire is what the market actually sees.
What Does Quality of Hire Mean?
Quality of hire is a measure of whether a new employee delivers real, lasting value through performance, cultural fit, and retention, rather than simply how fast the role was filled. Unlike time to hire, which tracks internal process speed, quality of hire reflects outcomes the market and candidates actually experience.
Quality of hire, for me, starts with alignment. Is the person in the right environment in terms of culture and values, does it genuinely align with them, and does it confirm what you saw in the interview process? That’s the definition I come back to once someone’s had a positive experience getting onboarded and ramped up.
Ask most talent acquisition teams to define quality of hire, though, and you’ll get a range of answers.
If it’s culturally aligned and the values align, that new hire will probably start making a difference in the organisation within their first three to six months. It’s not just about being transactional, showing up each day. A salesperson doing fifty calls a day and going home satisfied isn’t the same as a salesperson actually making a difference. One’s just activity, the other’s impact.
That’s the distinction worth noting. Time to hire and cost per hire measure the process. Quality of hire measures the outcome, and it’s historically been the hardest of the three to pin down. It’s fluid, because it really depends on the role. Quality of hire for a sales organisation means how much revenue someone brings in, and how quickly. Whereas for a back-office or operational role, the results might not bear fruit until the following year. But you can see the groundwork they’re laying, and they’re communicative about it. Take someone in marketing leading a rebrand. You don’t really know how good that rebrand is until it’s launched and you see how the market actually responds to it, sometimes six months down the track. But you can still see the value in the groundwork they’re doing along the way, even before the result is in.
Key Quality of Hire Metrics: The Formula and How to Calculate It
Ninety-day retention comes up constantly as an early signal, and I back it, but with a condition attached. What’s important in those first three months is you’ve actually got to look after the new joiner. Some people throw a candidate in the deep end, or rely too much on process, too systematic. But the leader and the team surrounding that new individual just have to care about that person. Whatever that cadence is- regular one-on-ones early, less as they get more independent, but a regular check on how they’re doing, and knowing they can come to you with questions. Once you get to that ninety-day mark, that person should feel like they’ve been looked after, and that’s also a reflection on the organisation, not just being left to do your job.
Ninety days cuts both ways. It’s also long enough to know if something’s genuinely wrong, whether that’s cultural, performance-based, or you just got it wrong.
This is the bit most teams skip. Everyone talks about quality of hire like it’s a feeling you get, and to be fair, a lot of it is, but if you want to actually track it and compare it over time, you need a number, not just a gut sense.
There’s no single formula everyone agrees on, because it really depends on what your organisation is set up to measure. Most credible versions land on the same two foundations: Crosschq’s benchmarking, for instance, runs on performance and retention. Here’s the version I’d point a team towards: a weighted average of a few post-hire indicators, each scored out of 100:
Quality of Hire = (Performance Score + Retention Score + Hiring Manager Satisfaction Score + Time-to-Productivity Score) ÷ number of indicators used
- Performance score – their rating at the first formal review, turned into a percentage. A 4.4 out of 5 becomes 88.
- Retention score – 100 if they’re still there at the 12-month mark, less if they’ve already gone.
- Hiring manager satisfaction – just ask the hiring manager how satisfied they are with the hire, and convert that to a percentage. This is the softest of the four, and I’d treat it that way, but it tells you something the other three don’t.
- Time-to-productivity – how long they actually took to reach full productivity against what you’d expect for that role, as a percentage. If they beat the benchmark, cap it at 100.
Worth being clear on the two timeframes here, because they’re doing different jobs. Ninety days tells you whether to worry. Twelve months is what actually goes into the number.
You need at least two inputs, and one of those has to be retention or tenure, with the other being some measure of performance. Three or four gives you a much more honest picture. And you can weigh them differently depending on the role; I’d weigh performance more heavily for a salesperson, and time-to-productivity more heavily for something technical.
Here’s a worked example, a customer service hire at the twelve-month mark:
- Performance score: 4.4 out of 5 → 88
- Retention: still there at 12 months → 100
- Hiring manager satisfaction: 4 out of 5 → 80
- Time-to-productivity: full productivity in 10 weeks against a 12-week benchmark → 100
Quality of Hire = (88 + 100 + 80 + 100) ÷ 4 = 92
Do that consistently, across every hire, by role, by recruiter, by source, and you’ve actually got something you can track and compare, rather than just a feeling that things are going well or not.
What’s a Good Benchmark to Measure Your Hiring Performance?
I’ll caveat this one: benchmarks move around a fair bit depending on who’s publishing them and what industry you’re in, so take this as a general reference point, not a number to chase exactly.
The external benchmarking data I’ve seen, using the Crosschq’s Q Report, puts the average around the low-to-mid 70s for a mid-sized organisation, anything above 80 is genuinely strong, and the top performers usually sit in the mid-80s or higher. On the other end, the organisations doing it poorly are often down in the high 50s to low 60s.
And it’s going to vary by role, same as everything else we’ve talked about. A sales role’s benchmark is going to lean on revenue and how fast they ramped up. A back-office or operational role is going to lean more on the groundwork they’re laying, the stuff that doesn’t show up straight away.
If your score comes in below whatever you’ve set as the benchmark, don’t jump straight to “we hired the wrong person.” It could just as easily be an onboarding problem, a job description that didn’t match the actual role, or, as I said earlier, just not enough genuine support in those first ninety days. The score tells you something’s off. Figuring out where it actually went wrong, that’s the real work.
Benchmark figures referenced above are drawn from Crosschq’s Q Report on quality of hire.
Quality of Hire vs Time to Hire: Why Speed Alone Is the Wrong Target
I don’t dismiss speed; it matters, but only when it isn’t the only thing I’m optimising for. I like an efficient process. I want to get to that first interview as quickly as I can, and our clients are the same. But that’s not to say the substance of the interview gets sped up. When I’m doing bulk hiring, say twenty-five roles in three months for twenty headcount, speed is important because the pipeline is going to run into hundreds of candidates, and I want to avoid candidates dropping off. So it’s okay to rely on speed and efficiency because of the sheer numbers involved. But if we are only dealing with ten candidates and the process is still efficient and speedy, absolutely we can go quickly, but I still take time in the actual engagement itself.
The two aren’t inherently at odds, in other words, but they can quietly work against each other if we stop watching quality once speed starts looking good. Process length is the clearest failure mode I see in both directions. If you have a six-interview process, that’s a process that wastes both the time of the hiring team and the candidate. Candidates are quite smart in this economy, and if the process is too long or too short, they’ve already got red flags about that organisation. On the flip side, I’ve been guilty of this myself; I’ve hired too quickly, and it hasn’t worked out. But if the process is too long, whatever the case, I question whether that organisation understands if they’ve got the right person, skills-wise and culturally, in that interview process. If they haven’t learned that by interviewing two or three, there’s something wrong there. And candidates aren’t stupid either; they’ll reach that same conclusion and think, why do I need two or three more interviews?
Improving Quality of Hire Through Pipeline Quality
One of the reframes I keep coming back to is that quality of hire isn’t only something you measure after someone starts; it’s shaped well before a candidate is ever assessed.
I think about the shaping of quality of hire as a set of distinct checkpoints, starting well before someone accepts an offer.
Attraction and the first interview. In a lot of cases, in the first few minutes of the first interview, I get a good gauge of knowing if that person is a cultural fit. I get it wrong sometimes.
Interview validation. This is where a second or third opinion matters. One validation point, particularly with culture, is when I get that confirmation from other interviewers. If I bring in the CEO or a sales leader for a second interview and we get that same cadence, that engagement with the candidate, even just simple eye contact during the interview, that’s good validation. Some organisations run a last meet and greet that isn’t even an official interview, just to confirm, this is the candidate we want, and that last person confirms, okay, now I see why you brought this person to the end of the process.
Final measurement. Consensus across the hiring team, not one person’s gut feel. It’s not just about one hiring manager speaking to one person, but making sure there’s a consensus with a team of people, and that it’s holistic.
Job Description Quality
A good job description is important because that’s reflective of the organisation. If you have a good job description in place, it means you’ve defined roles and responsibilities clearly, where they fit into the organisation, and what the career trajectory is for that role. Without those things, you can’t make a solid job description. There’s an exception at the senior end, though. At CEO level, or director level, sometimes the job description isn’t always a deciding factor, because it’s really about how they engage and lead other leaders; it’s about the people they meet in the process rather than what the job description says. But for technical, skills-heavy roles, it matters just as much as the culture piece. If you’re hiring a solutions architect, or someone for a role that’s really heavy on skills, qualifications and technology, the job description is really important, and reflects the organisation.
Channel Strategy: Where Top-Tier Candidates Actually Come From
If you’re weighing an internal candidate against an external one, don’t expect the data to decide it for you. On internal mobility versus external hiring, I don’t think there’s a clean answer. You always want to encourage internal mobility; that’s why you join an organisation, you want that career pathway. But there’s always a balance of being able to bring in a fresh, blank-slate external hire, because the organisation might just need new ideas. I’ve been in situations where a role’s opened up for both external and internal candidates, and both parties have a natural bias: the terminology, the vernacular, and with the external candidate, being a blank slate has its own bias too. There’s an unknown on both sides. With an internal hire, a lot of it is safety; you already know what you know, but you don’t know if that person could actually exceed. With an external hire, you don’t know what you’ll get.
On referrals, I’m far more decisive. A referral hire, by and large, is often better than a cold hire, if I just go by the numbers. What’s important is the current employee’s standing in the organisation: are they a high-performing employee, a great fit, and do they know the organisation well enough to say, I want to bring somebody else in, as opposed to referring to them for the sake of it? When that’s the case, a large percentage of those referral hires turn out to be quite good.
How Structured Interviews Can Improve Your Hiring
I’m a strong advocate for cultural fit, but structure and instinct aren’t in competition for me; the skill is knowing when to move between them. It’s important to be able to pivot in real time: structured questions, of course, but sometimes you need to go off script, or just focus on cultural fit. One example: if you’re hiring a salesperson, you’ll naturally get junior versus tenured versus very senior candidates. Often in the first five or ten minutes with a senior, seasoned salesperson, they just get it straight away, so I change script on the fly and focus on having them tell me about their sales process and having them do the storytelling. As opposed to a more junior candidate, where I might ask, how would you do this, this is how we do it, what do you think about the role.
How AI Improves Quality of Hire
Has AI improved the quality of hire in recent years? I’ll give an honest, slightly qualified answer rather than a tidy one. It’s a bit contradictory, but I think AI has helped our quality of service to clients. I’m not sure about quality of hire, but quality of service, in the sense that we’re able to deliver our recruitment more efficiently and faster. That goes back to speed, but it’s not about rushing through it, it’s about making it more efficient. A successful process in terms of speed, for me, is getting to that first interview quicker, the second interview quicker, the offer quicker, especially for candidate experience, but at the same time, not cutting corners.
Software and Tools Improve Quality: What to Look For
If you’re looking at platforms to help with any of this, here’s what I’d actually look for, because a lot of it is marketing dressed up as substance.
You want something that helps you measure quality after the hire, not just speed you up before it. So proper reporting on retention, performance, hiring manager satisfaction, not just time to fill and cost per hire sitting on a dashboard looking efficient. You want consistent, structured screening that cuts down on reviewer fatigue and bias, without taking the actual judgement out of your hands. And you want a system that keeps your existing talent pool warm, so good candidates you’ve already engaged with don’t just disappear the moment a role closes.
This is honestly where I think Scout Talents :Recruit does it differently to a lot of what’s out there. :Recruit, has AI built into it properly, not bolted on. AI Screen takes every application and turns it into a clear, consistent summary, so instead of a hiring team spending days wading through applications, they can triage a shortlist in minutes. AI Search goes back through your existing talent pool and surfaces people who already know your organisation, before you’ve spent a cent on new advertising. Both of those sit inside :Recruit alongside actual recruitment specialists, and that’s the bit I’d stress, because a people challenge like quality of hire is never going to be solved by software on its own. You need people behind the tech.
If you’re rethinking how your team tracks quality instead of just speed, that’s a conversation worth having. Book a demo with Scout Talent and see how :Recruit and AI Screen actually fit into your process.
Summary and Next Steps
If I could only start tracking one quality of hire metric this quarter, I wouldn’t point to a dashboard number. I’d point to engagement. Whatever KPIs and performance numbers someone needs to fulfil in the first ninety days is obviously a given. But what’s important is trying to get to the engagement aspect, are you keeping them engaged, and are they engaged. That’s a hard one to put a metric on, but if a new hire goes into their shell, stops talking, doesn’t put their hand up for help when things get challenging, that’s a red flag. Or is that a result of management and the surrounding people not engaging and supporting that person enough. It’s a key, emotional sort of metric. Often when someone’s in their shell and you’re trying to engage them, you just know it’s not going to work out.
It’s a fitting note to end on. Quality of hire isn’t a single formula or a benchmark you hit once and move on from, it’s a thread that runs from the job description, through the interview room, through the first ninety days, and into whether that person is genuinely thriving a year later. Teams that only track speed will keep filling seats. Teams that track quality will keep the people worth keeping.
