Key takeaways
Interview length depends on the stage. As typical ranges, a first-round phone or video screen runs 20 to 30 minutes, a technical or behavioral deep-dive 45 to 90 minutes, and a working session, pair-programming round, or panel an hour or more. Per Ashby, a candidate's total interview time before an offer has held flat since 2021, at about 2.4 hours for business roles and 3.5 for technical ones. Our argument is that the longer round deserves most of your preparation, because 30 minutes of rehearsed answers separates strong candidates from well-prepared ones less well than it used to.
How long the average job interview actually runs in 2026
There isn't one clean number, and anyone who quotes a single "average interview is X minutes" figure is flattening a process that varies by stage and role. What's measurable is the shape.
These are typical ranges rather than published standards. A first-round screen, the phone or video call that decides whether you move forward, commonly runs 20 to 30 minutes. A technical or behavioral deep-dive commonly runs 45 to 90 minutes. A working session, pair-programming round, or panel can run an hour or more, sometimes split across a half-day loop.
The number that moved in the last few years is how much interviewing a company does before it commits to anyone. Ashby's recruiter productivity data shows technical roles averaging 17.6 interviews per hire, a 52% increase from roughly 11 in 2021. For business roles the figure is 11.7, up 36% from around 8. Those interviews are spread across every candidate a team talks to. For any one candidate, the same report puts total interview time before an offer at about 2.4 hours for business roles and 3.5 hours for technical roles, and says both figures have held essentially flat since 2021. Broken out by function, data roles demand the most at 19.5 interviews per hire, product management at 18, and engineering at 17.9, while customer support sits at the bottom at 9.5.
Measured in hours rather than rounds, the same report puts the team's interviewing time at 24.9 hours per data hire and 24.7 per engineering hire, against 8.9 hours for customer support. Put together, teams are spending more of their own time per hire, mostly by talking to more candidates, while the process each candidate sees has stayed about the same length. Ashby also says team interview hours have stabilized since mid-2023 after rising sharply in 2022.
Why the 30-minute screen is losing weight in hiring decisions
The screen used to be a meaningful filter. A short, structured conversation with a recruiter or hiring manager could separate people who understood the role from people who didn't, because giving a clear, relevant answer on the spot took genuine preparation and signal.
That separation got cheaper. A polished answer to a predictable question is now something almost any motivated candidate can produce with a week of practice and a few AI-assisted reps. The format of a 30-minute screen, known questions and a single pass at each, is exactly the surface that rehearsal flattens. When a prepared performance is cheap to produce, our view is that the round that rewards it sorts people less well.
We made the interviewer-side version of this argument in The Hiring Brief, our own newsletter. The 30-minute screen optimizes for the wrong signal, because the thing it measures, can this person deliver a clean answer to a known question, is the thing rehearsal makes easy and the job rarely requires. The same logic shows up in how coding rounds lost signal once candidates could lean on AI, a shift we cover in behavioral vs coding interviews in 2026.
The screen still matters. It has been demoted to a gate you clear, and the offer is earned in the longer rounds after it.
What a 30-minute screen can and cannot measure
If you've got a short screen on the calendar, the useful question is what the company can actually learn about you in that window, and what it can't.
A 30-minute screen can measure:
- Whether you communicate clearly and concisely under mild pressure.
- Whether your background actually matches what's on your resume.
- Whether you can give a coherent, relevant answer to a question you saw coming.
- Whether you're someone the team would want to spend more time with.
- Whether you've done basic homework on the role and the company.
A 30-minute screen cannot measure:
- How you handle a problem that changes shape halfway through.
- Whether you recover gracefully after a wrong turn, or freeze.
- How you reason over a sustained, unfamiliar problem with no prepared answer.
- Whether your stories survive a third and fourth follow-up question.
That gap tells you exactly how to prep for the short screen. Don't over-invest in depth the round can't see. Prepare tight, clean versions of the predictable questions, a sharp answer to why this role and why now, and two or three specific examples you can deliver without rambling. The goal is to pass without friction so you reach the round that decides. Treat the screen as a clean handoff.
Why the 90-minute working session is the round that actually decides
The longer round exists for one reason. It's long enough to outlast a script.
Early in a 90-minute session, you can run prepared material. You introduce yourself, you walk through an approach you've practiced, you cover the ground you expected. Then the interviewer does the thing the short screen never had time for. They change a constraint. They add a requirement halfway through. They ask why until your prepared answer runs out and you have to reason in real time.
That moment is the interview now. The whole point of the extra hour is to get past the rehearsed version and watch you think. Can you hold a problem in your head while the requirements shift? Do you narrate your reasoning so the interviewer can follow it, or go silent and hope the answer lands? When you take a wrong turn, do you notice and recover, or dig in?
These are signals a short screen has little room to capture. In a 2025 interviewing.io survey of 67 interviewers, mostly at FAANG and FAANG-adjacent companies, 75% said AI assistance in coding interviews lets weaker candidates pass interviews they would otherwise have failed. That concern is one reason to expect more weight on the longer conversation, which is harder to fake.
How to prepare differently for a 30-minute screen vs a 90-minute deep-dive
Same job, two rounds, two completely different prep strategies. Matching the wrong prep to the wrong round is how strong candidates flame out, either by under-preparing the screen or by walking into the working session with nothing but memorized answers.
For the 30-minute screen:
- Write tight versions of the five or six questions you can see coming, then practice them out loud until they're clean and short.
- Lock a one-sentence answer to why this role, why this company, why now.
- Pick two or three specific examples with a real outcome you can name, and keep each under 90 seconds.
- Do enough company homework to ask one sharp question at the end.
For the 90-minute deep-dive:
- Stop memorizing answers. The round is built to outlast them.
- Get reps on hard problems with the conditions changing mid-stream. Solve, then have a partner or tool move the goalposts and force you to adapt.
- Practice narrating your reasoning out loud. Silent, correct work gives the interviewer no view of your thinking.
- Rehearse recovery. Deliberately take a wrong path, catch it, and talk through the correction. Recovering cleanly is a signal in its own right.
- For technical loops specifically, our technical interview preparation guide walks through how to build this kind of sustained problem-solving prep.
The asymmetry is the whole point. The screen rewards polish. The deep-dive punishes it the moment the script runs out.
What the length of your interview tells you about the company's process
The length and structure of a loop also leak information about how the company hires, which is worth reading before you walk in.
A process that's all short screens, three or four 30-minute conversations and a quick offer, usually signals one of two things. Either the team has a fast, confident process and knows what it's looking for, or it's relying on surface signal and hasn't built a round that tests real work. You can tell which by whether anyone goes deep at all. If no round runs past 45 minutes, the company may be optimizing for speed over signal, and the bar can swing either way once you're inside.
A process anchored on a long working session, take-home plus a 90-minute review, or a half-day on-site, signals a team that wants to see sustained work before committing. That's usually a sign of a more mature process, though it also means the bar in that room is the real bar. In Ashby's data the functions with the most interviews per hire are data, product management, and engineering, at 19.5, 18, and 17.9.
Neither shape is automatically better for you as a candidate. But knowing which one you're in tells you where the decision actually gets made, and therefore where to spend the hours.
The prep stack that survives both rounds
Here's the part that ties it together. The prep that clears a short screen feeds the prep that clears a long deep-dive, in order.
Start with the script work, because the screen demands it and because you can't improvise well on a foundation you haven't built. Write your core answers, say them out loud, tighten them. That's the floor.
Then deliberately break the script. This is the step most candidates skip, and it's the one that separates people who pass screens from people who get offers. Take your prepared answers into a setting where the questions change, the constraints shift, and someone keeps asking why. Solo practice gets you partway here, and our guide to practicing interviews by yourself covers how far that goes and where it stops. The honest limit is that you can rehearse a known answer alone, but you can't easily simulate the follow-up that breaks it, which is exactly the part the long round is built to test.
Build clean answers for the predictable questions. Then spend the larger share of your prep on real reps on hard problems with the conditions moving, because that's the round that decides. In our experience a memorized script carries you through the opening of a long round and then runs out. Reps on unfamiliar problems survive both.
The 30-minute screen has been demoted to a gate. Read the length of your round for what it tells you, then put your hours where the offer actually gets made.
If you want to practice the part that breaks scripts, Four-Leaf's voice mock interview holds a spoken back-and-forth, asks follow-ups grounded in what you actually said, and scores each session so you can see how you hold up when the prepared answer runs out.
