# The Published Hiring Statistic Reference, One Row per Interview Number

*Take any published hiring number, name its clock, unit, and sample, and turn it into a figure you can compare with your own loop, or reject it.*

- Canonical URL: https://www.refolk.ai/candidates/guides/published-hiring-statistic-reference
- Pillar: Reading the market
- Format: Reference
- Published: 2026-10-23
- Last reviewed: 2026-10-23
- Reading time: 21 min
- Keywords: how long does the interview process take on average, time to fill vs time to hire for job seekers, how many interview rounds is normal, interview to offer rate average, how many interviews per job offer, is my interview process taking too long

## Key takeaways

- Time to fill starts when the employer approves the requisition and time to hire starts at the candidate's application, so SHRM's 39-day nonexecutive median includes days before anyone applied. An older SHRM report puts that pre-screening phase at roughly 12 days (derived).
- In Ashby's data the hired candidate sits about 4 rounds for a business role and 5 for a technical role, while per-hire counts of 11.7 and 17.6 describe everyone interviewed for the seat.
- Gem's 14 to 20 interviews per hire counts individual sessions, so a finalist who meets 5 people across 3 rounds adds several to Gem's count and only one to Ashby's.
- Published interview-to-offer rates run from 22% at startups under 500 employees to 46 to 49% in campus hiring, so using a campus rate for an experienced-hire search roughly doubles the conversion you expect.
- Interview-to-hire equals interview-to-offer times offer acceptance: NACE's 47.5% interview-to-offer rate and 69.3% acceptance work out to about 33% interview-to-hire.
- In Refolk's index, US Technical Recruiters outnumber UK ones 21,394 to 715, so check which country a benchmark comes from before you use it in a UK search.

Recruiters write hiring benchmarks like "44 days to hire", "5 rounds", or "1 in 4 interviews end in an offer" for other recruiters, and each one counts something different. This reference is for job seekers who want to use those numbers to judge their own interview loops and timeline. Each row covers one published figure from the candidate's side: where its clock starts and stops, whose interviews it counts, which population it came from, how it misleads you, and how to convert it into something you can compare with your own search or else reject.

## The five fields every hiring statistic carries

Every published hiring number is defined by five fields: clock start, clock stop, unit, population, and statistic type. If you can't name all five, you can't compare the number with your own search.

- **Clock start.** The event that starts the count. It might be requisition approval, your application, or your first interview. Get this wrong and you misread a figure by weeks.
- **Clock stop.** The event that ends the count, which is either offer accepted or offer-or-rejection. If the clock stops at a rejection, the figure includes candidates who were turned down.
- **Unit.** Days, people interviewed per hire, rounds the hired candidate sat, or individual sessions. A count of people and a count of sessions can differ by a factor of two or more for the same hire.
- **Population.** Whose hiring was measured: small businesses, campus programs, startups, enterprises, or a broad sample of new hires. Offer rates swing by a factor of two across these groups.
- **Statistic type.** Median or mean. A median is the middle value. A mean is the arithmetic average, and a handful of very long searches pull it up.

There's a sixth thing to check, the collection method, but it isn't a field you can convert. Glassdoor's figures are self-reported by job seekers. SHRM's come from a survey of HR teams. SmartRecruiters, Gem, and Ashby use timestamps from their applicant tracking systems (ATS), the software employers use to move candidates through stages. Nobody has publicly established which way each method biases the result, so note the method and don't adjust for it.

> **Rule:** No matched field, no comparison
>
> If you can't match the clock start, clock stop, unit, and population to your own search, the statistic isn't a benchmark for you. Reject it rather than eyeballing an adjustment.

## Which clock is it: time to fill vs time to hire for job seekers

Time to fill starts when the employer approves the requisition. Time to hire starts when the candidate applies. Both stop at offer acceptance. Glassdoor and NACE use shorter clocks that stop at either an offer or a rejection, so their figures aren't measuring the same span.

