Quality of Hire Fast Track Series 2: Calculating Quality of Hire

Almost every talent leader I talk to says the same thing.

We know quality of hire is what matters. We just don't measure it well.

And then they describe some version of the same situation: the data lives in three different systems, no one owns the work of stitching it together, and the closest thing they have to a quality of hire report is a spreadsheet someone updates manually once a quarter when the CHRO asks for it.

This is the gap LinkedIn's research has been pointing at for years — 91% of talent leaders call quality of hire their most important metric, and only about a third actually track it. That gap isn't a tooling problem. It's a process problem. Most teams don't lack the data; they lack the playbook for turning the data they already have into something that flows on a cadence, lands on the right desks, and changes the next hire.

This is that playbook.

It's organized as a phased rollout — Define, Instrument, Cadence, Composite, Close the Loop — so you can start where you are, ship something useful in 60 days, and build maturity from there.

Quality of hire, defined for the purposes of this playbook.

Before any data work, the definition.

A quality hire is an employee who creates measurable value in their role within a defined timeframe — value that shows up across four dimensions: how long they stay, how well they perform in their core role, how much they contribute beyond it, and how much they grow. That's the framework we use at Crosschq, and it's deliberately broader than any single metric.

This matters because how to measure quality of hire depends entirely on what you've agreed quality of hire means. Teams that try to measure it before defining it end up with a dashboard nobody trusts.

So: write the definition down. Get the CHRO, the head of TA, and the heads of the businesses you hire for to sign off on it. One paragraph is enough.

Then you can start measuring.

Phase 1 — Define what success looks like, role by role.

The hardest part of measuring quality of hire isn't the math. It's getting honest about what "good" actually looks like in a specific role before you've hired anyone.

For every role family you hire for, pin down four things:

• Timeframe. When can someone reasonably be judged a successful hire in this role? Often 180 days for individual contributors, 365 days for managers, longer for senior leaders. The point is to pick a number and commit to it.
• Success criteria. What does a high-performing person in this role accomplish? Not "exceeds expectations" — actual, observable outcomes (closes X in pipeline, ships Y, retains Z% of accounts).
• Failure modes. What does a misfit hire look like? This is the conversation most hiring processes skip. The answer informs your screening more than the success criteria do.
• Data owner. Who already has the data needed to evaluate this role — the hiring manager, sales ops, the engineering manager? Name them now. You'll need them in Phase 2.

This work is unglamorous and slow. It is also the single highest-leverage thing a TA function can do before instrumenting anything. Skipping it is how teams end up measuring quality of hire by retention alone — because retention is the only data they don't have to negotiate to get.

Phase 2 — Instrument the inputs.

Once the definition and success criteria are locked, the next move is making sure the data sources you'll need are actually capturing the right things.

Most TA teams underestimate how much of the data already exists. You almost certainly have:

• ATS data — source, recruiter, time-to-fill, interview scores, assessment results. The pre-hire side of the picture.
• HRIS data — start date, role, manager, comp, termination date and reason. Tenure metrics live here.
• Performance management data — review scores, goal attainment, promotions, comp adjustments. The core in-role signal.
• Operational systems — CRM data for sellers, ticket data for support, deployment data for engineers. Role-specific outcomes.

What you probably don't have yet, and need to add:

• A hiring manager satisfaction pulse. One question, sent to the hiring manager at 90 and 180 days post-start: Knowing what you know now, would you hire this person again? That's it. Don't dress it up.
• A new-hire pulse. A short engagement and expectations-alignment check from the candidate side at 30 and 90 days. If they're already disengaged at 90 days, your retention metric is going to confirm what you could have known three months earlier.
• Structured reference data, if you don't already have it. Reference checking, done as structured intelligence rather than a formality, is one of the highest-signal pre-hire inputs you can later correlate against post-hire outcomes.

The deliverable from Phase 2 isn't a dashboard. It's a clean list of the data sources, the system of record for each, the cadence at which each updates, and the person responsible for keeping it accurate.

Phase 3 — Establish the measurement cadence.

This is where most teams over-engineer. Resist the urge.

The right cadence is the simplest cadence that actually fires every time. Here's the one we recommend starting with:

• Day 30: New-hire experience pulse. A short survey to the new hire. Are they getting what they expected? Are they ramping? Early warning system for misalignment.
• Day 90: Hiring manager satisfaction + first performance check-in. The "would you hire again?" question to the manager, plus a structured 30-minute review on the success criteria you defined in Phase 1.
• Day 180: Second performance check-in + initial outcome data. The success criteria again, plus the first real read on role-specific outcomes (pipeline built, code shipped, accounts retained).
• Day 365: Cohort review. Pull the full hire cohort into a single review — who's still here, who left voluntarily, who got promoted, what the source-of-hire patterns look like.

Two things make this cadence work that don't show up on the calendar:

1. The data has to be entered the same way every time. Same survey, same scale, same questions. Variance in how the data is captured destroys the comparability that makes the measurement useful.
2. It has to be automated. Manual surveys delivered by recruiters get skipped. Calendared, system-triggered surveys get answered. The technology lift is small. The discipline lift is enormous.

Most of how to measure quality of hire is really about running these four checkpoints reliably for a full year before you do anything fancier.

Phase 4 — Build the composite picture.

Once you have a year of checkpoint data, you can start composing it into something useful.

A quality of hire index pulls the four dimensions into a single score per hire — typically a normalized 0–100 or 1–5 — weighted to reflect what matters in that role. Senior leadership hires might weight tenure and extra-role contribution heavily; high-velocity sales hires might weight goal attainment and ramp time more.

