23.3 Hours of Interviews Per Tech Hire. Here's How to Cut It.

You are not imagining it. A technical loop that took a week in 2021 now eats most of a month, and Ashby's Q1 2026 numbers say you will spend 23.3 hours in interviews before anyone types an offer letter. Most of that time is coordination slop, not screening rigor, and candidates have more leverage to compress it than they think.

Where the 23.3 hours actually comes from

The 23.3-hour figure is collective interview time per technical hire in Q1 2026, versus 12.2 hours for the average business role. It is not one candidate's calendar, but it tracks closely with what a finalist actually sits through.

Ashby's April 2026 report broke the number down by function. Data roles were the worst at an average of 24.9 hours per hire. Product management and engineering sat just under. Customer support, for comparison, cleared in roughly 9.5 interviews.

The interview count matters more than the hour count, because each round is a scheduling event that can slip. Technical roles now average 17.6 interviews per hire, a 52% jump from around 11 in 2021. National time-to-fill hit 63 to 68 days in January 2026, nearly double the 36 to 44 days reported in 2023.

The role-by-role breakdown

Here is what the loop looks like by function, cross-referenced against how many people actually hold each title in Refolk's US index.

The engineering row is the tell. There are roughly 554,763 US professionals holding Software Engineer, Senior SWE, or Staff SWE titles in Refolk's index. Employers are not running 17.9 rounds because SWEs are scarce. They are running 17.9 rounds because that is the habit. Companies like Google, Microsoft, LinkedIn, and Figma have normalized the five-round loop, and mid-market employers copy the shape without the recruiter capacity to run it.

How many interview rounds is normal in 2026

Three to five rounds is the current norm for Ashby-using startups, covering a recruiter screen, a technical assessment, one or two cross-functional panels, and a founder or hiring-manager close. Anything past five is a red flag you should name out loud.

The typical shape looks like this:

1. Recruiter screen (20 to 30 minutes)
2. Hiring manager conversation (45 to 60 minutes)
3. Technical assessment or take-home review (60 to 90 minutes)
4. Cross-functional or "values" panel (60 minutes)
5. Founder or executive close (30 to 45 minutes)

That is the ceiling, not the floor. Ashby's own product data, cited in a March 2026 write-up from theresource.com, shows that moving from four or more rounds down to two structured rounds cuts time-to-hire by 20 to 30 days without meaningfully reducing placement quality. That is the single most powerful sentence to have in your pocket the next time a recruiter mentions a "quick fifth panel."

Median time-to-hire, per Ashby's 2025 data on 54M+ applications, is 41 days for technical roles and 32 days for business. Seventy-five percent of technical positions fill within 60 days. If your loop is stretching past 45 days at round four, you are already inside the tail where competing offers start closing.

The real bottleneck is scheduling, not screening

Most of the 23.3 hours is not interview time, it is coordination. Greenhouse's March 2026 benchmark, cited by candidate.fyi, puts actual interview time at 12.3 hours per hire. The remaining hours are scheduling, rescheduling, chasing feedback, and waiting for debrief slots.

Two numbers make this concrete:

• Coordinating a single slot against interviewer availability takes an average of 243 minutes of back-and-forth. Candidate self-scheduling does the same job in 27 minutes, a 9x speedup.
• When an interviewer declines, the manual reschedule takes 68 hours to resolve. At a structural 14% reschedule rate, a 17-round loop generates roughly three of these events per role. That is more than a week of wall-clock time evaporating into decline-and-reschedule cycles.

Applications per recruiter are up 411.8% since 2022, while recruiter headcount per organization fell 55.6%. One coordinator is now doing five people's jobs. This is why "let's add one more round" costs you a week, not an hour.

The Monday problem

Refuse Monday slots. In candidate.fyi's Wrapped data, Mondays generated 5,409 interviewer declines versus 3,495 on Fridays, making Mondays 40% more chaotic than any other weekday. A Monday-scheduled panel is disproportionately likely to slip into the following week, which drags your entire timeline.

Push for Tuesday through Thursday, ideally with two rounds stacked in the same day.

The 5th-round-added moment is the offer-killer

If a recruiter adds a fifth or sixth round after you thought the loop was closing, that is the point at which offers statistically fall apart. Each additional round tacks 3 to 7 days onto the timeline and raises the odds that a competing offer lands before you finish.

You are allowed to say this out loud. A script that works:

"I'm happy to do a fifth round, but I want to flag that my other process is closing next week. If we can compress this into two back-to-back sessions on Wednesday, I can hold the timeline. If not, I'll likely have a competing offer before we close."

That sentence does three things. It signals you have leverage. It offers a specific compression path. It puts the deadline on the record without making an ultimatum.

