Time to hire: how long a RevOps search actually takes

A RevOps search runs six to eight weeks from signed brief to accepted offer, and ten to twenty weeks from signed brief to the new hire’s first day. The gap between those two numbers is the notice period, the largest single block of elapsed time and the one nobody controls. Published benchmarks put average time to hire at 44 to 46 days. Senior operations roles run longer.

The short answers

• Offer accepted in six to eight weeks. First day in ten to twenty weeks. Those are Rareix’s own figures for UK RevOps and GTM engineering searches, measured as cumulative elapsed weeks from the day the brief is signed.
• Average time to hire is 46.2 days and average time to fill is 63.5 days. Both figures come from the same 6,640 companies in Employ’s 2026 benchmarking. A 17 day gap between two metrics on identical data is why the two words matter.
• Senior and technical roles take longer, and the size of the penalty is published. Ashby’s benchmarks across 93,000 jobs put median time to first fill at 52 days for junior roles, 71 for senior and 75 for technical.
• If you applied online and heard nothing, the median wait before a first screening conversation is seven days. Employ puts application to screening at 7.2 days, and nine days in software and technology.
• Searches collapse at the offer stage far more often than at the sourcing stage. CIPD’s 2024 survey of 1,016 UK HR professionals found 27 per cent reported problems with counter-offers or candidates dropping out after accepting.
• A recruiter on the role cuts about a third off the elapsed time at small companies. Ashby’s startup data puts time to hire at 42 days with a recruiter involved and 62 days without, at companies under 25 people.
• Speed is not free. The stages you can compress are scheduling, decision-making and internal approval. The stages you cannot are notice periods, statutory checks and the candidate’s own decision.

This post owns the timing question for the whole site. For the steps themselves, in order, with what happens at each one, that post is the spine and this one is the clock.

Time to fill, time to hire and time to productivity

Most articles use time to fill and time to hire as synonyms. They are different measurements of different things, and the difference is not small. On Employ’s 2025 data the two numbers sit 17.3 days apart on the same set of hires.

Metric	Starts counting when	Stops counting when	What it tells you	Published figure
Time to fill	The requisition is approved or the role is opened	The candidate accepts the offer	How long your organisation takes to decide, advertise, choose and close	63.5 days in 2025, down from 67.7 in 2024
Time to hire	The eventual hire enters the pipeline, by applying or being sourced	The same candidate accepts the offer	How fast you move a person once you have found them	46.2 days in 2025, up from 45.7 in 2024
Time to productivity	The new hire’s first day	The hire delivers work at the standard the scorecard describes	Whether the hire was right and whether onboarding worked	Not comparably benchmarked. Rareix plans against 90 days

Read those two Employ rows together. Time to fill fell by 4.2 days while time to hire rose by 0.5 days. Companies got faster at the front of the funnel and no faster at all once a real person was in it. If you are diagnosing a slow search, that distinction tells you where to look.

The definitions are not universal. Workable defines time to fill as requisition approval to offer acceptance and time to hire as pipeline entry to offer acceptance, which matches Employ. iCIMS uses the same split and cites SHRM’s 54 day average for time to fill alongside a 44 day global average for time to hire. LinkedIn measures something else again: its analysis defines time to hire as the interval between a candidate submitting an application and the start date recorded on their profile, which folds the notice period into the metric and inflates it against everyone else’s.

Three organisations, three formulas, one phrase. When a vendor tells you their average time to hire, ask which of those three they mean before you compare it to yours.

Time to productivity has no comparable benchmark because almost nobody measures it. It is also the only one of the three that a hiring manager should care about, since a fast hire who is still guessing at month five has cost more than a slow hire who was useful in week three. Why ops hires fail in the first 90 days covers what happens after the start date, and this post stops at the door.

How long the hiring process takes, week by week

This is Rareix’s own timeline for a UK RevOps manager or GTM engineer search. Every number is a cumulative elapsed week counted from week zero, the day the brief and scorecard are signed. They are not stage durations. “Assessment: 2 to 4 weeks” means assessment activity happens between elapsed week two and elapsed week four, and it overlaps with sourcing, which is still running. People misread these tables as a list of durations to add up, arrive at twenty-seven weeks, and conclude the process is broken.

