HR GLOSSARY · Analytics & reporting

Time-to-hire

Also known as: hiring velocity, days-to-hire

Time-to-hire is the number of days from when a candidate enters your hiring funnel (first application or first contact) to when they accept the offer. Lower is better — but only up to the point where speed compromises quality of fit. Distinct from time-to-fill, which counts from when the role opens.

Time-to-hire is the single most-tracked recruiting metric and one of the most-gameable. Lower is generally better — candidates who go through a fast, well-run process say yes more often and feel valued. But chasing the number for its own sake produces second-order damage: shortcutting reference checks, pushing offers to the first OK candidate rather than the right one, or counting candidates who applied 8 months ago as having a 1-week time-to-hire because they "re-entered" the funnel. Use time-to-hire alongside quality-of-hire metrics (90-day retention, first-year performance ratings) so the optimization stays honest.

How to define it consistently

Start clock: first application OR first sourced contact (not "role opens")
Stop clock: candidate accepts offer (not "candidate starts")
Unit: calendar days, not business days (cleaner, harder to game)
Track median, not mean — a few outliers skew the mean badly
Segment by source (referral vs LinkedIn vs job board) — these run at different speeds

Common benchmarks (calendar days)

Engineering / specialist roles: 30-45 days
Sales: 20-35 days
Operations / admin: 18-25 days
Senior leadership: 60-90 days (typical, often longer)
Referrals: 30-40% faster than other sources

When low time-to-hire is bad

If time-to-hire is dropping while 90-day attrition is rising or first-year performance ratings are dropping, the funnel is too lenient. Speed at the cost of fit is hidden churn. A healthy funnel optimizes for both — a slightly-longer time-to-hire that produces hires who stay 2+ years is much better than a 14-day average where 30% leave within 6 months.

Frequently asked questions

Time-to-hire vs time-to-fill — which should you track?

Both, but they answer different questions. Time-to-hire tracks the candidate experience (how fast we move people through). Time-to-fill tracks the role experience (how fast we close vacancies). Recruiting teams should optimize for time-to-hire; hiring managers care about time-to-fill.

What's a good time-to-hire?

Industry-dependent. 30-45 days is the broad average for knowledge work. Faster than 20 days usually means either a referral-heavy pipeline or a too-loose process. Slower than 60 days usually means a leadership-level role or a process problem.

How do you reduce time-to-hire honestly?

Tighten the interview loop (4-5 stages, not 7-9), pre-commit interviewer availability windows, use structured rubrics so debrief decisions happen the same day, and pre-write offer letter templates so offer-out happens within 24 hours of decision.

Should time-to-hire include the notice period?

No — stop the clock at offer acceptance, not start date. Including notice-period days makes the metric uncomparable across geographies (Germany has 3-month notice as standard; the US has 2 weeks).