How Long Should Interview Answers Be? A Guide by Question Type
How long your interview answers should be, by question type: introductions, STAR stories, technical explanations and system design. Plus how to tell you're rambling and how to cut an answer down.
LiveHint.ai team · · 4 min read
Most interview advice is about what to say. Just as many candidates lose points on how long they take to say it. An answer that runs four minutes loses the interviewer halfway through. One that lasts 20 seconds sounds like you have nothing to say.
Here are practical lengths for each type of question, and how to hit them.
The short version
| Question type | Target length | Roughly |
|---|---|---|
| Quick factual ("Why are you looking?", "When can you start?") | 15–45 seconds | 2–4 sentences |
| "Tell me about yourself" | 60–120 seconds | A short story in three parts |
| Behavioral (STAR) | 90 seconds to 2 minutes | 250–350 words |
| "Why this company?" / "Why this role?" | 45–90 seconds | 2–3 specific reasons |
| Technical concept ("Explain how a hash map works") | 60–90 seconds, then stop | Core idea, then depth if asked |
| Your solution before coding | 30–60 seconds | Approach and complexity |
| System design | 35–45 minutes across the whole round | A conversation, not a speech |
These aren't hard limits. They're the range where most interviewers stay engaged and still have time for follow-ups.
Why shorter usually wins
Interviewers have a fixed amount of time and a list of things to assess. Long answers cause three problems:
- They crowd out other questions. If your first behavioral story takes five minutes, the interviewer may only get to three questions instead of five, and has less evidence to score you on.
- The point gets lost. People remember the start and the end. A long middle buries the result.
- It looks like weak judgment. Knowing what to leave out is a skill interviewers want to see.
Leaving room for follow-ups also helps you. A follow-up question is the interviewer telling you what they care about. A two-minute answer that invites "Why did you choose that?" is better than a five-minute answer that tries to cover everything.
Introductions: 60 to 120 seconds
"Tell me about yourself" sets the tone. Use a present–past–future shape: what you do now, the most relevant highlights before that, and why you're interested in this role. Our guide to tell me about yourself has examples.
Behavioral answers: about two minutes
A STAR story should take around 90 seconds to two minutes. The most common mistake is spending most of that time on the situation. A better split:
- Situation and task: 20–25 seconds.
- Action: about a minute. This is where you're scored.
- Result: 20–30 seconds, with a number if you have one.
If your story needs a minute of background, you've probably picked the wrong story, or you're including detail the interviewer doesn't need. See the STAR method guide for more.
Technical explanations: answer, then offer depth
For "Explain X" questions, give a clear core answer in about a minute, then stop and offer to go deeper: "I can go into how collisions are handled if that's useful." This lets the interviewer steer instead of sitting through detail they didn't ask for.
In a coding round, explaining your approach before writing code should take under a minute: the idea, why it works and its complexity. Then narrate briefly as you code.
System design: a conversation, not a lecture
System design rounds last 45 to 60 minutes, but the same rule applies to each part. Don't talk for ten minutes without checking in. Pause after requirements, after your high-level design and after each deep dive: "Does this make sense, or would you like me to go deeper on storage?" Our system design framework breaks down how to pace the round.
Signs you're rambling
- You've said "and then" more than three times.
- You're explaining context the interviewer didn't ask about.
- You've lost track of the original question.
- The interviewer starts nodding quickly, glancing at the clock, or tries to interrupt.
If you notice it, recover cleanly: "In short, the result was that we cut latency by 40%." Then stop.
How to cut an answer down
- Write it out once, in full. Most people find their first draft runs 500 words or more.
- Cut the background to two sentences.
- Keep one or two actions, the ones that show your judgment most clearly. Drop the rest.
- Lead with the result if it's impressive, then explain how you got there.
- Say it out loud and time it. Reading silently is much faster than speaking, so written drafts always feel shorter than they are.
Practice with a timer
The only reliable way to know how long your answers run is to say them out loud and time them. An AI mock interview keeps time for you and flags rambling and buried results in the feedback, so you can see which stories need trimming. Run the same set of questions twice and compare.
Keep reading
13 min read
STAR Method Examples: 12 Interview Answers That Work
Twelve full STAR method examples for software engineers, from conflict and failure to tight deadlines and production incidents, plus a checklist to adapt them.
- behavioral interview
- STAR method
- interview tips
- software engineering
5 min read
"Tell Me About a Time You Failed": How to Answer, With Examples
How to answer "Tell me about a time you failed" in a software engineering interview: what the interviewer is checking, how to pick the right failure, a STAR structure that ends on learning, and three example answers.
- behavioral interview
- interview tips
- STAR method
- software engineering