Stage	Cumulative elapsed weeks from kickoff
Brief and scorecard	0 to 1
Sourcing	1 to 3
Assessment	2 to 4
Client interviews	4 to 6
Offer to start date	6 to 14

The stage table is the summary. The table below is what actually happens, who is holding it up, and what the person on the other side of the process is experiencing in the same week. The candidate column is not decoration. Most of the delay you inflict is invisible to you and extremely visible to them.

Week	What is happening on your side	Who is blocking	What the candidate experiences
0	Brief written. Scorecard agreed. Salary band signed off. Panel named and interview slots held in the calendar	You. Nothing moves until the scorecard exists in writing	Nothing. The role is not public and they do not know it exists
1	Advert live. Target list built. First outreach sent. Inbound applications begin arriving	You, if the brief is unfinished. Otherwise nobody	Sees the advert or receives a first approach. Applies or replies
2	Outreach continues. Replies triaged. First screening calls booked and held	Nobody. This is the one week that runs on its own	Waiting. Median time from a recruiter approach to a candidate reply is 3.9 days
3	Longlist becomes a shortlist. Assessment briefs issued to the strongest three to six	The candidates. Screening calls have to fit around a working day	On a screening call, or starting a work sample in the evening
4	Assessments returned, scored against the scorecard, shortlist submitted with evidence attached	The recruiter and the scorers	Waiting for feedback on work they did unpaid. First real silence risk
5	First round interviews with the hiring manager	Your panel’s diary, almost always	Interviewing at 7am or in a lunch hour, without telling their employer
6	Second round or panel. Debrief. Decision made	The hiring manager and anyone else whose opinion is collected late	Waiting for a decision they know has been made in a room they were not in
7	Offer approved internally. Verbal offer made. Terms negotiated	Finance, the founder, or a compensation committee	Deciding. Talking to a partner. Possibly running a second process to a deadline
8	Offer accepted. Contract issued and signed. References and right to work started	The candidate, then compliance	Resigning. This is the week the counter-offer arrives
9	Notice week one. Background checks running in parallel	Nobody you control	Handing over, and being talked out of leaving by people they like
10	Notice week two. Start date confirmed in writing	The candidate’s employer	Same, with less of it
11 to 12	One month notice ends. First day. Onboarding plan should already be written	You, if the 30/60/90 plan does not exist yet	Starts, or has one week left
13 to 16	Two month notice ends here. The one month hire is now in week four	Contractual notice	In the job, or two weeks out from it
17 to 20	Three month notice ends here. Start date lands	Contractual notice	Starts, three months after saying yes

Two things fall out of that table.

The first is that weeks zero to eight are yours and weeks nine to twenty belong to somebody else. If you want a shorter search, all of the available savings sit in the first eight weeks. Arguing about the notice period is arguing about the half of the timeline you have no purchase on.

The second is that the candidate is waiting during almost every week where the blocking column names you. Week four and week six are where good candidates leave a process, and neither of them is a week where anything is visibly happening.

Average time to hire: what the published benchmarks say

The benchmarks disagree, and they disagree for a reason worth understanding before you use any of them as a target.

Source	What it measures	Headline figure	Sample	Period
Employ, 2026 Hiring Benchmarks	Time to fill, and separately time to hire	63.5 days to fill, 46.2 days to hire	6,640 companies across Jobvite, Lever and JazzHR	2025 against 2024
Greenhouse, The Hire Standard	Time to fill	59.67 days in 2025, up from 43.64 in 2022	6,000+ companies, 640 million applications	2022 to 2025
Ashby, Recruiting Operations Benchmarks	Median time to first fill, split by level	52 days junior, 63 mid, 71 senior, 75 technical	54 million applications across 93,000 jobs	January 2021 to March 2026
Josh Bersin Company and AMS, Time to Hire Factbook	Time to hire	44 days average, up from 43. Energy and defence 67, professional services 47	Half a million data points, 8 industries, 25+ countries	Multi-year
SmartRecruiters, UK analysis	Median days to fill a UK vacancy	40 days	8.8 million UK applications, 89 million globally	September 2023 to August 2024
LinkedIn, via HR Dive	Application submitted to start date	33 to 37 days for administration, 47 to 49 for engineering	Not disclosed	2021
SHRM, as cited by Workable and iCIMS	Time to fill	42 days per Workable, 54 days per iCIMS	Not disclosed in either citation	2022 benchmarking

