What Is Hiring Velocity? The Formula, the Three Waits and the Benchmarks

Say one of your roles took 42 days to fill. At one company that might be a week waiting for an interview slot. At another it might be three days waiting on feedback, repeated across several rounds. The number is the same. The fix is completely different.

Time to fill can't tell those two companies apart. It measures how long the whole process took, not which part of it took the time. That is why most hiring teams know their time to fill and almost none know where the days inside it actually go.

Hiring velocity is the measure that answers that question, and it is criminally under-discussed in our industry. Search for it and you mostly find one-paragraph glossary definitions. This guide covers what hiring velocity is, how to calculate it, and what it looks like in practice, using The Hiring Velocity Framework, our analysis of 12 months of hiring activity, 7.72 million applications and 2.4 million completed stages from candidate.fyi data.

What is hiring velocity?

The word velocity can make it sound like a push for speed at any cost. It isn't. Hiring velocity is about building a recruiting system that doesn't make everyone wait. The interviews themselves take the same hour they always did. What changes is how long candidates sit between the steps.

That distinction matters because most of hiring is waiting. A recruiter can screen quickly, an interviewer can give sharp feedback and a hiring manager can decide on the spot, and a candidate can still spend a week in a single stage. The time goes to the gaps, and nobody owns the gaps.

Hiring velocity vs time to fill

Time to fill is a useful number. It is easy to calculate, it compares across roles and quarters, and the rest of the business understands it. If it goes up, something needs attention. Time to hire, measured from a candidate entering the process to accepting, has the same strength and the same limit.

Both are totals. Neither one tells you whether a candidate pool was weak, a hiring manager was slow to respond, scheduling took two weeks or feedback sat untouched in the ATS. Hiring velocity sits underneath them. It treats the process as a chain of stages and measures what happens inside each one, so a slow total becomes a specific, fixable wait.

We have looked at where those days go from a different angle in the hiring process and where the days actually go. Hiring velocity is the way to measure it.

The hiring velocity formula

Some definitions treat hiring velocity as one number for the whole process. That is easy to report and hard to act on. Breaking it into stages and waits is what makes it useful, and it only takes four timestamps per interview stage.

Stage entry. When the candidate moved into the stage.

Booked. When the interview was booked.

Held. When the interview took place.

Moved on. When the candidate was advanced, rejected or hired.

From those four points you get the three waits. Time to book is booked minus stage entry. Time to interview is held minus booked. Time to decide is moved on minus held. Add them together and you have the time a candidate spent in that stage.

Two rules keep the numbers honest. Number stages by their position in the process, first stage, second stage and so on, rather than by their names, because every company labels stages differently. And look at the slowest quarter of each wait as well as the median. The median describes a typical candidate. The slowest quarter shows you where candidates actually get stuck.

Hiring velocity benchmarks

These are the medians for each wait across The Hiring Velocity Framework data, with the fastest and slowest quarters alongside.

Time to book, about 20 hours. A quarter of interviews are booked within about an hour and a half. A quarter take more than three days.

Time to interview, about 5 days. A quarter happen within about two days. A quarter take more than a week. This is the largest single wait in the process.

Time to decide, about a day and a half. A quarter are decided within about three and a half hours. A quarter take more than five days.

Put another way, booking is roughly an eighth of a typical interview stage, deciding is roughly a quarter, and waiting for the interview date is roughly two thirds. When hiring feels slow, scheduling is usually the first thing people blame. The data points at the wait after the booking instead.

Across a whole job, the typical process has eight stages, and most jobs have between seven and nine. One stage ends and the next begins almost instantly, with a median gap of 4.5 milliseconds, so the time a candidate spends in your process is simply the sum of the time they spend in each stage. Small delays compound. A two hour delay here and a one day delay there are how a 30 day process becomes a 45 day one.

One caveat matters. Every company in this data uses candidate.fyi, which is built to reduce scheduling friction. Teams scheduling interviews by hand over email are likely to see longer waits, especially to book.

Why hiring velocity is so under-discussed

Part of the reason is tooling. An ATS is a system of record. It knows which stage a candidate is in, but the moments that make up the waits, the booking, the interview actually happening, the feedback landing, are spread across calendars, email threads and scorecards.

Part of it is ownership. A recruiter owns the req and a hiring manager owns the decision, but the time between steps belongs to everyone and therefore to no one. When the gap belongs to no one, no one measures it.

And part of it is that time to fill already exists. It answers the question leadership asks, which is how long hiring takes. It just doesn't answer the question a recruiting team needs answered, which is what to fix next. Hiring velocity does, and that is why it deserves a lot more attention than it gets.

What moves hiring velocity

Each wait has its own levers, and the report walks through them one at a time. Two findings give a sense of the size of what is on the table.

How candidates are asked to book makes a large difference. When candidates picked a time from a self-booking link, the median time to book was about 4 hours and about 1 in 9 never responded. When teams asked for availability instead, it was about 28 hours, and about 1 in 3 never replied. That wasn't a controlled test, but the pattern is clear.

Silence is its own leak. About 1 in 11 scheduling requests never turns into an interview at all. And decisions don't land evenly. Hired candidates hear back in a median of 27 hours, while rejected candidates, about three quarters of all decisions, wait a median of 41. That shows up in candidate engagement long before it shows up in a dashboard.

Round count matters too, since every interview stage adds roughly a week. We cover that trade off in how many interview rounds you should have.

candidate.fyi works on all three waits for candidates already in your pipeline. Candidates can book from a self-booking link or send their availability, including straight from the email they already opened. Interviews that have to move are rescheduled automatically rather than restarting the back and forth. And after an interview, interviewers are nudged for feedback so the decision isn't held up waiting for it.

FAQ

What is hiring velocity?

Hiring velocity measures how efficiently candidates move from recruiter ready to accepted offer. It breaks each interview stage into three waits, time to book, time to interview and time to decide, so a team can see where candidates are waiting and remove that friction.

How do you calculate hiring velocity?

For each interview stage, record when the candidate entered the stage, when the interview was booked, when it took place and when the candidate was moved on. The gaps between those four timestamps are the three waits. Report the median and the slowest quarter for each wait, grouped by stage position.

What is a good hiring velocity?

In candidate.fyi data, a typical interview stage takes about a week, made up of about 20 hours to book, about 5 days to the interview and about a day and a half to decide. Treat those as a reference point, and focus first on your slowest quarter, where most of the difference between teams sits.

What is the difference between hiring velocity and time to fill?

Time to fill is a single total, the days from opening a role to filling it. Hiring velocity measures the waits inside each stage of that process. Time to fill tells you how long hiring took, and hiring velocity tells you which part of the process took the time.

What slows hiring velocity the most?

In candidate.fyi data, the largest single wait is the time between booking an interview and the interview taking place, a median of about 5 days and roughly two thirds of a typical interview stage. Interviewer availability, notice periods and habits about how far out to book could all play a part.

Does improving hiring velocity mean rushing hiring decisions?

No. Hiring velocity targets the waiting between steps, not the steps themselves. Interviews stay the same length and assessment stays the same. What shrinks is the time candidates spend waiting for a booking, an interview date or a decision.

The bottom line

Most hiring teams can tell you their time to fill. Very few can tell you which wait inside it is costing them the most. Hiring velocity closes that gap by turning one slow total into three measurable waits per stage, each with its own fix.

The full framework goes further than this guide. It follows the three waits from the first stage of a job to the last, compares jobs of different lengths, shows where each wait tends to break down and walks through how to run the same analysis on your own ATS data. Get The Hiring Velocity Framework to see where your hiring time actually goes.