| Source and metric | Clock | Value (days) | Type |
|---|---|---|---|
| SHRM time to fill | Requisition to accept | 39 nonexec / 45 exec | Median |
| Gem time to hire | Pipeline entry to accept | 41 | Mean |
| Ashby time to hire | Application to accept | 30 business / 40 tech | Median |
| Glassdoor interview duration | Application to offer or rejection | 23.8 | Mean |
| NACE interview lag | First interview to offer or rejection | 27.3 | Mean |

#### The four published hiring clocks, outermost first

1. **Time to fill (SHRM)** - Requisition approval to offer acceptance, including days before anyone applied
2. **Time to hire (Ashby, Gem)** - Application or pipeline entry to offer acceptance
3. **Interview duration (Glassdoor)** - Application to an offer or a rejection letter
4. **Interview lag (NACE)** - First interview to an offer or a rejection

*Each inner clock starts later or stops earlier than the one around it, so the same search can produce four different "average" lengths.*

### "39 days" or "44 days" (SHRM time to fill)

- **Counts:** Calendar days from requisition approval to offer acceptance, with weekends and holidays included. It comes from a survey of HR teams. The current brief gives medians of 39 days for nonexecutive roles and 45 for executive roles. An older SHRM Talent Access report gave a nonexecutive median of 44.
- **Misleads by:** Including the days before the posting existed for you. People read "44 days" as interview time, but it isn't.
- **Convert:** In an older SHRM report summarised by AIHR, time to fill was 36 days and the gap between screening candidates and offer acceptance was 24, which implies about 12 days before screening (derived). Subtract about 12 days to get a rough screening-to-acceptance figure, so 39 becomes roughly 27. Since that gap comes from a different, older sample, treat the result as approximate.

### "30", "40", or "41 days" (ATS time to hire)

- **Counts:** Ashby's medians run from application to acceptance: 30 days for business roles and 40 for technical roles. Gem's mean runs from pipeline entry to acceptance and went from 33 days to 41 over its reported period.
- **Misleads by:** Mixing a median (Ashby) with a mean (Gem). Gem's pipeline entry can also come before a formal application for sourced candidates.
- **Convert:** These are the closest match to a candidate's own clock. Measure from your application date to the day you accept. If you haven't accepted yet, measure to today.

### "23.8 days" (Glassdoor interview duration)

- **Counts:** Days from application submission to an offer or a rejection letter, self-reported in 83,921 interview reviews. The US figure was 23.8 days in 2017 and 22.9 in 2014.
- **Misleads by:** Being old and including rejections. A quick rejection ends the clock early.
- **Convert:** Compare it with your application-to-decision days, counting rejections as well as offers. Don't compare it with acceptance dates.

### "27.3 days" (NACE interview lag)

- **Counts:** Days between a student's first interview and an offer or a rejection, averaged across campus recruiting at NACE member employers. The 2019 survey figure was 23.5.
- **Misleads by:** Starting at the first interview and sampling only campus pipelines.
- **Convert:** It only applies to campus searches. Measure from your first interview to the decision.

### Industry and seniority figures

- **Counts:** Glassdoor's industry split, from January to June 2017 data: Government 53.8 days, Aerospace and Defense 32.6, Energy and Utilities 28.8, Restaurants and Bars 10.2. SHRM's seniority split is executive 45 and nonexecutive 39. An older SHRM release gave 60 and 44.
- **Misleads by:** Age. The industry figures are nine years old. A healthcare figure of 27.0 shows up only in a secondary source, and no director-level figure has been published.
- **Convert:** Use the industry figures for ranking only. Government is slow and restaurants are fast. Don't use them as day counts.

## How many interview rounds is normal, and whose interviews a count includes

In Ashby's data the hired candidate sits about 4 rounds for a business role and 5 for a technical role. Bigger figures like 11.7, 17.6, 20, or 35 count everyone interviewed for the seat or every individual session, not the rounds you sit.