Four mechanisms produce the spread.

The metric is not the same metric. Employ’s own data shows a 17.3 day gap between time to fill and time to hire on the same hires. Any comparison that puts a time to fill number next to a time to hire number and calls one faster is comparing a marathon to a half.

The population differs. SmartRecruiters’ 40 day UK median covers a job mix heavy in high-volume roles that fill in days. Ashby’s 75 day technical median covers venture-backed software companies hiring engineers. Neither is wrong and neither describes your RevOps vacancy.

The direction of travel differs by source. Greenhouse shows time to fill rising 37 per cent between 2022 and 2025, from 43.64 days to 59.67. Employ shows time to fill falling 4.2 days between 2024 and 2025. Both are large datasets. They disagree because Greenhouse’s window is longer and starts in a hiring market that no longer exists, and because Employ’s customer base skews towards smaller employers filling operational roles.

Nobody agrees what SHRM said. Workable cites a 42 day SHRM average and iCIMS cites 54 days from SHRM’s 2022 benchmarking, in articles that are otherwise saying the same thing. The underlying SHRM data brief sits behind a membership wall, so the 42 and the 54 both circulate uncorrected. Treat any secondhand SHRM number as approximate.

Against all of that, Rareix’s six to eight weeks to accepted offer is 42 to 56 days, which sits at the fast end of the published range for senior roles and slightly slow against high-volume averages. That is the correct place to be for a role where the shortlist is four people and one of them is the hire.

Time to hire by function and level

Operations and technical roles run longer than the all-role average, and the penalty is consistent across every dataset that breaks the number down.

Cut of the data	Figure	Source
Junior roles, median time to first fill	52 days	Ashby, 93,000 jobs
Mid-level roles	63 days	Ashby
Senior roles	71 days, 37 per cent longer than junior	Ashby
Technical roles	75 days	Ashby
Business roles	60 days	Ashby
Engineering, globally	62 days	Workable
Engineering, research and project management	47 to 49 days median	LinkedIn
Administration, customer service, accounting	33 to 37 days median	LinkedIn
Energy and defence	67 days	Josh Bersin Company and AMS
Professional services	47 days	Josh Bersin Company and AMS
Time from first interview to last, technical roles	18 days	Ashby
Time from first interview to last, business roles	14 days	Ashby

A RevOps manager sits between Ashby’s business and technical categories and above its mid-level line. A GTM engineer sits closer to the technical figure, because the assessment is harder to design and the candidate pool is smaller. Ashby’s interview-window row explains part of the gap: technical processes take four days longer to run from first interview to last, before any decision is made.

The other structural reason ops roles run long is that the brief is usually wrong on day one. A search for a “RevOps manager” that turns out to be a search for a Salesforce administrator, or a demand generation analyst, or a chief of staff, loses two weeks in the discovery. That is not a sourcing problem and no amount of speed at the top of the funnel fixes it.

How long to wait after submitting a job application online

This section is for candidates. Everything above is the same process seen from the employer’s chair, and the numbers below are what those weeks feel like from the other side.

The short answer: expect a first response within seven to ten days, chase at two weeks, and treat four weeks of silence as a no even though nobody will tell you it is one.

What you are waiting for	Median or typical wait	Source
Application to first screening conversation	7.2 days, and 9 days in software and technology	Employ, 6,640 companies
Application review, UK	7 days	SmartRecruiters, 8.8m UK applications
Application to an interview invitation, UK	15 days	SmartRecruiters
A recruiter’s approach to your reply	3.9 days median, 70.8 per cent within 7 days	Pin, 230,000+ outreach threads
First approach to first interview	5.8 days median, 58.9 per cent within a week	Pin
Rejection if you were never interviewed	6 days median	Ashby
Rejection after you were interviewed	21 days median	Ashby
Final interview to offer letter, at employers who are good at this	64 per cent within one week	Talent Board CandE research, via Pin
Silence once you are already in conversation	Median 75 days from last recruiter contact	Pin Employer Ghosting Index, 200,000+ conversations

Three of those rows deserve reading twice.

Rejection after an interview takes 21 days against six days if you were never seen. The company already knows. The delay exists because they are holding you as a backup while a preferred candidate decides, and because telling someone no is the task everybody moves to tomorrow.

