--- title: How Long Is a Technical Interview? Round-by-Round (2026) description: How long a technical interview lasts — phone screens, coding rounds, system design, HR — plus full-process timelines and what a short interview really means. url: https://usegreenroom.app/blog/how-long-is-a-technical-interview last_updated: 2026-07-12 --- ← Back to blog Interview Prep # How long is a technical interview? July 12, 2026 · 7 min read ![How long is a technical interview — round-by-round timeline from Greenroom, the AI mock interviewer](/assets/blog/how-long-is-a-technical-interview-hero.webp) Your calendar says 60 minutes. At minute 38, the interviewer says "that's all from me — any questions?" and you spend the next four hours in the group chat asking whether a 38-minute interview means rejection. Or the opposite: minute 71, third follow-up question, laptop fan screaming, and you're wondering if it's rude to mention you have another interview in nine minutes. So, **how long is a technical interview?** The short answer: **most single technical rounds run 45–60 minutes**, phone screens run shorter, machine coding and onsites run longer, and the full process from application to offer typically takes two to six weeks. Here's the round-by-round breakdown — and the honest read on what a short or long interview actually signals. ## How long is a technical interview, round by round? - **Recruiter screen: 15–30 minutes.** Logistics, salary range, notice period. Not technical, still eliminatory. - **Technical phone screen: 30–45 minutes.** One coding problem or rapid-fire fundamentals. Our [telephonic interview guide](/blog/telephonic-interview-tips) covers the format. - **Coding / DSA round: 45–60 minutes.** Usually 5 minutes of intro, 40 of problem-solving, 10 for your questions. Two problems means roughly 20 minutes each — budget accordingly. - **Machine coding round: 90–120 minutes**, plus a separate review discussion — the long-form Indian product-company staple (full guide: [machine coding round](/blog/machine-coding-round)). - **System design: 45–60 minutes.** Senior rounds sometimes stretch to 75. - **Behavioral / hiring manager: 30–45 minutes.** - **HR round: 15–30 minutes.** - **Campus TR at mass drives: 15–30 minutes.** Service-company technical rounds in India can be brutally short — 15 minutes, three questions, next candidate. Short ≠ failed; it's throughput. ![How long each technical interview round runs — phone screen to HR, typical durations](/assets/blog/how-long-is-a-technical-interview-diagram.webp) *Typical durations by round — budget your energy for the loop, not just the slot.* ## How long does the whole interview process take? End to end, application to offer: **startups** move in one to two weeks (sometimes days if they're bleeding for the hire). **Mid-size product companies** take two to four weeks across three to five rounds. **FAANG-scale loops** take four to eight weeks — phone screen, four-to-five-round onsite, then a hiring committee or debrief that adds a week or two of silence that means nothing about your result. **Campus drives in India** compress everything into a single day: OA in the morning, TR after lunch, HR by evening, results at midnight. ## Is a short interview a bad sign? The question everyone actually googles from the parking lot. Honest answer: **sometimes, and you can usually tell from what happened, not the clock**. Bad-sign short: the interviewer stopped probing after your first answers, skipped the "any questions for me" ritual, or ended a scheduled hour at minute 25 without warmth. Good-sign short: you answered cleanly, they ran out of prepared questions, and they spent the last ten minutes selling you the team — interviewers don't sell to rejects. Also common and meaningless: the interviewer was double-booked and had 40 minutes all along. One data point, wide error bars. ## Why interviews run over Running long is usually good news — follow-up questions mean engagement, and "do you have ten more minutes?" almost always means the interviewer is building a case to hire you. The exception: a struggling round where the interviewer keeps offering hints past the hour is them fighting to find a reason to pass you. Either way, never look at the clock like you have somewhere better to be — and if you genuinely do, say so at a question boundary, not mid-answer. ## Budget your energy, not just your time Here's what the duration tables miss: a 60-minute technical interview is a 60-minute *spoken performance*, and most candidates have never once practised talking through problems for a full hour. Reading Glassdoor timelines tells you how long you'll sit in the chair; it does nothing for minute 50, when your explanations get sloppy because your brain is out of fuel. I learned that one the hard way — my prep survived every 25-minute practice session and died in real 60-minute rounds. It's why [Greenroom](/) mocks with Ari run like real full-length rounds with follow-up questions, so the endurance isn't a surprise. How much total prep time you need before the loop is its own question — we've covered it in [how long to prepare for coding interviews](/blog/how-long-to-prepare-for-coding-interviews) — and don't forget to keep five minutes of energy for [your questions at the end](/blog/questions-to-ask-at-end-of-interview-software-engineer); ending flat is how good interviews land as average. > **The core truth:** the clock is the least informative part of your interview. What the interviewer did with the time — probed deeper, sold the team, or checked out — tells you everything the duration can't. ## Frequently asked questions ### How long is a technical interview? Most single technical interview rounds run 45–60 minutes: about 5 minutes of introductions, 40 minutes of problem-solving or technical discussion, and 10 minutes for your questions. Phone screens run 30–45 minutes, machine coding rounds run 90–120 minutes, and campus technical rounds at mass drives can be as short as 15–30 minutes. ### How long is a technical phone screen? Typically 30–45 minutes — one coding problem in a shared editor or rapid-fire fundamentals, plus a few minutes of introductions and questions. Recruiter screens (non-technical) are shorter, usually 15–30 minutes covering logistics, salary range and notice period. ### How long do coding interviews last? Standard coding/DSA rounds last 45–60 minutes. If the interviewer plans two problems, budget roughly 20 minutes per problem plus discussion. Machine coding rounds are the exception at 90 minutes to 2 hours of solo building, followed by a separate design-review discussion. ### Is a short interview a bad sign? Not by itself. It's a bad sign when paired with other signals: no follow-up questions, no 'any questions for me', no attempt to sell you the team. It's a neutral or good sign when you answered cleanly and the interviewer finished early or spent the remaining time pitching the company — interviewers don't sell the role to candidates they've rejected. Scheduling constraints also cut interviews short for reasons unrelated to you. ### How long does the full interview process take? From application to offer: startups typically take one to two weeks, mid-size product companies two to four weeks across three to five rounds, and FAANG-scale companies four to eight weeks including a hiring committee stage. Indian campus placements compress the whole process — OA, technical and HR rounds — into a single day. ### How long is a system design interview? Usually 45–60 minutes, occasionally 75 for senior roles: a few minutes of requirement clarification, 35–45 minutes of design discussion at a whiteboard or shared doc, and time for trade-off questions at the end. The time pressure is real — practicing the full hour out loud matters as much as knowing the patterns. A 60-minute interview is a 60-minute spoken performance — train the endurance, not just the answers. Greenroom runs full-length voice mock interviews with follow-ups and honest feedback. Free to start. Planning your prep timeline? Read how long to prepare for coding interviews.