Extended definition
Time to hire is the metric most directly tied to candidate experience. It captures how long the company takes from the moment a candidate is engaged — applied, sourced, referred — to the moment they have a signed offer.
Unlike time to fill, time to hire excludes pre-candidate process delays (req approval, sourcing strategy, hiring manager availability before sourcing starts). That makes it the cleaner measure of the candidate-facing process and the better diagnostic for whether the loop is moving fast enough to compete for strong candidates.
Time to hire and time to fill are complementary; serious TA teams track both.
How to calculate time to hire
The standard formula is:
Time to hire = Date offer accepted − Date of first candidate contact
“First candidate contact” is the moment the candidate enters the funnel — application date for inbound, sourcing-outreach date for outbound, referral submission date for referrals. Different sources have slightly different start dates; consistency within a company matters more than perfect comparability across companies.
Two calculation variants:
Per-hire time to hire — The headline number for an individual hire. Useful for spotting outliers and individual case retrospectives.
Cohort time to hire — Average or median time to hire across all hires within a period.
The reportable trend metric. Median tends to be more useful than mean because long outliers distort averages.
Industry benchmarks for time to hire are commonly cited around 23-30 days across general roles in mature TA functions, with technical and senior roles running longer. As with time to fill, the most useful comparison is the company’s own history broken down by role family, not aggregate benchmarks that mix categories.
The gap between time to hire and time to fill is the pre-candidate process — req approval, intake, sourcing setup. A large gap signals slow front-end work; a small gap signals candidate-side process is the bigger lever.
Why time to hire matters
Time to hire is the metric candidates actually experience. From their side, the hiring process is the days between their first contact and the offer — everything before that is invisible.
Long time to hire correlates directly with offer decline and competitive losses. Strong candidates in active search are usually in three to five processes simultaneously; whoever moves fastest often wins, especially for in-demand skills.
Talent leaders use time to hire as the diagnostic that distinguishes “we’re slow because of our process” from “we’re slow because reqs sit too long before sourcing starts.” Improving the wrong one wastes effort.
Common mistakes and misconceptions about time to hire
- Conflating time to hire with time to fill — They measure different things. Time to hire excludes pre-candidate delays; time to fill includes them. Reporting one as if it were the other distorts diagnostic conversations.
- Inconsistent “first contact” definitions across hires — If one recruiter starts the clock at application and another at first response, the data isn’t comparable. Standardise the start point.
- Reporting only mean time to hire — Outlier searches that ran 120 days drag the mean. Median time to hire is usually a better representation of typical performance.
- Treating time to hire as a candidate-experience proxy without measuring it directly — Time to hire correlates with experience but isn’t a substitute for direct candidate feedback. Strong-NPS hires can have long time to hire if the experience along the way was good; bad-NPS hires can be fast.
- Optimising time to hire at the expense of decision quality — Faster decisions aren’t always better decisions. The goal is the fastest process that still produces sound hires, not the fastest possible process.
Frequently asked questions
What is time to hire?
Time to hire is the number of days between a candidate's first contact with the company and their acceptance of the offer. It measures the candidate-side journey through the hiring process, not the full requisition lifecycle. It captures how long the company takes from the moment a candidate is engaged — applied, sourced, referred — to the moment they have a signed offer.
What's a good time to hire benchmark?
Benchmarks commonly cited for general roles sit around 23-30 days in mature TA functions. Technical, senior, and specialist roles run longer (often 45-90 days). The right benchmark for any company is its own historical performance broken down by role family rather than aggregate industry averages.
How is time to hire different from time to fill?
Time to hire measures from the candidate's first contact to offer acceptance — the candidate-side journey only. Time to fill measures from requisition opening to offer acceptance — the full process including pre-candidate delays. The gap between the two reveals whether front-end or candidate-side process is the bigger constraint.
Why does time to hire matter more for candidate experience than time to fill?
Because candidates only experience the time-to-hire window. The pre-candidate work — req approval, sourcing setup — is invisible to them. From the candidate's side, slow time to hire feels like the company doesn't take them seriously, regardless of why the broader process is slow.
How do you reduce time to hire without sacrificing quality?
Tight interview loop scheduling (no week-long gaps between conversations), faster debriefs (within 24 hours of the final interview), pre-aligned compensation parameters so offers move quickly, and structured sourcing briefs so screening starts faster. Decision quality stays intact when the speed comes from process discipline, not shortcut decisions.