Skip to content
Hiring teams6 min read

How to Reduce Time to Hire

Time to fill hit 60 days in 2025. How to measure where your hiring days go, fix the usual delays stage by stage, and stop losing people to faster offers.

By the HireRabbit.AI team · Published · Last updated

Winding path past calendars, clocks and hourglasses, with an arrow cutting straight through to a waiting candidate
On this page
  1. How slow hiring has become
  2. Time to fill and time to hire are different numbers
  3. Measure where the days actually go
  4. The usual culprits, stage by stage
  5. Targets for each stage
  6. A weekly pipeline review that takes 20 minutes
  7. What not to cut
  8. Where software helps and where it does not

A familiar complaint in HR meetings goes like this: "Our roles take two months to fill, and the people we want take another offer before we get to ours."

In most processes the lost time comes from five or six small delays that each look reasonable on their own and together add up to weeks. The fix is to find those delays in your own data and remove them, while keeping the steps that protect candidates and the company.

How slow hiring has become

Greenhouse's Hire Standard benchmarks, published in March 2026, draw on more than 6,000 companies and over 640 million applications. They show average time to fill rising every year since 2022: 43.6 days in 2022, 47.1 in 2023, 53.0 in 2024 and 59.7 in 2025. That is a 37% increase in three years.

Each year is a stack of plates a week thick, as tall as that year's average time to fill: 43.6 days in 2022, 47.1 in 2023, 53.0 in 2024 and 59.7 in 2025. Point at a year to spread its weeks apart.

Ashby's 2026 recruiting operations benchmarks (May 2026, based on 54 million applications and 93,000 jobs) put median time to first fill at 71 days for senior roles, 63 for mid-level roles and 52 for junior roles. Read together, six to ten weeks is now normal.

Gartner's December 2025 survey of 3,072 employees found that only 48% of candidates accepted their most recent job offer, down from 54% in late 2024 and 85% in late 2023. Every week you add gives a candidate more time to find, or be found by, someone else.

Time to fill and time to hire are different numbers

Time to fill runs from the day a role is opened to the day a candidate accepts the offer. It includes everything from writing the job description to closing, and it is how long a seat sits empty.

Time to hire runs from the day the eventual hire applied to the day they accepted. It tells you how long your process holds a good candidate, which predicts whether you lose them.

Comparing the two tells you where to look. If time to fill is 60 days but time to hire is 20, the problem is before the candidate shows up: slow approvals, a late posting or weak sourcing. If time to hire is 40 of those 60 days, the problem is inside the process.

Twelve beads of five days each make a 60-day time to fill. The gap is the day the eventual hire applied, and the bright beads after it are time to hire: 20 days at rest. Point along the rod to move the gap, for example to 40 days of time to hire.

Measure where the days actually go

Export stage-change dates from your applicant tracking system for the roles you filled in the last two quarters, and calculate the median days candidates spent in each stage. Use the median, because one candidate left untouched for 90 days will distort an average.

Then look at how much of each stage is waiting: the candidate had finished their part and nobody on your side had acted. Nine days spent on a work sample is different from nine days of unopened feedback forms.

Say you're hiring an account manager, and your export shows these waits:

  • 6 days from application to first review
  • 4 days to a recruiter screen
  • 11 days to the hiring manager interview
  • 12 days from final interview to decision
  • 8 days to get an offer out

None of those numbers looks outrageous, but together they come to 41 days, and at least 25 of them are spent waiting on your team.

Each stage is as long as its wait, one dot per day, using this post's example of 6, 4, 11, 12 and 8 days. Point at a stage to fix it and watch the whole track get shorter.

The usual culprits, stage by stage

A slow or skipped intake meeting

Many searches lose their first week before a job is posted, waiting for a meeting with the hiring manager that keeps moving. A 30-minute intake meeting held within two working days of approval, with a written outcome, prevents most of the rework that follows.

Vague must-haves

When requirements are fuzzy, the team keeps discovering what it wants by meeting people. Agree on three to five must-haves at intake and write them down, separate from the nice-to-haves. If they change after the manager sees candidates, treat it as a reset and tell everyone.