The weighting is less important than the discipline of doing it the same way every time, for every cohort.

Once the index exists per hire, the analysis you've been waiting to run becomes trivial:

• Quality by source. Which sourcing channels produced the highest-quality cohorts? Almost always different from your highest-volume sources.
• Quality by recruiter. Which recruiters are producing hires that perform at 180 days, not just hires that close fast?
• Quality by interview panel. Which interview compositions correlate with the strongest downstream outcomes?
• Quality by assessment profile. Once you have enough data, you can begin to identify which pre-hire signals predict success in which roles — the start of a genuine predictive hiring model.

This is the analysis layer that turns measurement from a reporting exercise into a decision-making one.

Phase 5 — Close the loop.

Measuring quality of hire is not the goal. Improving quality of hire is the goal.

A lot of measurement programs stall here. The data exists, the dashboard exists, and nothing actually changes about how the next hire gets made — because the feedback loop between post-hire performance and upstream hiring decisions was never built.

Closing the loop means:

• A monthly TA review where source-of-hire quality, recruiter-by-recruiter outcomes, and 90-day hiring manager satisfaction are the standing agenda. Not a one-time readout. Operational rhythm.
• A quarterly business review where the quality of hire index sits on the same dashboard as time-to-fill and cost-per-hire — and gets equal weight in the conversation.
• A clear decision rule. When source X consistently underperforms source Y in the quality index, you change the sourcing mix. When recruiter A's hires consistently outperform recruiter B's, you study what A does differently and codify it. The data has to drive action, not just describe.

This is the work that separates TA functions that talk about quality of hire from TA functions that compound it. The first group has a dashboard. The second group has a flywheel.

The pitfalls that derail measurement programs.

A few patterns I see frequently enough to call out:

• Trying to measure everything at once. Pick three or four checkpoints, run them well for two quarters, then expand. The teams that try to launch a 15-metric framework on day one almost always end up with a 0-metric framework by quarter three.
• Treating subjective ratings as objective data. Hiring manager satisfaction is incredibly useful when it's one consistent question scored the same way every time. It becomes noise the moment different managers interpret a 14-item survey differently. Standardize the instrument or skip it.
• Conflating voluntary and involuntary turnover. These tell completely different stories and need to be measured separately. A high involuntary turnover rate is on your performance management process. A high voluntary turnover rate is on your hiring and retention process. Lumping them together masks both.
• Skipping the post-hire data flow. This is the one most worth repeating: if post-hire performance never makes it back to the recruiters and hiring managers who made the original decision, your measurement program is generating reports, not improving outcomes.

The hardest part of how to measure quality of hire isn't analytical. It's organizational — getting three or four teams that don't normally share data to share it on a cadence, in a format that compounds.

What you can ship in 60 days.

If this looks like a year's worth of work, it isn't. A pragmatic 60-day starting point:

• Days 1–14. Get sign-off on the one-paragraph definition. Pick three role families to start with. Identify the success criteria and data owners for each.
• Days 15–30. Stand up the 90-day hiring manager satisfaction pulse. One question, automated, calendared to fire 90 days after every start date.
• Days 31–45. Build a simple report combining first-year retention, 90-day hiring manager satisfaction, and source-of-hire. This is your v1 quality of hire dashboard. Don't wait for a composite index.
• Days 46–60. Run your first monthly TA review using that dashboard. The point of the meeting isn't to admire the data. It's to make one sourcing or process decision based on what the data shows.

At the 60-day mark, you have a working measurement program. Crude, but working. From there it compounds.

That's how to measure quality of hire in a way that actually changes hiring outcomes — not by building the perfect model, but by closing the loop on the data you already have.

Once it's closing, the rest gets easier.

Frequently asked questions about measuring quality of hire

How do you measure quality of hire? You measure quality of hire by defining what success looks like for each role before hiring, instrumenting the data sources you'll need (ATS, HRIS, performance management, operational systems), running a fixed cadence of checkpoints at 30, 90, 180, and 365 days post-hire, composing the results into a per-hire index, and feeding the data back to recruiters and hiring managers to inform future decisions.

What is the best way to measure quality of hire? The best way to measure quality of hire is to combine post-hire performance, retention, and contribution data on a fixed cadence — not to chase a single composite formula. Most teams should start with first-year retention, 90-day hiring manager satisfaction, and structured 90- and 180-day performance check-ins, then layer in source-of-hire quality and a composite index.

How long does it take to start measuring quality of hire? A working quality of hire measurement program can be live in 60 days. The first 30 days focus on definition and data-source ownership; the next 30 days stand up the 90-day hiring manager satisfaction pulse and a simple v1 dashboard combining retention, satisfaction, and source-of-hire.

Who owns quality of hire measurement? Quality of hire measurement is typically owned by the TA function, with shared accountability from HR operations (for retention data), performance management (for in-role data), and the business units being hired for (for outcome data). The single most common failure mode is leaving ownership ambiguous.

What data do you need to measure quality of hire? The core data sources are ATS data (source, recruiter, time-to-fill), HRIS data (tenure, departures), performance management data (review scores, promotions, goal attainment), and a structured hiring-manager satisfaction signal at 90 and 180 days post-hire. Most TA teams already have the first three; the fourth is the one most often missing.

Why don't most companies measure quality of hire well? Most companies don't measure quality of hire well because the data lives in different systems with different owners, and no single function is accountable for stitching it together. The result is a write-only hiring process — decisions go in, performance data never flows back to inform the next decision.