What “quality of hire” actually means — and how to measure it

Ask most founders what “quality of hire” means and you’ll get a feeling, not a measurement. “We know a good hire when we see one.” The trouble is that this only tells you about hires you’ve already made and already have an opinion on. It says nothing about the candidate in front of you right now, which is precisely when you need the definition to do any work.

Why “gut feel” quietly fails at scale

Gut feel works reasonably well when one person — usually the founder — is making every hiring decision personally and has a large, consistent internal dataset of who’s worked out and who hasn’t. It stops working the moment hiring gets delegated, because the new decision-maker doesn’t have that dataset. They have their own instincts, shaped by a different set of experiences, applied inconsistently to a role they may not fully understand yet. That’s how two capable managers, interviewing for the same kind of role, arrive at completely different bars for “good” — and neither of them is wrong, because there was never an agreed definition to be wrong against.

This is also why agencies rarely improve quality of hire even when they improve speed of hire. An agency’s incentive is to present candidates who get accepted. Whether those candidates go on to perform is largely invisible to them — by the time you’d know, the invoice is long paid and the recruiter’s attention has moved to the next search.

A definition that can actually be tested

Quality of hire is measurable when you define it before the search starts, not after the fact. That means writing down, for the specific role, what this person needs to be able to decide and do within a defined window — not a generic list of competencies, but the two or three outcomes that would prove the hire is working. A sales leader might need to be able to run pricing exceptions independently within ninety days. An operations hire might need to own the monthly close without escalation within a quarter. Whatever it is, it needs to be specific enough that six months from now, everyone would agree on whether it happened.

From there, quality of hire becomes a small set of things you can actually track: time-to-productivity against that defined bar, retention at the twelve-month mark, and — the one that matters most and gets measured least — whether the hire needed to keep coming back to the founder for decisions that were supposed to be theirs to make. A hire who’s technically excellent but still routes every judgment call upward hasn’t actually raised the ceiling, no matter how strong their résumé looked going in.

Why this has to be built before the interview, not during it

A structured scorecard, written before the first interview, does two things a gut-feel process can’t. It gives every interviewer the same bar to evaluate against, so “quality” stops depending on who happened to be in the room. And it gives you a record — across searches, across roles, across a year of hiring — of whether your process is actually getting better or just staying busy. Without that record, “we’ve gotten a lot better at hiring” is an opinion. With it, it’s a number you can check.

This is the part of hiring that has nothing to do with sourcing candidates and everything to do with whether the whole system produces good outcomes reliably — which is also why it’s the part that outlives any single search. A recruiter fills the role in front of them. A hiring system built around a real definition of quality keeps working on the next fifty roles you’ll ever fill, whether we’re involved in the next one or not.

We build this scorecard-and-standard work into every search we run, for exactly this reason — see Talent for how it fits alongside search and embedded recruiting. And because a hiring miss is so often a symptom of something upstream — an undefined role, the wrong org design — it’s worth reading how we diagnose that first, on How We Work.