How long should interview answers be?
Most interview answers should run between 30 seconds and 3 minutes, depending on the question. Story questions that start with “tell me about a time” sit at the long end, about two to three minutes. Quick factual questions sit at the short end. Anything past three minutes usually needs an invitation from the interviewer.
The two-to-three-minute figure comes from Amazon, which runs a lot of story-based interviews. Its interview guide tells candidates to practise STAR answers that are concise yet detailed, typically lasting two to three minutes each. Other employers rarely publish a number, so treat Amazon's as a sensible upper limit for a story.
The rest of this page breaks that range down by question type, converts it into words, and shows how it fits into a whole interview. If you already know an answer ran long, the page on shortening an answer that drifted covers the rewrite itself.
How many words is a two-minute answer?
A two-minute answer is roughly 330 to 390 spoken words at normal conversational pace. Researchers measured speaking rates in about 2,400 recorded phone conversations and found averages between 164 and 196 words per minute, depending on how the time was measured. Interview speech may be slower than a phone chat, so treat these as rough figures.
The study, by Yuan, Liberman and Cieri of the University of Pennsylvania, was presented at Interspeech 2006. Its overall average was 196 words per minute, with individual conversations ranging from 111 to 291. Counting each speaker's turns separately gave 164 words per minute.
That gives you a practical check. Write your answer out, count the words, and divide by about 180. A 600-word story is a three-minute answer at best, and likely longer once you slow down for the parts that matter. Most first drafts of a story are too long for this reason.
How long should each type of answer be?
Each type of question has its own natural length, and matching it matters more than any single rule. The table gives a target for the common types, with the reason for each. The targets for story questions follow Amazon's guidance, and the others are working guides you can adjust to the interviewer's pace.
| Question type | Example | Target length | Why |
|---|---|---|---|
| Factual or yes/no | “What's your notice period?” | Under 30 seconds | They need a fact to plan with |
| Salary expectations | “What are you looking for?” | One or two sentences | A long answer sounds unsure |
| Tell me about yourself | “Walk me through your background” | 60 to 90 seconds | It's an opener, and it sets the tone for the rest |
| Why this role or company | “Why do you want to work here?” | About 1 minute | Two or three specific reasons are enough |
| Situational | “What would you do if...?” | 1 to 2 minutes | A plan and a reason, with less backstory |
| Behavioral story | “Tell me about a time...” | 2 to 3 minutes | Room for what you did, the result and the evidence |
| Technical walk-through | “How would you design...?” | As needed, checking in every 2 minutes | The interviewer may want to steer |
| Your questions for them | “Any questions for us?” | One sentence per question | Leave them time to answer |
For the opener, the tell me about yourself guide shows a structure that fits in 90 seconds. For pay, the salary expectations question has short scripts you can copy.
How does answer length fit into a whole interview?
Answer length decides how many questions you get through, and the number of questions shapes your score. Amazon says its phone screens are 30 to 45 minutes and its loop interviews last 45 to 60 minutes each. In a 45-minute slot, two four-minute answers already use a fifth of the time.
Here is an example budget for a 45-minute interview. Allow about 5 minutes for introductions and 10 minutes at the end for your questions. That leaves about 30 minutes for theirs. At three minutes per answer plus a minute or two of follow-ups each, that's six or seven questions.
Run long, and the interviewer gets through four, which matters when the interview is scored. Google's structured interviewing guide describes asking every candidate the same questions with set follow-ups and scoring each answer on a rubric. A question you never reached gets no score. The Amazon timings come from its page on what candidates should know.
How can you tell an answer is running long while you give it?
You can tell an answer is running long when you're still on the background after about 30 seconds, or when you notice yourself saying “and then” to start a new part. Both mean the story is spending its time on setup. The fix in the moment is to jump to what you did.
Watch the interviewer too. Shorter nods, eyes going to the clock or the notes, and a hand moving toward the keyboard are common cues, though none is certain on its own. The guide on what to do when the interviewer went quiet covers the silent version, and how to tell you lost the room lists the moments that mark a turning point.
A line you can use mid-answer, as an example: “I'll skip ahead to what I did, since that's the part that matters here.” It sounds deliberate, and it gives you a clean way back to the action.
Can an interview answer be too short?
Yes. A story answer under about 30 seconds usually leaves out the result or your own part in it, and those are what scorers look for. The US Office of Personnel Management says highly structured interviews are scored against benchmarks of proficiency. A short answer often misses the benchmark for lack of evidence.
The OPM structured interview page also notes that every candidate gets the same lead and probe questions. A short answer usually draws a probe, which is fine if you can fill the gap. If you can't, the answer stays short on the scorecard too.
Pausing before you answer is different, and it's fine. In ordinary conversation, replies start very fast: a 2009 study in PNAS found an average gap of about 208 milliseconds across 10 languages. So a three-second silence feels long to both people. Say “Let me think about that for a second” and the pause reads as care.
How do you practise the right length?
Time yourself out loud, because written answers always feel shorter than spoken ones. Record each story on your phone with a timer running, then note where the two-minute mark lands. If it lands before you've reached what you did, cut the background until it doesn't.
Use this routine for each of your main stories:
- Say the story once without stopping, and note the total time.
- Note the time when you first say what you did. Aim for under 40 seconds.
- Note the time when you say the result. It should come before the end, with a number if you have one.
- Cut one sentence of setup and run it again.
After a real interview, mark which answers ran long in the free debrief template, so you know which ones to retime. The STAR method guide shows how to split a story into parts that each have a time.
Prept's Mock room is built for this kind of practice: you answer out loud on a clock and get a score out of 10, checked against your resume. It's in the free plan.