| Measure (Ashby data) | Business | Technical |
|---|---|---|
| Interviewed per hire, all candidates | 11.7 | 17.6 |
| Rounds the hired candidate sits | 4 | 5 |
| Interviewer hours per hire | 12.2 | 23.3 |
| Hired candidate's hours | 2.4 | 3.5 |
| Per-hire count ÷ rounds (derived) | 2.9x | 3.5x |
| Interviewer ÷ candidate hours (derived) | 5.1x | 6.7x |

**3.5x - Ashby's technical interviews per hire, divided by the rounds the hired candidate actually sits**

17.6 interviews per technical hire against about 5 rounds for the person hired (derived from Ashby's data).

For this guide, a **round** means a distinct scheduled stage you attend, with any same-day block counted once. The sources don't state this definition. I inferred it from how they count, and it's the definition to use when you log your own loop.

### "11.7" and "17.6" interviews per hire (Ashby)

- **Counts:** How many candidates are interviewed for each hire, across all candidates.
- **Misleads by:** Sounding like the length of your loop. The technical figure rose from 11.6 to 17.6 while the hired candidate still sat about 5 rounds. The cause was more applicants interviewed per hire, as the share of applications that got an interview fell from 7 to 8% to between 3.6 and 4.7%.
- **Convert:** Read it as a measure of competition for the seat. For your loop length, use 4 or 5 rounds.

That falling interview rate is the part of these numbers you can actually act on. If fewer than one application in twenty gets an interview, sending a generic resume costs you more than it used to. [Refolk](/candidates) tailors your resume to each posting from your own history, so a carefully targeted application doesn't take an evening's rewrite.

### "14 to 20" and "35" interviews per hire (Gem)

- **Counts:** Sessions, meaning individual interviews conducted, across all candidates. Gem's figure rose from 14 to 20 per hire over its reported period.
- **Misleads by:** Getting reported as rounds. Pin's write-up calls Gem's 14 to 20 figure "average interview rounds per hire", even though Gem counts interviews conducted. A finalist who meets 5 people across 3 rounds adds 1 to Ashby's count and several to Gem's, which explains most of the gap between 17.6 and 35.
- **Convert:** Don't convert it. No published figure turns sessions into rounds per candidate, so this number tells you about interviewer workload and nothing about your loop.

Rising counts often reflect pipeline volume rather than longer loops. Célia Sauthier, Director of TA at Moss, reported interview volume "up by about 30%" without more hires.

### "5 stages" and "7 or more stages" (Pin)

- **Counts:** Distinct interview stages configured for a role. Pin found that the median corporate hire passes through 5, based on more than 4,000 ATS-connected jobs, and 38.5% of roles are configured with 7 or more.
- **Misleads by:** Measuring configuration, not what candidates experienced. A role set up with 7 stages can skip some of them for a strong candidate. Same-day panels count as one stage here but as several in Gem's session count.
- **Convert:** This is close to the candidate's definition of a round. Compare it with your own stage count, counting same-day blocks once.

### "5 interviews to 2 offers" (ZipRecruiter)

- **Counts:** New hires reported completing 5 interviews to secure 2 job offers over their whole search, across all employers. An earlier survey found 4 interviews across all companies but a median of 2 for the job respondents actually took.
- **Misleads by:** Getting read as one employer's loop. The survey also never defines "interview" for respondents.
- **Convert:** This is the closest public figure to "how many interviews per job offer" from the candidate's side. Compare it with your own count of interviews and offers across the whole search, and remember the unit isn't defined.

#### One search, as ZipRecruiter's new hires reported it

| Stage | Figure | Note |
| --- | --- | --- |
| Interviews completed | 5 | Across all employers, "interview" undefined |
| Offers secured | 2 | Across the same search |
| Job accepted | 1 | The job the respondent took |

*The 5 interviews are spread across every employer in the search, not sat inside one loop.*

### Hours per hire

Ashby's interviewer hours per hire (12.2 business, 23.3 technical) measure the employer's workload. The hired candidate spends about 2.4 and 3.5 hours, roughly a sixth of the interviewer time. If an "hours per hire" headline leaves you dreading the time you'll spend, it's describing the interviewers' time, not yours.

## Interview-to-offer rate averages, by sample

Published interview-to-offer rates range from 22% at startups to between 46 and 49% in campus hiring. The spread comes from who was sampled and from whether declined offers are counted. None of these is a universal rate.

| Sample (source) | Metric | Rate |
|---|---|---|
| Campus (NACE) | Interview to offer | 46 to 49% |
| Campus, derived | Interview to hire | about 33% |
| Startups under 500 (Gem) | Interview to offer | 22% |
| Tech, overall (Gem) | Onsite to offer | 39%, from 47% |
| Small business (CareerPlug) | Interview to hire | 27%, from 48% |
| Franchise (CareerPlug) | Interview to hire | 54% fitness, 12% cleaning |

The conversion that matters most is: **interview-to-hire equals interview-to-offer times offer acceptance.** NACE's average interview-to-offer rate of 47.5%, multiplied by its 69.3% acceptance rate, gives about 33% interview-to-hire (derived). To go the other way, divide a hire rate by acceptance. Across published acceptance rates of 69% to 84%, that step moves the figure by up to a third. Nobody has publicly established how much of the spread in the table comes from population and how much from excluding declined offers.

A "1 in 4" headline usually lands between Gem's 22% startup interview-to-offer rate and CareerPlug's 27% small-business interview-to-hire rate. Those two figures measure different things, so check which one the headline is quoting before you use it. A third figure gets relayed secondhand: 72.2% for enterprise, 16.6% for mid-market, and 7.0% for small business. It hasn't been verified at the primary source, so I leave it out.

### What each rate proves about your search

- **Campus rates** prove that a pre-filtered pipeline at large member employers converts well. They don't tell you anything about an experienced-hire search.
- **Startup rates** are the nearest match for an experienced candidate applying to small companies. Gem's sample is limited to companies under 500 employees. A second Gem segment shows 14%, but its label wasn't captured, so don't use it.
- **Small-business rates** move with applicant volume. CareerPlug's interview-to-hire halved between reports while applicants per hire rose from 85 to 180, so a year-old figure can't be carried forward. The current report covers more than 60,000 small businesses and more than 10M applications.
- **Onsite-to-offer** starts at a later stage, so it runs higher than interview-to-offer for the same employers. Compare it only with your own final-round results.

> **Tip:** Your rate depends on fit, not the base rate
>
> A published rate averages over every candidate the employer interviewed, strong fits and weak ones alike. Before you read one rejection against a 22% base rate, check how well you actually matched that posting.

Every benchmark rate blends candidates who fit the role closely with candidates who barely fit, so it can't tell you whether one particular loop was a long shot. Refolk scores how well you fit each posting before you apply, which lets you separate the loops where you'd expect to beat the base rate from the ones where a rejection was always likely.

## Who runs the loops behind the benchmarks

In Refolk's index of professional profiles, US Technical Recruiters outnumber UK ones by about 30 to 1, coordinators are a fraction of the recruiter headcount, and campus recruiters are a small group concentrated at a few employers. Each of these facts narrows which hiring a benchmark actually describes.

| Population (Refolk's index) | Count | Derived ratio |
|---|---|---|
| Technical Recruiter, US | 21,394 | 29.9x the UK |
| Technical Recruiter, UK | 715 | 1.0 |
| Recruiting/Interview Coordinator, US | 6,663 | 3.2 Technical Recruiters per coordinator |
| Campus/University Recruiter, US | 888 | 24.1 Technical Recruiters per campus recruiter |

**21,394 - Technical Recruiters in the US in Refolk's index, against 715 in the UK**

A US-heavy recruiting population is a reason to check which country any benchmark was drawn from before you use it elsewhere.

Here's how each count changes how you read a benchmark. I've marked where I'm inferring rather than reporting.

- **Country.** None of the timing or offer-rate sources above says its sample covers the UK. With the UK recruiter population this much smaller in Refolk's index, UK job seekers should treat these figures as describing a different market until a local source turns up. The top UK Technical Recruiter employers in a 25-profile sample are Monzo, Meta, and Capgemini.
- **Scheduling.** There are 6,663 Recruiting/Interview Coordinators in the US against 21,394 Technical Recruiters. The ratio suggests, but doesn't prove, that the person who schedules your rounds is often shared across several recruiters. It's one possible reason gaps between rounds run longer than the interviews themselves.
- **Campus.** Only 888 Campus/University Recruiters appear in the US, and the campus sample concentrates at Jane Street, Meta, and Eli Lilly. Together with NACE's 24.9% response rate (197 of 790 member organizations), that's why campus offer rates describe a narrow, large-employer slice of hiring.
- **Agencies.** The staffing agencies K2 Partnering Solutions and Experis are among the top US Technical Recruiter employers in a 25-profile sample. My inference, which nobody has established publicly, is that loops run through agencies may not show up in employer ATS benchmarks at all. If an agency placed you, published loop counts may not include searches like yours.

## How to convert a hiring statistic to your own search

Work through seven fields in order, then convert or reject. It takes about 15 minutes per number, and most numbers fail at step 3 or step 4.

#### Converting one published figure

1. **Name the metric family** - Decide whether it is time to fill, time to hire, application to decision, or first interview to decision. Done when you can name the event that starts the clock.
2. **Name the stop event** - Offer accepted, as SHRM and the ATS vendors use, or offer or rejection, as Glassdoor and NACE use. Done when the stop event is written down.
3. **Name the unit** - Days, candidates interviewed per hire, rounds the hired candidate sat, or sessions. Done when you can say whether it counts people, sessions, or stages.
4. **Name the population and data year** - Small business, campus, startup, enterprise, or broad new-hire sample, plus the year the data was collected. Done when you could describe who was measured in one line.
5. **Name the statistic type** - Median or mean, and look for percentiles. Done when you know whether long searches are pulling the figure up.
6. **Convert to your own frame** - Subtract about 12 days of pre-screening from time to fill, multiply offer rates by acceptance, or swap all-candidate counts for the hired candidate's rounds. Done when the figure starts at the same event and uses the same unit as your log.
7. **Compare or reject** - Hold the converted figure against your own dates and counts, or mark it not comparable if any of steps 1 to 4 failed to match. Done when it is logged either way.

For step 5, SHRM's older nonexecutive time-to-fill distribution (n = 840) shows why the statistic type matters:

- 25th percentile: 28 days
- Median: 44 days
- 75th percentile: 73 days
- Mean: 54 days

The mean sits 10 days above the median because a few long searches pull it up. Wherever percentiles are published, compare yourself with them rather than with a single average.

#### Compare, convert, or reject

Horizontal axis runs from Population does not match to Population matches. Vertical axis runs from Definition does not match to Definition matches.

| Quadrant | What it means |
| --- | --- |
| Right metric, wrong sample | Use it for direction only and look for a sample like yours |
| Comparable | Hold your loop against it, using the median and percentiles if published |
| Not comparable | Reject it and log why |
| Right sample, wrong clock or unit | Convert the clock or unit, then compare |

*A published figure is only usable when both its definition and its sample match your search, or when the definition gap can be converted.*

**Statistic card, one per published number**

```
Figure as quoted:
Source and collection method (self-report / HR survey / ATS timestamps):
Clock start (requisition / application / pipeline entry / first interview):
Clock stop (offer accepted / offer or rejection):
Unit (days / people per hire / rounds the hire sat / sessions):
Population (small business / campus / startup / enterprise / broad new hires):
Data year:
Statistic type (median / mean / percentile):
Conversion applied (e.g. minus ~12 days pre-screening; x acceptance rate; replaced with rounds):
Converted figure:
Verdict (compare / direction only / reject):
```

*Fill one card per figure you plan to rely on; leave a field blank only if you then mark the verdict "reject".*

## How published hiring statistics mislead job seekers

Most misuse comes from eight specific mix-ups, each of which can shift a figure by weeks or by a factor of two or more. Run each one as a check before you trust a number.

> **Watch out:** The most common misread is "44 days" as interview time
>
> SHRM's 44-day figure is time to fill, so it starts before the posting reached you. Comparing it with your application date makes your search look about 12 days faster than it really is (derived).

1. **"44 days" read as interview time.** It's time to fill, so it includes the days before you applied. *Check:* does the definition start at the requisition? If it does, subtract roughly 12 days (derived from the older SHRM data) or reject the comparison.
2. **"5 interviews" read as one loop.** ZipRecruiter's figure covers the entire search across all employers. The earlier per-job median was 2. *Check:* does the wording say the interviews were for the respondent's current job?
3. **Gem's "20 interviews per hire" read as rounds.** It counts sessions across all candidates. The hired person sits 4 to 5 rounds. *Check:* is the unit people, sessions, or stages?
4. **A campus offer rate applied to an experienced-hire search.** NACE samples are pre-filtered pipelines at member employers that chose to answer the survey, about a 25% response rate. Startup interview-to-offer is 22%. *Check:* does the sample hire students or experienced people?
5. **Interview-to-offer confused with interview-to-hire.** The gap between them is offer declines, and acceptance rates between 69% and 84% move the figure by up to a third. *Check:* does the rate stop at the offer or at the accepted hire?
6. **Glassdoor's 2017 industry numbers quoted as current.** One candidate-facing explainer calls the 23.8-day figure "outdated" and then quotes a 63 to 68 day "national average" without naming any source for it. *Check:* the data year, and whether the replacement figure has a named source at all.
7. **Median and mean swapped.** SHRM's older nonexecutive median of 44 days sits against a mean of 54. *Check:* which one is quoted, and whether percentiles exist.
8. **Offer-or-rejection clocks read as time to offer.** Glassdoor's and NACE's clocks stop at a rejection as well as an offer, so fast rejections may shorten the average. Nobody has measured this effect. It's my inference. *Check:* does the stop event include rejections?

> A benchmark you can't define is worse than no benchmark, because it feels like evidence.

Two more limits apply across the whole table. First, nobody has publicly established whether self-reports, HR surveys, or ATS timestamps run fast or slow, so any adjustment for collection method is guesswork. Second, vendor explainers that start from metric definitions, such as Klipfolio's, use illustrative numbers rather than measured ones. Don't cite them as benchmarks.

## Is my interview process taking too long? Holding your loop against a benchmark

Your loop is taking too long only when your own application-to-today count is past a converted median for a matching clock and population. Even then, it means you're behind half of hires, not that the process has stalled. To make that comparison you need your own dates logged the same way the benchmarks log theirs.

Log every search event against the same fields the sources use:

- Application date, which is your time-to-hire and Glassdoor start
- First interview date, which is NACE's start
- Each distinct scheduled stage, with same-day blocks counted once
- Decision date, whether offer or rejection
- Acceptance date, if you accept

Then compare like with like. For an experienced-hire business role, hold your application-to-acceptance days against Ashby's 30-day median and your round count against about 4. For a technical role, use 40 days and about 5 rounds. For a campus search, hold your first-interview-to-decision days against NACE's 27.3. If you're already past the median, the useful next step is to ask the recruiter how many stages remain. Treat that number as information, not a verdict.

**Own-loop log line, one per employer**

```
Employer | Role type (business/technical/campus) | Applied | First interview | Rounds sat | Decision date | Offer or rejection | Accepted date | Days applied-to-decision | Benchmark used | Verdict
```

*Add one line per employer; count a same-day panel as one round, and leave acceptance blank until it happens.*

To keep this reference current, re-check the mechanism rather than memorising values. Each source publishes in editions. When a new one appears, confirm three things before you update your card: the data year, whether the definition page changed its start or stop event, and whether the sample changed size or type. CareerPlug's small-business rate halving between reports shows how fast a volume-driven figure can move, so any small-business figure older than one report cycle should go back through the steps.

#### Before you use a published figure to judge your search

- [ ] I can name the event that starts the figure's clock and the event that stops it.
- [ ] I know whether the figure counts days, people per hire, rounds the hired candidate sat, or sessions.
- [ ] The figure's population (campus, startup, small business, enterprise, broad new hires) matches my search, or I marked it "direction only".
- [ ] I know whether the figure is a median or a mean, and I used percentiles where published.
- [ ] I converted time to fill by removing the pre-screening phase, or I rejected the comparison.
- [ ] I converted any interview-to-hire rate to interview-to-offer by dividing by acceptance, or the reverse.
- [ ] I compared my rounds against the hired candidate's rounds, never against an all-candidate count.
- [ ] I wrote the data year on the card and checked it against the latest edition.
- [ ] My own log uses the same start and stop events as the figure I'm comparing with.

## Frequently asked questions

### How long does the interview process take on average?

There's no single average, because each source runs a different clock. Glassdoor's self-reported US figure, measured from application to an offer or a rejection, was 23.8 days in 2017 data. ATS data from Ashby gives median application-to-acceptance times of 30 days for business roles and 40 for technical roles. SHRM's 39-day nonexecutive median is time to fill, so it includes days before you applied. Use the figure whose start and stop events match your own dates.

### What is the difference between time to fill and time to hire for a job seeker?

Time to fill starts when the employer approves the requisition, so it includes days before the posting reached you. Time to hire starts when you apply. Both stop at offer acceptance. In an older SHRM report, roughly 12 of the 36 days of time to fill came before screening (derived). Subtract about that much before you compare a time-to-fill figure with your own search, or reject the comparison.

### How many interview rounds is normal?

About 4 rounds for a business role and 5 for a technical role, counting the rounds the hired candidate actually sat, in Ashby's data. Pin found a median of 5 distinct stages across more than 4,000 ATS-connected corporate jobs, and 38.5% of roles were configured with 7 or more. Count a same-day block as one round. Figures like 17.6 or 20 per hire count candidates or sessions, not your rounds.

### How many interviews does it take to get a job offer?

ZipRecruiter's new-hire survey found people completed 5 interviews to secure 2 offers over their whole search. An earlier survey found a median of 2 interviews for the job respondents eventually took. The survey never defines "interview", so treat both as rough. Your own figure is your offers divided by the number of employers that interviewed you, and that is the one to track.

### What is a good interview-to-offer rate?

It depends on the sample. Gem's data shows 22% for startups under 500 employees, and NACE's survey shows 46 to 49% for campus hiring. CareerPlug's small-business figure is 27%, but that is interview-to-hire, so offer declines have already been taken out. Compare yourself with the sample closest to your search. To turn a hire rate into an offer rate, divide it by the acceptance rate.

### Is my interview process taking too long?

Count calendar days from your application to today and compare that with a time-to-hire median for your role type: 30 days for business roles and 40 for technical roles in Ashby's data. Passing the median puts you behind half of hires. It doesn't mean the process has stalled. Ask the recruiter how many stages are left, and only use time-to-fill figures after subtracting the pre-application phase.

---

*From the Refolk guide library. I revise these guides rather than replacing them, so the current version is always at https://www.refolk.ai/candidates/guides/published-hiring-statistic-reference*