On this page▾
- The dashboard problem nobody admits
- 1. Time to hire, measured from first contact
- 2. Stage-to-stage conversion, especially the top of funnel
- 3. Offer acceptance rate
- 4. Quality of hire, even though it is hard
- 5. Sourcing channel effectiveness, by quality not volume
- 6. Recruiter capacity, measured in active reqs and load
- 7. Candidate experience, captured as a real signal
- The metrics to delete today
- Make the metrics ask you questions
Walk into almost any talent org and you will find a dashboard with thirty tiles on it. Time to fill, time to hire, source of hire, pass-through by stage, candidate NPS, offer rate, decline rate, diversity at every funnel step, recruiter activity counts, req aging, and a dozen more. It looks impressive in a board deck. It is also, for the most part, useless. A metric you look at but never act on is not a metric. It is decoration.
The reason this happens is structural. Modern applicant tracking systems make it trivially easy to chart anything, so teams chart everything, and the signal drowns in the noise. The discipline of talent analytics is not collecting more numbers. It is ruthlessly deciding which handful of numbers you will actually change behavior over, and ignoring the rest until they matter. After watching dozens of recruiting teams, I am convinced there are about seven metrics that genuinely move the function. Here they are, why they matter, and what to do when they go red.
Time to fill, the number most teams report, counts from the day a req opens to the day someone accepts. It is contaminated by things recruiting does not control, mainly how long it took the hiring manager to get approval and how long the req sat in a queue. Time to hire is cleaner. Measure it from the candidate's first real touch, the application or the sourcing reply, to their signed offer. That window is the part of the process your team owns.
The reason time to hire matters is not impatience. It is conversion. The best candidates are off the market in roughly ten business days. Every extra day in your process is a day a competitor can close them. If your time to hire for engineering is forty days and the market clears good engineers in two weeks, you are not losing candidates because your comp is low. You are losing them because you are slow. Track the median, not the average, because one stalled exec search will wreck your mean and hide the typical experience.
A single funnel number tells you nothing. Conversion between stages tells you where the process actually breaks. The two transitions worth obsessing over are application-to-screen and screen-to-onsite, because that is where most of the leakage and most of the wasted recruiter hours live.
Here is a useful benchmark. If fewer than one in five applicants make it to a recruiter screen, either your sourcing is wrong or your job descriptions are attracting the wrong people. If more than half of your screens advance to onsite, your screen is too soft and you are burning your hiring managers' time on people who should have been filtered earlier. Healthy screen-to-onsite sits somewhere around a third. When a stage conversion drifts, you have a concrete, fixable problem rather than a vague feeling that hiring is hard.
Offer acceptance rate is the most honest mirror in recruiting. It tells you whether the story you sold during the process survived contact with a real number and a competing option. A healthy rate for most companies sits between eighty and ninety percent. Below seventy, something is structurally wrong, and it is almost never just comp.
When acceptance drops, resist the reflex to immediately raise salary bands. Interview your declines. The pattern is usually one of three things: the role was sold differently than it turned out to be, the process took so long the candidate cooled or got another offer, or the final conversation was transactional instead of human. All three are cheaper to fix than a comp overhaul, and fixing them lifts every future offer too.
Every honest recruiter knows quality of hire is the metric that matters most and the one almost nobody measures well. The temptation is to skip it because it is fuzzy. Do not. A rough quality signal beats a precise vanity metric every time.
The practical version is a simple ninety-day and one-year check. At ninety days, ask the hiring manager one question on a five-point scale: knowing what you know now, would you make this hire again. At one year, pull performance review ratings and regrettable attrition. You are not looking for academic rigor. You are looking for whether your fast, high-converting funnel is actually producing people who succeed, or whether you are optimizing speed at the cost of fit. If quality is high and time to hire is low, you have a great process. If quality is dropping while speed improves, you are gaming the wrong number.
Most source-of-hire reporting counts where applicants come from. That is the wrong end of the funnel. A job board that floods you with two thousand applicants and produces one hire is worse than a referral channel that sends ten people and lands three. Measure channels by hires produced and by downstream quality of those hires, not by raw applicant count.
Do this and the picture usually inverts. Referrals and targeted outbound, which produce small numbers at the top, almost always dominate on quality and acceptance. The expensive job board spend that looks productive because it generates volume often produces your worst conversion and your shortest tenures. Reallocating budget from volume channels to quality channels is one of the highest-leverage moves a talent leader can make, and you cannot make it without this metric.
This one is internal and unglamorous, and it predicts burnout and missed hires better than anything else. The number is simple: how many open reqs is each recruiter actively carrying, weighted by difficulty. A recruiter juggling eight senior engineering searches is in a different universe than one running eight high-volume support roles, so weight accordingly.
The reason this matters is that recruiting quality collapses non-linearly under load. A recruiter at reasonable capacity gives candidates fast, personal responses. The same recruiter at double capacity ghosts people, rushes screens, and lets pipelines go stale, which then shows up two months later as a bad time to hire and a sinking acceptance rate. By the time the downstream metrics go red, the damage is done. Watching load lets you intervene before the visible numbers break.
The last metric is candidate experience, and the trap is treating it as a feel-good survey. Capture it as a number you act on. A short post-process survey to every candidate, hired or not, with one rating and one open text field, is enough. The rejected candidates' responses are the most valuable, because they have no reason to flatter you.
Candidate experience compounds in ways the others do not. A candidate you rejected well refers a friend, reapplies in two years, or becomes a customer. A candidate you ghosted writes a review that quietly suppresses your applicant quality for years. In a tight market your reputation as a place that treats people decently is a sourcing advantage you cannot buy. Measure it, and read the verbatims, because the number alone hides the story.
If those seven are the keepers, here is what to stop reporting. Raw applicant volume, which rewards noise over signal. Recruiter activity counts like calls made and emails sent, which optimize busyness instead of outcomes. Time to fill on its own, for the contamination reasons above. Cost per hire as a headline number, which quietly pushes teams toward cheap, low-quality channels. And any diversity metric that is reported as a single top-line percentage without funnel context, because it tells you where you are without telling you where you are leaking, which is the only part you can fix.
None of these are evil. They are just lower in the hierarchy, and putting them on the main dashboard crowds out the numbers that actually drive decisions. Keep them in a drawer and pull them when a top metric points you there.
Here is the deeper shift. Most teams treat metrics as something you go look at, usually in a Monday meeting, usually too late. The better model is metrics that come find you. The moment screen-to-onsite drops below threshold, or a recruiter's load crosses a line, or acceptance dips on a given team, someone should know that day, not at the end of the quarter.
This is the part of recruiting analytics that legacy tooling handles worst. The data sits in the system, technically correct and completely inert, waiting for a human to think to ask. Part of why we built VScout the way we did is that an AI agent watching the pipeline can surface the anomaly in plain language, the moment it appears, and tell you which of these seven just moved and why. You can quite literally ask it where you are losing engineering candidates and get the stage, the trend, and the likely cause instead of a chart you have to interpret yourself.
But the tool is secondary. The discipline is primary. Pick these seven, or your own honest version of them, put them where you cannot avoid them, and commit to acting when they move. A recruiting function run on seven metrics you actually use will outperform one drowning in thirty it merely displays, every single time.
