Hiring velocity is how fast your recruiting machine turns open roles into hires. When a company needs to grow a team quickly, hiring velocity is the number leadership asks about, usually as "are we going to hit the plan?". This guide explains how to measure hiring velocity, how it relates to time to hire and time to fill, and how to improve it without hiring worse people.
What is hiring velocity?
Hiring velocity is the rate at which open roles become accepted offers, plus the speed at which candidates move through each stage. There is no single official definition, so most teams track two measures together:
- Throughput: hires (or offers accepted) per week, month or quarter, compared with the plan.
- Stage velocity: the average number of days a candidate spends in each stage of the process.
Throughput tells you whether you will hit the target. Stage velocity tells you why not.
How do you calculate hiring velocity?
Count accepted offers in a period and divide by the length of the period. Then measure average days in each stage for candidates who moved on in that period.
| Measure | Formula | Example use |
|---|---|---|
| Hiring throughput | Offers accepted ÷ weeks in period | "We are closing 3 hires a week against a plan of 4" |
| Throughput vs plan | Actual hires ÷ planned hires to date | Early warning in a hiring push |
| Stage velocity | Sum of days each candidate spent in a stage ÷ candidates who left that stage | Finding the slow stage |
| Pipeline velocity | (Candidates in pipeline × stage conversion rate) ÷ average days in process | Forecasting hires from today's pipeline |
| Requisition velocity | Roles filled ÷ roles open at the start of the period | How fast the backlog clears |
Worked example (illustrative numbers)
A team needs 40 engineering hires over two quarters, so about 1.5 a week. After six weeks it has made 6 hires, 1 a week. Stage velocity shows:
| Stage | Illustrative average days in stage |
|---|---|
| Applied → screened | 9 |
| Screened → technical test sent | 2 |
| Test → first interview | 6 |
| First interview → final interview | 8 |
| Final interview → offer | 7 |
| Offer → acceptance | 4 |
Total: 36 days from application to acceptance. The two biggest numbers, 9 days to screen and 8 days between interview rounds, are both waiting time. Cutting them to 2 and 3 days would remove 12 days from every hire, and the same team could move more candidates through in the same period.
Raise hiring velocity without lowering the bar
Cohesyve sources and contacts candidates, puts them through job simulations of the real work, and returns a ranked shortlist, so your interviewers spend time only on the strongest people.
Hiring velocity vs time to hire vs time to fill: what is the difference?
Time to hire and time to fill measure how long one hire takes. Hiring velocity measures how many hires your system completes in a period and how quickly candidates flow through it.
| Metric | What it measures | Starts | Ends | Best for |
|---|---|---|---|---|
| Time to hire | Speed for the person you hired | Candidate enters your process | Candidate accepts | Candidate experience, losing people to faster competitors |
| Time to fill | How long a role stays empty | Requisition approved or posted | Offer accepted | Workforce planning, business impact |
| Hiring velocity | Throughput of the whole system | Start of the period | End of the period | Hitting a growth plan |
You can have a decent average time to hire and poor velocity, for example when each hire moves quickly once found but you only have enough recruiter capacity to work a few roles at once. Track all three.
Why does hiring velocity matter when you are scaling?
Velocity matters because every week a planned role stays empty is a week of work not done, and strong candidates rarely wait. In a fast-growing company, a plan to hire 50 people in two quarters is really a plan to hire about two a week, every week. If velocity is half that, the gap compounds: the backlog grows, hiring managers interview more, and the team you hired to grow spends its time hiring.
Slow processes also cost candidates. People with options accept the first good offer. A long gap between stages is often where you lose them.
How do you improve hiring velocity?
Find where candidates wait, remove the wait, and fix the stage that does not scale. In most teams that means three things: screening, interview scheduling and decisions.
1. Measure stage velocity first
Pull days in stage for the last quarter's hires. Sort stages by days. Fix the slowest first. Without this you will speed up a stage that was never the problem.
2. Remove the screening backlog
If applications sit unread for a week, nothing later in the process can recover that week. Options:
- Send every applicant who meets basic criteria a short, job-relevant test immediately, so the first human review happens on test results.
- Set a rule: every application gets a decision within a fixed number of working days.
- Use a ranked shortlist so recruiters review the top of the pool first.
Cohesyve is built for this step: give it a job description and it sources candidates, contacts them, runs AI job simulations of the real work and returns a ranked shortlist before interviews.
3. Cut scheduling delay
- Block recurring interview slots in interviewers' calendars during a hiring push.
- Let candidates self-schedule; see our guide to interview scheduling.
- Run final rounds on one day where you can.
4. Collapse rounds
Each round adds days. Check what each round tests. If two rounds test the same thing, merge them. A structured interview with a scorecard usually lets you decide in fewer rounds.
5. Set feedback and decision deadlines
- Scorecards submitted the same day as the interview.
- Debrief within a set number of working days of the final round.
- Offer approval rules agreed before the role opens, with the pay range pre-approved.
6. Add capacity where it scales
More recruiters help sourcing and candidate care. They do not fix interviewer bottlenecks. Train more interviewers, and spread loops across a wider pool.
How do you raise velocity without lowering the bar?
Keep every evaluation that predicts performance and remove only waiting time and duplication. Speed that comes from skipping assessment shows up later as early attrition and poor quality of hire.
A short checklist:
- Every candidate is tested on the actual work at some stage.
- Interviewers score against the same criteria.
- You track quality of hire for each hiring cohort, and compare it before and after you speed up.
- You review early attrition by hiring month during a push.
If velocity rises and quality of hire holds, the change worked.
A weekly hiring velocity dashboard
Keep it to one screen:
| Row | Value this week | Trend |
|---|---|---|
| Hires vs plan to date | ||
| Offers out, awaiting answer | ||
| Candidates in final stage | ||
| Average days in each stage | ||
| Candidates waiting longer than your limit at any stage | ||
| Roles with no candidate in final stage |
Our posts on how to speed up the hiring process, reducing time to hire and the tools that reduce time to hire go deeper on each lever.
FAQs
What is a good hiring velocity?
A good hiring velocity is one that meets your plan with stable quality of hire. Because velocity depends on role mix, market and team size, compare against your own plan and history rather than a general benchmark.
Is hiring velocity the same as time to hire?
No. Time to hire is how long one candidate takes from entering the process to accepting. Hiring velocity is the throughput of the whole process: how many hires you complete in a period and how fast candidates flow through each stage.
How do you measure recruiting velocity per recruiter?
Divide hires (or offers accepted) by recruiter in a period, and look at it alongside the number of open roles each recruiter carries. Raw hires per recruiter rewards easy roles, so compare like with like.
What slows hiring velocity the most?
Waiting time between stages: unread applications, interview slots weeks away, slow feedback and offer approvals. Measure days in each stage to find yours.
Can automation improve hiring velocity?
Yes, where it removes waiting or manual review: self-scheduling, automated outreach, and testing every applicant at once instead of reading CVs one by one. See our guide to recruitment automation tools.