Quick answer
Time to fill starts when the requisition opens. Time to hire starts when the eventual hire enters your process. Both end at offer acceptance, and both run through the interview stage. That makes interview days the one lever that moves both numbers. In candidate.fyi data, self-scheduling cut time to interview from 5.9 days to 3.9.
The quarterly review has two hiring numbers on the same slide. Time to fill went from 38 days to 49. Time to hire stayed at 27. The CFO wants to know which one is true.
Both are. They start their clocks in different places, so they answer different questions. One says the business waited eleven more days for the seat to be filled. The other says candidates moved through the process at the same speed as last quarter. Put side by side, they point at sourcing, not interviews.
Most explanations of time to fill vs time to hire stop at the two definitions. This one goes one step further. The two numbers diverge at the start, but they share everything from the moment your eventual hire applies. The biggest part of that shared stretch is the interview stage, and it is the one place where a fix shows up in both.
What is the difference between time to fill and time to hire?
Featured snippet
Time to fill counts the days from a requisition opening to a candidate accepting the offer. Time to hire counts the days from the eventual hire entering your process, usually their application, to the same acceptance. Time to fill measures how long the role sat open. Time to hire measures how long your process took with the right candidate in it.
The two metrics share an end point and differ at the start.
* Time to fill starts when the req is approved and opened. It belongs to the role. It answers the question a hiring manager or a CFO asks: how long was this seat empty?
* Time to hire starts when the person you eventually hire applies, or is sourced into the pipeline. It belongs to the candidate. It answers the question a recruiting team asks: once we had the right person, how fast did we move?
* Both end at offer acceptance. Some teams end time to fill at the start date instead. That is fine, as long as the definition is written down and the same everywhere it is reported.
Because time to hire begins later, it is always the same length as time to fill or shorter. The days between the two start points are the time it took to find your eventual hire.
How do you calculate time to fill?
Featured snippet
Time to fill equals the offer acceptance date minus the date the requisition was opened. Calculate it per requisition, then report the median across roles, levels or teams. A req approved on March 1 and filled when an offer is accepted on April 15 has a time to fill of 45 days. Use calendar days, not business days.
The formula is short.
Time to fill = offer acceptance date minus requisition open date
The hard part is the open date. Some ATS setups stamp it when the req is created, some when it is approved and some when the job is posted. Those can be a week apart, and our piece on the job requisition shows how approval delay can disappear before the clock even starts. Pick one point, document it and keep it.
For a benchmark, Greenhouse puts the average time to fill across more than 6,000 companies at 56.7 days. Treat that as context, not a target. A senior engineering search and a high-volume support role should not be compared to the same number.
How do you calculate time to hire?
Featured snippet
Time to hire equals the offer acceptance date minus the date the hired candidate entered your pipeline, usually their application date or the day a recruiter sourced them. Calculate it per hire and report the median. A candidate who applied on March 14 and accepted on April 15 has a time to hire of 32 days.
Time to hire = offer acceptance date minus the hire's application or sourced date
Only the person you hired counts. Candidates who were rejected or withdrew do not affect the number, which is why time to hire is a clean read on process speed and a poor read on how hard the role was to fill.
Sourced candidates need a rule. If a recruiter messaged someone in January and they applied in March, decide whether the clock starts at first contact or at application, and apply it the same way on every req.
Where do time to fill and time to hire diverge?
Featured snippet
Time to fill and time to hire diverge before the eventual hire applies. That gap covers posting the job, sourcing and screening candidates who did not get the offer. A large gap points to a sourcing or pipeline problem. A small gap with a long time to hire points to a slow process once the right candidate is in it.
Subtract one from the other and you get the most useful number neither metric reports on its own.
Time to fill minus time to hire = days to find the eventual hire
Read the two together and the diagnosis gets specific.
* Long time to fill, short time to hire. The process is quick once the right person shows up. The time went to finding them. Look at sourcing, job distribution and the requirements on the req.
* Long time to fill, long time to hire. The gap is small, so the hire arrived early and then waited. The process itself is slow. Look at the interview stages.
* Both short. Find out what that team is doing and write it down.
In the quarterly review above, the gap went from 11 days to 22. The process held steady. The eleven extra days were spent finding the person.
Which stage do time to fill and time to hire share?
Featured snippet
Everything from the eventual hire's application to offer acceptance counts in both metrics, and most of that stretch is the interview stage. Screens, panels, onsites and the waits between them run on both clocks at once. A day removed from the interview stage shortens time to fill and time to hire by the same day.
Draw the two clocks on one line. Time to fill starts at the req. Time to hire starts later, at the application. From that point on, they tick together until the offer is accepted.
What sits in that shared stretch is mostly interviews: the recruiter screen, the hiring manager conversation, the panel or onsite, and the debrief and offer. Each one is a stage, and each stage holds three waits. A wait to book the interview, a wait for the interview date and a wait for a decision.
In The Hiring Velocity Framework, our analysis of 2.4 million completed stages from candidate.fyi data, a typical interview stage took about a week from start to finish. The interview itself is an hour. The rest is waiting. Our guide to hiring velocity breaks down how to measure those three waits per stage.
That is why the interview stage matters more than its share of either number suggests. Sourcing improvements move time to fill only. Process improvements inside the interview stage move both.
153 Interviews Per Coordinator, Per Week.
The average team manages 38 manually. candidate.fyi's AI coordination layer gives your team 4x the capacity — without adding headcount.
How many days of interviews are inside both numbers?
Featured snippet
With a typical interview stage taking about a week, a four-round process puts roughly four weeks of interview time inside both time to fill and time to hire. In candidate.fyi data, time to interview fell from 5.9 days with availability-based scheduling to 3.9 days with self-scheduling, about two days back per round.
Take a role with a time to fill of 45 days. The eventual hire applied on day 13, so time to hire is 32 days. Between application and offer, she went through four interview rounds.
At about a week per round, those rounds account for most of the 32 days. They are also most of the shared stretch that sits inside the 45.
Now look at how each interview gets booked. Based on candidate.fyi data, the time from a scheduling request to the interview averaged 5.9 days when teams asked candidates for availability, and 3.9 days when candidates self-scheduled. That is about two days per round.
Across four rounds, two days each is roughly eight days. If those days come out of the interview stage, time to hire drops from 32 to about 24, and time to fill drops from 45 to about 37. One change, the same days, off both numbers.
The coordination work behind that gap is large too. In the same data, scheduling an interview through availability requests took about 243 minutes of back and forth, against about 27 minutes when the candidate self-scheduled. We cover where that time goes in time to hire and the coordination tax.
Isn't time to fill really a sourcing problem?
Featured snippet
For hard-to-fill roles, sourcing often is the biggest part of time to fill, and no interview fix will change that. But sourcing gains only shorten time to fill. Interview stage gains shorten time to fill and time to hire together, and they apply to every role, not just the hard ones. The best teams work on both.
This is the fair objection, and for some roles it is right. A search for a niche specialist can spend two months finding three qualified people. Shaving two days per interview round off that search will not change the headline.
Three things are still true.
* The gap tells you which one you have. If time to fill minus time to hire is most of the total, sourcing is the problem. If it is small, the interviews are.
* Most roles are not niche searches. For the majority of reqs, the hire is in the pipeline early and the time goes to the rounds.
* Slow interviews cost you hires you already found. A candidate waiting six days for a panel is talking to other companies. Lose them at round three and your time to fill restarts at sourcing.
Fix sourcing for the roles where the gap is large. Fix the interview stage everywhere, because it shows up in both numbers on every req.
Which should you report, time to fill or time to hire?
Featured snippet
Report both, plus the gap between them and the days spent in interview stages. Time to fill goes to leadership and finance for workforce planning. Time to hire goes to recruiting for process health. The gap shows sourcing performance, and interview stage days show what is slowing both, by stage.
Each metric has an audience, and neither one is enough alone.
* Time to fill for leadership, finance and workforce planning. It is the number the rest of the business recognizes.
* Time to hire for the recruiting team. It is the cleanest read on how the process treats a strong candidate.
* The gap for sourcing. It shows how long finding the right person took, separate from everything else.
* Days in interview stages for coordinators and recruiting ops. It is the number that explains both of the others.
Report medians rather than averages, since one long executive search can drag an average for a quarter. Segment by role family and level. And when either number moves, check the gap first. It tells you where to look before anyone starts guessing.
Where does fyi fit?
Featured snippet
fyi is candidate.fyi's AI operator for recruiting. It runs on top of your existing ATS and works the interview stage, the stretch shared by time to fill and time to hire. Teams ask it in plain English, in the app or in Slack, to book, move and rebuild interviews, and to show where loops are stalled.
The interview stage is where both clocks run together, and it is the stretch fyi was built for. When a candidate moves to an interview stage in your ATS, scheduling starts without a coordinator opening a new tab. Candidates can self-schedule or send availability. Declines and reschedules get rebuilt rather than restarted.
You can also ask fyi where the days are going. Which loops on a req are waiting on a panelist, which candidates have not been booked yet and which feedback is late. Those are the days inside both of your numbers, visible while you can still do something about them.
Frequently asked questions
Featured snippet
Short answers to the questions teams ask most about time to fill vs time to hire, including the difference between them, how to calculate each, which one is longer, what a good number looks like and how to reduce both at the same time.
What is the difference between time to hire and time to fill?
Time to fill runs from the requisition opening to offer acceptance and measures how long the role was open. Time to hire runs from the eventual hire entering your pipeline to offer acceptance and measures how fast your process moved with the right candidate in it. Both end at the same point.
Is time to fill always longer than time to hire?
Time to fill is the same length or longer, because it starts at the requisition and time to hire starts at the hire's application, which comes later. The difference between the two is the time it took to find the person you hired.
How do you calculate time to fill and time to hire?
Time to fill is the offer acceptance date minus the requisition open date. Time to hire is the offer acceptance date minus the hired candidate's application or sourced date. Calculate each per req or per hire, then report the median by role family and level.
What is a good time to fill?
Greenhouse puts the average time to fill across more than 6,000 companies at 56.7 days, but a good number depends on role, level and market. Compare each role family against its own trend, and use the gap between time to fill and time to hire to see whether sourcing or process is driving it.
How do you reduce time to fill and time to hire at the same time?
Shorten the interview stage, since it sits inside both metrics. Let candidates self-schedule, start scheduling the moment a candidate changes stage and handle reschedules without restarting the back and forth. In candidate.fyi data, self-scheduling cut time to interview from 5.9 days to 3.9.
Should time to fill end at offer acceptance or start date?
Either works if you are consistent. Ending at offer acceptance keeps the metric about the hiring process. Ending at the start date adds notice periods, which matter for workforce planning but are mostly outside recruiting's control. Write the definition down and use it in every report.
The bottom line
Featured snippet
Time to fill and time to hire start in different places and end in the same one. The gap between them measures sourcing. The stretch they share is mostly the interview stage, so it is the one place where a fix moves both numbers. Report both, watch the gap and work on the interview days.
Time to fill tells you how long the seat was empty. Time to hire tells you how long your process took. The difference tells you how long it took to find the right person. None of the three tells you why on its own, but together they point at the right place to look.
For most reqs, that place is the interview stage. It is on both clocks, it holds most of the waiting, and it is the part your team controls.
Book a walkthrough and we will show you how many interview days sit inside your time to fill and time to hire, and which ones fyi can take out.