Silence is common enough to be the default rather than the exception. Pin’s index found 72 per cent of candidates in an active conversation on an open role went 30 days or more with no logged follow-up. iHire’s survey of 1,024 job seekers in October 2025 found 53 per cent had been ghosted, with 28 per cent of those after submitting an application and 20 per cent after a first interview.

The odds at the top of the funnel are worse than most applicants assume. SmartRecruiters’ UK data puts the interview invitation rate at 4.3 per cent of applications and the offer rate at 1.1 per cent, against an average of 72 applications per posting. Ashby’s passthrough rates tell the same story from inside the process: 35 per cent of candidates pass the screen, 24 per cent pass the onsite, and 81 per cent of offers are accepted.

What to do with that. Apply, log the date, and move on to the next one the same day. Chase once at day ten with a short note to a named person. If you were interviewed and have heard nothing at day fourteen, ask directly for a decision date and hold them to it. Do not stop other applications because one process feels warm, since the median employer will take longer than they told you and 21 days of post-interview silence is normal rather than a signal.

Why does HR take so long to make an offer

Because the decision and the offer are two separate events, and the second one is an internal process the candidate cannot see.

The decision usually happens in the debrief, within a day or two of the final interview. What follows is approval. On a senior operations hire that typically means the hiring manager, a finance sign-off on the band, sometimes a founder or a compensation committee, then a contract drafted by whoever owns templates. Each of those is a person with a calendar and none of them is treating your offer as their most urgent item.

Four specific things stall an offer after the decision has been made.

The band was never agreed. If nobody signed off a salary range before sourcing started, the offer stage becomes the first time finance sees the number, and the number is always higher than the placeholder in the plan. Publishing the band up front removes this entirely. Rareix’s salary benchmarks exist so this conversation happens in week zero.

Somebody’s opinion was collected late. A panel member who was not in the debrief, or a stakeholder added at the last minute, resets the decision. Ashby found the largest gap between fast and slow employers sits at exactly this point: offer turnaround differs by 3.26 days for business roles and 4.71 days for technical roles between high and low performers.

The second candidate has not finished. Employers hold an offer to keep a backup warm. It is rational and it is also how you lose the first choice, who is reading the silence as a lack of enthusiasm.

Contract admin is nobody’s job. The verbal offer lands on a Thursday and the paper arrives eleven days later because the person who generates contracts was on leave. Candidates resign against paper. A phone call will not do it.

None of these are HR being slow. They are an organisation without a decision path being asked to make a decision quickly, which it has no mechanism to do.

What actually compresses, and by how much

These are the levers with an evidence base, and what each one is worth in elapsed time.

Lever	Weeks saved	Why it works	What it costs you
A written scorecard before sourcing starts	1 to 2	Removes the rewrite in week three when the brief turns out to describe two different jobs	Half a day of the hiring manager’s time in week zero
Panel availability agreed and slots held in advance	1 to 2	Scheduling is the largest recoverable delay in most processes	Blocked diary time that may go unused
A recruiter on the role at all	2 to 3	Ashby puts time to hire at 42 days with a recruiter and 62 without, at companies under 25 people	The fee. See what a retained search buys you in speed
Deciding within 48 hours of the last interview	0.5 to 1	Ashby’s fast and slow employers differ by 3.26 days on business roles and 4.71 on technical at exactly this step	Fewer opinions collected. That is usually a gain
Two interview stages instead of four	1 to 2	Each additional stage adds a whole scheduling round on top of the hour itself	Less coverage, which a work sample can replace
Assessment run alongside sourcing	1	The shortlist arrives already scored rather than needing a fortnight of scheduling	Assessments run on candidates who will not make the shortlist
Publishing the salary band in the advert	0.5 to 1	Removes the offer-stage discovery that finance never approved the number	Internal pay comparisons become visible
Automated interview scheduling	Hours, not weeks	Ashby measures 3.7 hours against 5 hours of coordinator time per scheduling event, 26 per cent faster	Tooling. Do not expect it to change the calendar week
Buying out part of a notice period	0 to 4	Only works where the outgoing employer agrees, which is rare above one month	Cash, and a candidate who starts owing you a favour

The pattern in that table is that almost every real saving comes from a decision made before the search starts. Nothing you do in week five recovers a week you lost in week zero.