Data candidates have the most room to push. They average 19.5 interviews per hire despite the smallest US technical talent pool (~46,126 Data Engineers in Refolk's index versus ~554,763 SWEs). If you are the data hire, the company has fewer alternatives and less standing to add rounds. PM candidates interviewing at panel-heavy shops like Ramp, Brex, Wiz, or Intuit have similar leverage: the 18-interviews-per-PM-hire average is driven by those exact environments.

The five things to say to compress your loop

Here is what to send back when the loop starts ballooning: name the timeline, offer to self-schedule, cite the two-round data, refuse Mondays, and pre-negotiate the debrief.

1. "Can I self-schedule the remaining rounds?" Nine-times-faster coordination, cited above. Most modern ATSes (Ashby, Greenhouse, Gem) already support this. Recruiters juggling 5x more reqs will usually say yes.
2. "Ashby's own data shows moving from four rounds to two structured rounds cuts time-to-hire by 20 to 30 days." Cite the source. It reframes you as informed, not difficult.
3. "Can we stack rounds three and four on the same afternoon?" Panel density is the single biggest lever you control. Ask for a "super day" format.
4. "I'd prefer Tuesday through Thursday slots." No need to explain. If they ask, "Mondays run 40% more reschedules industry-wide" is a defensible answer.
5. "When can I expect the debrief?" Feedback latency, not interview count, is what pushes loops past 45 days. Get a committed date before you leave the last panel.

What long loops are actually screening for

Long loops screen for hiring-manager anxiety, not candidate quality. Mike Meyer, CIO at Salesloft, told IT Brew that tech managers want to see candidates demonstrate skills firsthand because experience alone does not speak for itself in engineering. That is the steelman, and it is fair for rounds one through three.

Past round three, the marginal information gained per round collapses. The fourth and fifth panels are almost always about consensus manufacturing, not signal. Executives want to feel bought-in. Cross-functional partners want to feel consulted. Neither of those requires a full 60-minute panel with the candidate.

You can help them get the consensus they want with less of your time:

• Offer a written work sample instead of a live coding round for the third technical touch.
• Ask if the cross-functional panel can be async: two questions answered in writing, reviewed by three people.
• Propose that the executive close be a 20-minute conversation, not a full panel.

The resume and the loop are the same fight

Getting fewer, tighter loops starts with getting into loops you actually fit. Applying broadly with a generic resume is how you end up in five loops at once, one of which balloons to seven rounds because the hiring manager was never fully sold in the first place. Loops stretch when the hiring manager is not confident, and hiring managers are not confident when the resume does not obviously map to the job.

This is the work Refolk takes off you: paste the posting, and I rewrite your resume from your own history to match what the role actually asks for, draft the cover letter, and score how well you actually fit before you spend a Wednesday afternoon on a panel. Applying to five well-matched roles beats applying to fifty generic ones, because the well-matched ones close in three rounds instead of seven.

The candidates who compress their loops in 2026 are the ones who apply to fewer, better-fit roles and then negotiate scheduling density from a position of leverage. If your resume is already tuned to the posting, you spend less time defending gaps in round four and more time closing in round three.

What "normal" should look like by December 2026

A reasonable target for a technical loop in 2026: three to four rounds, 8 to 12 total interview hours, closed inside 30 days from first recruiter call. That is achievable at any company running a modern ATS.

If you are being asked for materially more than that, the loop is not screening you harder. It is being coordinated worse. Name it, price it, and offer a compression path. If the company will not compress, that is data about how they will operate once you are inside, and you should treat it accordingly.

The 23.3-hour number is an industry average, not a law of physics. The candidates cutting it in half are the ones who came in already fit for the role and pushed back on the fifth round with a specific alternative.

FAQ

How many interview rounds is normal for a technical role in 2026?

Three to five rounds is the working norm at Ashby-using startups, covering recruiter screen, hiring manager, technical assessment, one cross-functional panel, and a founder or executive close. Ashby's own data shows two structured rounds is sufficient for hire quality, so anything above five is padding you can push back on. The median technical time-to-hire is 41 days.

Why do data roles have the longest interview loops?

Data roles average 19.5 interviews per hire, the most of any technical function, despite the US Data Engineer pool being roughly 12x smaller than the SWE pool (~46,126 vs ~554,763 in Refolk's index). Hiring managers over-index on rigor for roles they perceive as high-leverage and hard to replace, which produces longer loops for the candidates who actually have the most leverage to negotiate them down.

What do I say when a fifth interview round gets added?

Say you are willing to do it, but flag that a competing process is closing and ask to stack the remaining rounds into one afternoon. Cite Ashby's finding that moving from four-plus rounds to two structured rounds cuts time-to-hire by 20 to 30 days without hurting quality. Recruiters know this data. Naming it moves you from "difficult candidate" to "informed candidate."

Is 23 hours of interviewing actually all interviewing?

No. Greenhouse's March 2026 benchmark puts actual interview time at 12.3 hours per technical hire. The remaining time is scheduling, rescheduling (68 hours per decline event), and waiting for debriefs. Half of your loop is coordination slop, which is why self-scheduling and refusing Monday slots compress timelines faster than any other lever.