What's a 'good' time-to-hire?

Heavily depends on role profile. 2026 benchmark for DE mid-market: junior 25-35 days, mid 35-50, senior 50-90, tech-senior 60-120. Significantly above, at least one stage bottleneck is active. Significantly below often signals 'we accept too quickly' (check quality of hire).

Should we make time-to-hire public?

Internally transparent yes, externally (to candidates) as 'we'll respond in X days'. 'Response in 7 days, final decision in 21 days' on the careers page is a strong signal. But: only communicate what you can hold. A broken SLA hurts more than none.

What about time-to-productivity post-hire?

Outside the ATS world - it's an onboarding metric (in Personio / HeavenHR / etc.). But: good recruiting produces hires that become productive faster. Correlation is real, measurement lives outside KI BMS.

KI BMS

Pricing

Guides

Measuring + improving time-to-hire - what the number actually says

Time-to-hire is the most-measured and most-misunderstood HR metric. Here's how to define it cleanly, which bottlenecks it reveals in most teams - and when to ignore it.

Reporting

Time-to-hire

Guide

Julia YukovichCo-Founder + CEO

·April 2, 2026·

3 min read

Key takeaways

Time-to-hire = days between role publication and signed contract. Not application to contract (that's time-to-fill).

Median beats mean. A role open 6 months distorts the mean massively and tells you nothing about the typical role.

Per-stage measurement matters more than the total. Bottlenecks almost always live in a single stage.

2026 benchmark (DE mid-market): Junior 25-35 days, Mid 35-50 days, Senior 50-90 days. Very wide spans because role profile dominates.

Step by step

1. Agree + document the definition

10 minutes: write in your team wiki: 'Time-to-hire = calendar days between data.opened_at and data.contract_signed_at on the Application'. Make sure everyone knows the same definition - debating the number is useless if the definition wobbles.

2. Keep role status clean

data.opened_at is auto-set on 'publish'. data.contract_signed_at you fill manually in the hire dialog (KI BMS asks in the hire modal). If this data has gaps, the time-to-hire analysis is unreliable.

3. Calculate per-stage aggregation

In Reports tab: activate 'Time per stage' chart. Shows for each closed application how long it sat in each stage. Focus on median per stage - reveals the bottleneck.

4. Identify + address bottleneck

Review backlog? Activate KI screening + automate receipt with timeframe. Hiring-manager bottleneck? SLA + auto-reminder after 48h. Offer bottleneck? Pre-approved salary bands + direct-send template.

5. Re-measure quarterly

Bottleneck optimisation only shows after 1-2 quarters. Quarterly check whether median time-per-stage improved. Watch mean tricks: a single hire with 200 days time-to-hire can improve mean if previously excluded - read median.

The definition you must agree on

Time-to-hire is constantly measured differently, making the number incomparable across tools + teams. Our definition: calendar days (not workdays) between the day the role went public and the day the contract was signed by both sides. A role never hired has no time-to-hire (it's 'open' or 'closed without hire').

Time-to-fill is the other common metric: days between role creation (internal, before publication) and contract. Time-to-fill is always longer than time-to-hire (approval + pre-publication lead time counts), and is measurement-trickier because 'role creation' is subjective.

Three bottleneck patterns in 80% of teams

One - 'review backlog': 7+ days pass between application receipt and first review. Cause: HR overloaded, applications read in batches. Fix: KI pre-sort with score orders the queue so top 20% are visible in the first 30 minutes. Effect: -3 to -5 days time-to-hire per role.

Two - 'hiring-manager bottleneck': 5+ days between 'HR says: invite' and actual invite. Cause: hiring manager hasn't responded. Fix: explicit SLA with hiring manager (e.g. '48h response on recommendation'), auto-reminder after 48h. Effect: -2 to -4 days.

Three - 'offer bottleneck': 4+ days between 'we'll offer' and 'offer sent'. Cause: salary/contract discussion, approval loop. Fix: pre-approved salary bands per role, contract templates, direct send. Effect: -2 to -3 days.

When time-to-hire becomes irrelevant

For senior/specialist roles with long searches, time-to-hire is a poor optimisation metric because the dominant factor is 'did we find the right person' - not 'did we decide quickly'. A senior backend role open 90 days because the first 60 days no one with the profile arrived isn't an HR-speed problem, it's a sourcing-reach problem.

Rule of thumb: time-to-hire is a junior/mid volume metric. For senior roles, 'quality of hire' (12-month performance of hire) and 'sourcing reach' (how many qualified profiles we actively contacted) matter more.

FAQ

Frequently asked

Share this article

Try KI BMS

Free plan, no credit card. We host in Germany. You can export and delete everything self-serve.

Written by

Julia Yukovich

Co-Founder + CEO

Julia is one of the Co-Founders. She handles design, product direction, and most of the support replies that arrive in the morning.

julia.yukovich at aicuflow dot comLinkedIn