Parallel processing is the one exception worth naming precisely. References, right to work and background checks belong in the notice period, not before the start date is agreed. The Disclosure and Barring Service route is the slowest of these: police turnaround averaged 0.7 days for a basic check, 1.2 days for a standard check and 11.7 days for an enhanced check in March 2026. Run those against a twelve week notice period and they cost nothing. Run them after the last day of notice and they are two weeks of a start date you have already promised.

What does not compress

Four things are fixed, and pretending otherwise is how a plan becomes a broken promise.

Notice periods. UK statutory minimum is one week’s notice after a month’s service, which is irrelevant, because contracts override it. In UK B2B software, one month is standard at mid-level, two to three months at head-of and director level, and three to six for VP and C-suite roles. Rareix’s working assumption for a RevOps manager or GTM engineer is one to three months. A candidate on three months who accepts in week eight starts in week twenty-one, and no amount of goodwill changes that.

Statutory and regulated checks. An enhanced DBS check took 11.7 days on police average turnaround in March 2026. Referencing depends on a previous employer’s HR team replying. Right to work checks are fast, and the rest are not under your control.

The candidate’s own decision time. A senior operations candidate with a partner, a mortgage and a functioning current job takes three to seven days to accept, and they should. Compressing this by imposing a 24 hour exploding deadline works occasionally and poisons the start.

The market itself. ONS put UK vacancies at 707,000 in May to July 2026, down 2.7 per cent on the year and 10.3 per cent below early 2020, with 2.5 unemployed people per vacancy. KPMG and the REC’s survey of around 400 UK recruitment consultancies found permanent placements stabilising in July 2026 after a 45 month downturn, with starting salary growth at a six month high. More available candidates has not translated into faster senior hiring, because the constraint on an ops search was never raw supply.

Why a fast process is not always a good one

Speed is a proxy metric. It is easy to measure and it correlates with things you want, which is exactly what makes it dangerous as a target.

A search that closes in four weeks usually did one of three things: hired an internal referral, hired the first person who was available, or lowered the bar under time pressure. The first is fine and often excellent. Ashby found 52 per cent of referred candidates pass an initial screen against 35 per cent overall. The other two are how you end up rerunning the search in month seven.

Three places where speed costs you the hire you wanted.

Cutting the assessment. The work sample is the stage that feels most cuttable because it adds a week of elapsed time. It is also the stage carrying most of the predictive load. Ashby’s data shows take-home assignments were used in only 13 per cent of hires, which tells you how often this gets dropped. The evidence for work samples against interviews sets out what you lose when it goes.

Shortening the shortlist to whoever replied first. The strongest RevOps candidates are employed, busy and slow to respond. Pin’s outreach data shows a median 3.9 day reply and a 90th percentile of 16.8 days. A process that closes its longlist at day seven systematically excludes the top decile of responders, who are frequently the top decile of candidates.

Making the offer before the panel has aligned. Ashby found scorecard scores matched exactly in 62.5 per cent of cases and differed by one point in 33.5 per cent. That one point of disagreement is worth surfacing before the offer goes out. A panel that resolves it afterwards resolves it as a management problem in month three.

The counterweight is real and should be stated plainly. Slow processes lose candidates. Employ’s benchmarking put first-year turnover at 12.1 per cent in 2025, down from 23.7 per cent, in the same year that time to fill fell, which does not support the idea that faster hiring produces worse hires at population level. The argument for taking a fifth week on assessment is a quality argument, and it has to be made on the specific role. As a general principle it does not hold.

What to tell a candidate about timing, and the cost of going silent

Give the candidate a date, then either meet it or send a message on the day you miss it. That is the whole discipline and almost nobody does it.

The cost of silence is measurable. Ashby tracked candidate net promoter score against how quickly rejected candidates were archived: rejecting within one day produced an NPS of 9, ten to twenty-four days produced a 7, and 50 days or more produced a 3. The people you rejected slowly are the people who will not reply to your next approach, and in a market as small as UK RevOps, that pool is not large enough to burn.

What to say, and when.

At first contact, name the number of stages and the target date for a decision. “Three stages, decision by the 19th” is enough. Vagueness reads as disorganisation because it usually is disorganisation.

