Skip to content
Hiring teams10 min read

Roles Taking Two Months to Fill? How to Find Where the Days Go and Win Back Candidates

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

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. A table you can use in your next hiring review
  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 something like this: "Our roles take two months to fill, and the people we actually want take another offer before we get to ours." If that sounds like your team, you are not unusual. In most processes the lost time comes from five or six small delays, each of which looks reasonable on its own, and together they add up to weeks. This guide shows how to find those delays in your own data, what typically causes them, what to change, and which steps you should keep even when everyone is in a hurry.

How slow hiring has become

Greenhouse's Hire Standard benchmarks, published in March 2026 and drawn from more than 6,000 companies and over 640 million applications, 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, and it happened while application volumes climbed.

Ashby's 2026 recruiting operations benchmarks (May 2026, based on 54 million applications and 93,000 jobs) break the number down further. Its median time to first fill was 71 days for senior roles, 63 for mid-level roles and 52 for junior roles. Technical roles took about 75 days and business roles about 60.

SHRM's 2025 Recruiting Executives Benchmarking report, covering more than 2,300 SHRM members, put median time to fill at roughly 45 days for both executive and nonexecutive positions. SHRM's figure comes from a survey of HR leaders and the other two come from applicant tracking data, so they will never match exactly. They agree on the general picture: six to ten weeks is now normal, and two months is not an outlier.

Meanwhile, candidates are harder to close. Gartner's December 2025 survey of 3,072 employees, reported by HRD in June 2026, found that only 48% of candidates accepted their most recent job offer, down from 54% in late 2024 and 85% in late 2023. When fewer than half of offers are accepted, every week you add to the process gives a candidate more time to find, or be found by, someone else.

Time to fill and time to hire are different numbers

Before you try to shorten anything, get your team to agree on what you are measuring. People use these two terms loosely, and it causes arguments where both sides are right about different things.

Time to fill runs from the day a role is opened (or the requisition is approved) to the day a candidate accepts the offer. It includes everything: writing the job description, getting approval, sourcing, screening, interviewing and closing. It is the number your leadership cares about, because it is how long a seat sits empty.

Time to hire runs from the day the eventual hire applied (or was first contacted) to the day they accepted. It tells you how long your process holds a good candidate, which is the number that predicts whether you lose them.

The difference matters for diagnosis. If time to fill is 60 days but time to hire is 20, your problem is before the candidate ever shows up: slow approvals, a slow intake meeting, a job posted late, or weak sourcing. If time to hire is 40 of those 60 days, your problem is inside the process: screening backlogs, interview scheduling and slow decisions.

Measure where the days actually go

Most applicant tracking systems record when a candidate moved from one stage to the next. Export that data for the roles you filled in the last two quarters and calculate the median number of days candidates spent in each stage. Use the median because one candidate who sat untouched for 90 days will distort an average.

A basic stage list is enough to start:

  1. Role approved to job posted
  2. Applied to first review
  3. First review to recruiter screen
  4. Recruiter screen to first hiring manager interview
  5. Final interview to decision
  6. Decision to offer sent
  7. Offer sent to accepted

Then look at two things. The first is which stage is longest. The second, often more telling, is how much of that time is waiting, meaning the candidate had finished their part and nobody on your side had acted yet. A stage that takes nine days because a candidate needed a week to complete a work sample is different from a stage that takes nine days because feedback forms sat unopened.

Say you're hiring an account manager and your export shows 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 and 8 days to get an offer out. None of those numbers looks outrageous. Together they are 41 days, and at least 25 of them are waiting on your team.

The usual culprits, stage by stage

A slow or skipped intake meeting

Many searches lose their first week before a job is posted. The recruiter waits for a meeting with the hiring manager, the meeting gets moved, and when it happens the manager is not yet sure what the role needs. 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 the requirements are fuzzy, screening slows down and so does every interview after it, because the team keeps discovering what it wants by meeting people. The fix is to agree on three to five must-have requirements at intake and write them down, separate from the nice-to-haves. If the hiring manager changes the must-haves after seeing candidates, that is fine, but treat it as a reset and tell everyone involved.

Resume backlog

With applications arriving by the hundred, the first review is where candidates wait longest without hearing anything. Ashby's data shows what that silence costs: 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. A reasonable target is a first decision on every application within five working days, which usually means someone owns review as a daily task, not something done when the calendar allows.