Resume backlog

The first review is where candidates wait longest without hearing anything. Ashby found that candidates whose applications were closed out within a day gave a median candidate NPS of 9, while those left 50 or more days gave a median of 3. Aim for a first decision on every application within five working days, with one person owning the review queue daily.

Interviewer calendar delays

Cronofy's 2024 Candidate Expectations Report, a survey of 12,000 candidates in seven countries, found that 42% had left a recruitment process because it took too long to schedule an interview.

Ashby found automated scheduling was 26% faster than manual. Cheaper fixes: ask interviewers to block two or three standing slots each week during a search, and offer candidates a choice of times in the first message.

Feedback that takes a week

Ashby found scorecard completion rates of 49% at companies with fewer than 25 employees and 72% at companies with 500 or more, so even at larger companies more than a quarter of scorecards go unsubmitted. Make written feedback due within 24 hours, before any group debrief, and have the recruiter chase it the next morning.

Slow decisions and offer approvals

Gartner research reported by HR Dive in 2019 found a 33-day lag from interview to offer, up 84% from 2010 to 2018, and linked it to a 16% reduction in candidates accepting offers.

Agree on the salary band and approvers before the role opens, so the offer is a formality. Then set a decision date when final interviews start, so "let's see a few more" stops being an option.

Targets for each stage

StageTypical delay causeFix and realistic target
Role approved to postedIntake meeting keeps moving; must-haves unclearIntake within 2 working days; written must-haves before posting
Applied to first reviewNobody owns the review queueDaily review owner; decision within 5 working days
Screen to first interviewInterviewer calendars fullStanding weekly slots; first interview within 5 working days of screen
Interview to feedbackScorecards late or missingFeedback within 24 hours; recruiter follows up next morning
Final interview to decisionManager waits to compare more candidatesDecision date set when finals are booked; decision within 3 working days
Decision to offer sentApprovals and salary questions start lateBand and approvers agreed at intake; offer out within 2 working days
Offer sent to acceptedCandidate has other offersCall before the written offer; agree a response date

These targets are our own. Hit all of them and the time from application to accepted offer comes out at around three to four weeks for a typical role with two or three interview rounds.

A weekly pipeline review that takes 20 minutes

In a long process, nobody can usually see that a candidate has been waiting eight days. A short weekly meeting between the recruiter and each hiring manager fixes that better than any policy.

For each open role, look at every candidate who has been in a stage longer than your target, and agree one next step with an owner and a date. Check how many candidates are in each stage, how long the oldest has waited, and whether any offers are pending approval.

End by asking whether the must-haves still hold. Report time to fill and time to hire separately to leadership each month, with the slowest stage named. "Our time to fill is 58 days and 12 of those are waiting for offer approval" gets a faster response than "hiring is slow."

What not to cut

Some of the time in your process is spent on real work. Structured, consistent evaluation makes decisions faster later, because the debrief compares like with like.

Fairness checks stay too. If you use a cut-off score or automated screening, someone should look at who is being filtered out and why. Reference and background checks can run in parallel with offer approval or, with the candidate's consent, start at the final round.

Finally, keep candidates informed. The 2024 Monster Work Watch report, covered by SHRM, found that 47% of respondents who withdrew from a hiring process cited poor communication. Our guide to stopping candidate ghosting has a message for each stage.

Where software helps and where it does not

Tools help most with the waiting stages: reviewing a large resume queue, sending scheduling links and reminding interviewers about overdue feedback. They do not fix a hiring manager who has not decided what the role needs. The playbook for hiring in the AI era covers where AI fits in the rest of the funnel.

HireRabbit.AI is built for the first of those waiting stages. It scores each resume on skill match, work experience, projects and education, builds the overall score from those four, and keeps a resume with none of the must-have skills at the bottom of the list. See how scoring works.

Whatever tools you use, measure the median days in each stage, name an owner for the slowest one, and look again in two weeks. Most teams find that two or three stages account for more than half of their total time.

Put this into practice.

Free during invite-only early access. All you need is a work email, and a person reviews every request.