Time to hire by seniority: 2026 benchmarks

By SkavanderHR · 13 September 2026

A non-executive hire now takes a median of 39 days and an executive hire 45, on SHRM’s benchmarking. Specialist technical roles run far longer: around 48 days for blended technology work, 62 for engineering, and close to eight months for an open IT position in Germany. The spread, not the median, is the number to plan against.

Key takeaways

• The median has improved slightly: 39 days for non-executive roles, down from 44, and 45 days for executive roles.
• Specialist roles do not follow the median. Engineering averages 62 days, IT overall 63 to 68, and cybersecurity commonly 3 to 6 months.
• A fixed tail sits after the decision: 14 to 21 days from offer to start, on top of 42 days from posting to offer for engineers.
• Screening cost is measurable and large, but it is not what separates a 39 day role from an eight month one.
• The part that stretches with scarcity is finding a suitable person at all, and it is the only stage that can start before the requisition opens.

What does a hire take in 2026, by seniority and role?

Published time to hire and time to fill benchmarks, by role and seniority

Role band	Reported duration	Source
All roles, non-executive	Median 39 days, improved from 44	SHRM, State of Recruiting benchmarking
Executive	45 days	SHRM, State of Recruiting benchmarking
Blended technology	Median around 48 days, spread 48 to 89 days by role and seniority	KORE1; Consultadd
Engineering	62 days on average, globally	Workable data, via KORE1
IT roles overall	63 to 68 days	GDH
Cybersecurity	Commonly 3 to 6 months	GDH, summarising staffing-firm sources
Data engineering	Three to four weeks longer than blended tech, for a clean mid to senior search	KORE1
Open IT position, Germany	Almost eight months on average	Bitkom Research
Offer to start, engineers	14 to 21 days, on top of 42 days from posting to offer	squadxp benchmarks, via Rockstar Developer University

Sources: SHRM’s State of Recruiting benchmarking for the all-roles and executive medians; KORE1, Consultadd and GDH for the technology, IT and security bands; Workable’s own data via KORE1 for engineering; Bitkom Research’s German IT labour market study for the German figure; squadxp via Rockstar Developer University for the offer to start tail. The medians come from a professional body’s survey; the role-level bands come from staffing firms and vendors, so treat them as directional and compare like with like before quoting one at a client.

Two cautions before anyone benchmarks themselves against this. Time to fill and time to hire are not the same measurement, and sources use them loosely: one counts from the requisition being approved, the other from the posting going live, and the gap between those two dates can be weeks on its own. And a median across all roles tells a specialist recruiter almost nothing, because the distribution has a long tail and the roles you struggle with live in it.

Where do the extra days actually sit?

Honestly: none of the published benchmarks above splits one hire into sourcing, screening and offer time with a clean number for each. Anyone who gives you that split with three neat percentages has estimated it. What the same sources do let you do is bound the stages.

The offer stage is bounded and short. For engineers, offer to start adds 14 to 21 days, and no process change removes a notice period. It is a scheduling fact, not a bottleneck.

Screening is expensive but roughly proportional to volume. With an average of 254 applicants per posting, one vendor synthesis puts the reading pass on the order of 23 hours per hire, with about 8% of applicants passing the first screen and roughly one hire per 200 applications. Those figures are directional, from a vendor blog rather than a benchmarking body, but the shape is not in doubt: screening consumes recruiter hours at scale. Note what it does not do. Screening time grows when too many people apply, and the roles that take eight months are the roles where hardly anyone applies at all.

That leaves the one stage that expands without limit. If the qualified population is small, or employed, or simply not reading postings, the calendar does not fill with screening work. It fills with waiting. The requisition sits open, the weekly hiring meeting reports no new candidates, and the days accumulate against nobody’s effort. That is what the difference between a 39 day median and an eight month German IT vacancy is made of.

Why does a longer search cost more than the extra days suggest?

Because the delay compounds in three directions at once. The work does not get done or lands on the team that is already stretched. The candidates you did interview early go cold or take another offer while the search continues. And a posting that has been public for months tells every later candidate that this role is hard to fill, which is not the story you want them reading.

What this means for a company of twenty to five hundred people

Benchmark yourself against the band your role sits in, not the headline median, and measure from the same start date every time. If you are near the band, your process is fine and you are looking at a market problem. If you are far outside it, look first at how many suitable candidates entered the process at all, before rebuilding the interview loop.

Then separate the two levers. The loop is yours to compress: fewer stages, faster feedback, a decision by a named person. The finding is what a comparison of an agency, RPO, an embedded recruiter and a standing monthly search is really about, and for a scarce role it is where almost all of the calendar hides. A role such as SAP consulting is a good example of the trap: the specialism is narrow, published day counts for it do not exist, and the search runs long for reasons no interview redesign will touch.

What a standing search changes about the clock

We treat finding people as a continuous monthly job rather than something that starts when a requisition opens. The system looks through professional networks and company websites for everyone in your market who matches the criteria for one specific role, and takes care of reaching every one of them about it. Everyone relevant is usually reached within two weeks of the search opening, which is the part of the timeline that normally has no upper bound, and it costs about a tenth of a recruiting agency. Your team still runs the interviews, so the days you save are the ones that were being spent waiting.

The median is not your problem. The tail is.

Numbers from our own searches. Written and checked by SkavanderHR.