At every stage, give the next date before the candidate has to ask. If you are waiting on a panel member’s diary, say that. Candidates forgive a specific delay and they do not forgive an unexplained one.

When you slip, message on the day, not the day after. “The panel debrief moved to Thursday, I will come back to you Friday” costs thirty seconds and preserves the relationship for the version of this where they are your second choice and your first choice takes a counter-offer.

When you reject, do it the day you decide. Ashby’s 21 day median for post-interview rejections is the industry admitting it holds people in reserve without telling them. Doing it faster is free.

None of this speeds the search up. It changes who is still in the process when you get to the offer.

Counter-offers and the offer to start window

The weeks between an accepted offer and a first day are where searches most often collapse, and it is the stretch of the timeline where the employer can see the least and do the least about it.

CIPD’s 2024 survey found 27 per cent of UK organisations reported challenges with counter-offers or with candidates dropping out after accepting, and 28 per cent said they use counter-offers themselves to retain people. Those two numbers describe the same market from both ends: the practice you are a victim of is the practice you also run.

On the widely quoted claim that 80 per cent of people who accept a counter-offer leave within twelve months: that figure has no traceable primary source. An investigation by recruiter Ken Davies found zero verified sources for it, and a follow-up analysis documents the same statistic circulating as 48, 66, 80, 89, 90 and 93 per cent depending on who is repeating it. The closest thing to a real number is roughly 50 per cent within twelve months, attributed to CEB, now part of Gartner, in a 2016 Harvard Business Review piece. A recruiter quoting you the 80 per cent figure is quoting folklore, and you should discount the rest of their pitch accordingly.

The honest version is that counter-offers work often enough that you have to plan for them. What reduces the risk, in order of effect:

Ask what the counter-offer would have to be, before the offer goes out. The answer is diagnostic. A candidate who names a number is negotiating with you. A candidate who says “nothing would keep me” and can explain why is telling you the truth about their reasons for leaving.

Get the resignation date in the diary and make contact on it. The counter-offer arrives within 48 hours of the resignation, from the person the candidate has the strongest relationship with in the building. That is the moment to be reachable.

Stay in contact through the notice period. A hire who accepts in week eight and starts in week twenty has twelve weeks of silence in which their current employer is actively working on them and you are not. Lunch in week two of notice, the onboarding plan in week four, an introduction to a future colleague in week six.

Have the start date confirmed in writing on the day the contract is signed. A vague “sometime in November” is an invitation to slip.

Fix the reason they were leaving, if it is a reason your offer does not address. If the candidate is leaving because they had no career path, and your offer is 12 per cent more money for a job with no career path, the counter-offer will win and it deserves to.

The other collapse in this window is the one nobody calls a collapse: the hire starts and is gone by month four. Employ’s 12.1 per cent first-year turnover is the population figure. The specific version for operations hires is covered in why ops hires fail in the first 90 days, and the fix belongs to onboarding rather than to the search.

Count the weeks from the day the scorecard is signed

The most common mistake in planning an ops hire is starting the clock at the job advert. By then the two most expensive weeks have already gone: the fortnight spent deciding what the role actually is, which happens either before sourcing in the form of a scorecard or during sourcing in the form of a rewrite.

Set the expectation internally as two numbers, not one. Six to eight weeks to an accepted offer, ten to twenty weeks to a first day. Say both to the executive who asked when the person starts, because they are asking about the second number and everyone else in the process is managing the first.

Then measure the three intervals that tell you whether the search is healthy: days from brief to first shortlist, days from last interview to decision, days from decision to signed contract. Those three cover most of the recoverable time. If the first is over 30 days, the brief was wrong. If the second is over five, the panel was wrong. If the third is over ten, the band was never approved.

Rareix runs to those numbers and publishes them because a search that quietly slips from eight weeks to sixteen is not a slow search, it is a search that stopped being planned somewhere around week three.

Related reading

• The steps themselves, in order, from brief to offer.
• What a retained search buys you in speed, and how the three fee models price the difference.
• What to budget before you set the band, which is the week-zero decision that prevents the week-seven offer delay.
• The evidence for work samples against interviews, if you are considering cutting the assessment stage for speed.
• What a GTM engineer actually does, and why that search runs longer than a RevOps search.
• Why ops hires fail in the first 90 days, which is what happens to the time you saved.