Interviewer calendar delays

This is where candidates tell you directly that they leave. 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. Only 9% had a first interview scheduled within a day, and 31% waited two to three weeks. Ashby found automated scheduling methods were 26% faster than manual ones. Other fixes are cheaper: ask interviewers to block two or three standing interview slots each week for the duration of a search, and offer candidates a choice of times in the first message instead of trading emails.

Feedback that takes a week

A panel of four interviewers, each of whom submits feedback "when they get a chance," can add a week to a single stage. Ashby's benchmarks 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. Set a rule that written feedback is due within 24 hours, and have the recruiter chase it the next morning. Ask for feedback before any group debrief, so each interviewer's view is recorded before the discussion shapes it.

Slow decisions and offer approvals

Gartner research reported by HR Dive in 2019 found a 33-day lag from interview to job offer, up 84% from 2010 to 2018, and said that longer decision stage was causing a 16% reduction in candidates accepting offers. The same research found that 75% of hiring managers were indecisive. The data is older, but anyone who has waited for a VP to sign off on an offer will recognize it. Two changes help most. Agree on the salary band and the approvers before the role opens, so the offer is a formality when a candidate is chosen. And set a decision date at the start of final interviews, so the hiring manager knows when "let's see a few more" stops being an option.

A table you can use in your next hiring review

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 on every application within 5 working days
Screen to first interviewInterviewer calendars full; email back and forthStanding weekly interview slots; offer times in the first message; first interview within 5 working days of screen
Interview to feedbackScorecards submitted late or not at allWritten feedback due within 24 hours; recruiter follows up the 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 sentApproval chain and salary questions start lateBand and approvers agreed at intake; offer out within 2 working days
Offer sent to acceptedCandidate has other offers; unanswered questionsCall before sending the written offer; agree a response date

These targets are not industry benchmarks. They are what a hiring team with ordinary calendars can hit once someone is watching. If you hit all of them, 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, which is close to the screen-to-final-interview spans Ashby measured (about 14 days for business roles and 18 for technical roles), plus the time to decide and close.

A weekly pipeline review that takes 20 minutes

Long hiring processes are usually a visibility problem: nobody on the team can 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.

Keep it to one agenda. For each open role, look at every candidate who has been in the same stage for longer than your target, and decide on one next step with an owner and a date. Then check three numbers: how many candidates are in each stage, how many days the oldest candidate in each stage has waited, and whether any offers are pending approval. If a stage has nobody in it, that tells you where the search is thin.

End the meeting by asking the hiring manager whether the must-haves still hold. If they have changed, the recruiter needs to know that week, not after another round of interviews.

It also helps to 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

Speeding up hiring can go wrong when teams remove the steps that protect candidates and the company. Some of the time in your process is doing real work.

Structured, consistent evaluation is one of them. Asking every candidate for a role the same core questions and scoring answers against the same criteria takes some setup, but it makes decisions faster later, because the debrief compares like with like. Skipping it to save a day tends to produce a debrief that ends with "let's bring in one more person."

Fairness checks are another. If you use a cut-off score or any automated screening, someone should still look at who is being filtered out and why, and each rejection should have a reason a person could explain. Removing that review to save time is how teams end up rejecting good candidates in bulk without noticing.

Reference checks and any background checks your role requires should also stay. You can run them in parallel with the offer approval, or start them as soon as a candidate reaches the final round with their consent, which removes most of the delay without removing the check.

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. A two-line update ("we're finishing interviews this week and will have a decision by Friday") costs nothing and keeps people from assuming they have been dropped.

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, or an offer that needs four signatures.

HireRabbit.AI is built for the first of those waiting stages. It scores each resume on four areas (skill match, work experience, projects and education) and builds the overall score from those four, and a recruiter can upload resumes in batches. A resume with none of the job's must-have skills stays at the bottom of the list, which is one more reason to write the must-haves down at intake. You can read how scoring works if you want to see how the four areas combine into the overall score.

Whatever tools you use, the order of work is the same. Measure the median days in each stage, name an owner for the slowest one, and look at the numbers again in two weeks. Most teams find that two or three stages account for more than half of their total time, and those are the ones to fix first.

Sources

Put this into practice.

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