How Long Should Interview Answers Be? Timed by Question Type

10 min read

Published August 20, 2026

Exact interview answer lengths by question type — seconds, words, and sentences at 125–150 wpm — plus the STAR time budget and how to tell you're running long.

Most interview answers should run 30 to 90 seconds. Behavioral answers — "tell me about a time…" questions — earn 90 seconds to 2.5 minutes, and no interview answer should pass 3 minutes uninterrupted. At a conversational pace of 125 to 150 words per minute, that is roughly 60 to 225 spoken words: one short paragraph out loud. Inside a behavioral answer, budget about 20 percent situation, 10 percent task, 50 percent action, and 20 percent result.

Those are the numbers. The rest of this guide converts them into the units you actually rehearse in — words and sentences, not seconds — budgets the inside of a STAR answer, gives you four ways to tell you are running long while you are still talking, and covers the honest counter-case where longer answers really do score better.

How long should interview answers be, by question type?

The most useful version of the answer is a single conversion table — the Seconds-to-Sentences Table — because nobody rehearses in seconds. You write and practice in words and sentences, so here is every common question type converted at a conversational 125 to 150 words per minute. That rate is measured, not folklore: speaking-rate data compiled by VirtualSpeech puts conversational English at 120 to 150 words per minute, with the National Center for Voice and Speech placing average US conversation at about 150.

Two numbers to memorize if you remember nothing else: 90 seconds, the point where an uninterrupted monologue starts costing you the room, and 3 minutes, the hard ceiling for even your most complex story.

For context on where these ranges sit: Indeed's guidance (updated June 15, 2026) spans 30 seconds to 4 minutes overall with behavioral answers at 2 to 4 minutes — a range so wide it barely constrains anything. Communication trainer Chris Fenning (January 2022) refuses fixed numbers but sets the same ceiling: no answer should exceed about 3 minutes. The table above is deliberately tighter than Indeed and more concrete than Fenning, because "it depends" is not something you can rehearse against.

One clock does not count against any of these budgets: the pause before you start talking. Indeed's same guidance allows up to about 10 seconds of thinking time before answering, and a deliberate pause reads as composure, not blankness. If you need longer, name it — "let me think about that for a moment" — because a paced answer after a pause beats an instant answer that rambles.

Why do shorter interview answers win?

Interviewers grade signal per minute, not completeness — a 45-minute interview at 90 seconds per answer gives them 15 or more data points on you, while 4-minute answers give them 7 or 8 and train them to stop asking follow-ups. Four mechanisms drive this:

1. Interview shrinkage math. A 45-minute interview has maybe 30 to 35 minutes of actual question time. Fenning's version of this argument: at 10 minutes per answer, an hour-long interview covers only about 6 questions. Every minute you add to an answer is a question — a chance to show range — that never gets asked.
2. Concision is itself the test. For most roles, "can this person organize their thoughts and communicate them efficiently" is a hiring criterion. A tight 75-second answer is evidence of that skill, independent of its content.
3. Monologue kills dialogue. The best interviews turn into conversations. A 4-minute answer teaches the interviewer to stop asking follow-up questions — which are exactly where you would get to show depth on your terms.
4. Attention decays in a monologue. Directionally true and worth respecting — but the famous version of this claim deserves scrutiny, so it gets its own section.

Is it true interviewers stop listening after 90 seconds?

The widely repeated claim that interviewer attention wanders at 60 seconds and collapses at 90 circulates across Monster, LinkedIn, and staffing-agency blogs with no primary source anywhere in the chain — treat the exact numbers as folklore. We looked for the original study behind it while researching this page and could not find one; neither, apparently, can anyone who cites it, because it is always stated bare.

This matters for more than pedantry. If you treat 90 seconds as a lab-verified cliff, you will panic-compress good answers. If you treat it as what it is — a reasonable practitioner heuristic for when a one-sided answer starts feeling long — you can use it calmly: aim under it by default, pass it deliberately when the story earns it.

How long should each part of a STAR answer be?

For a 2-minute behavioral answer, use the 20/10/50/20 STAR Budget: about 25 seconds of Situation, 10 seconds of Task, 60 seconds of Action, and 25 seconds of Result — and if your Situation runs longer than your Action, the answer is upside down.

• Situation — about 20 percent (25 seconds). One or two sentences of context. The interviewer needs "our Q3 launch was slipping and two teams blamed each other," not the org chart.
• Task — about 10 percent (10 seconds). One sentence: what you specifically were responsible for.
• Action — about 50 percent (60 seconds). The part they are actually evaluating. Specific decisions, first person singular.
• Result — about 20 percent (25 seconds). The outcome, with a number if you honestly have one, plus one sentence of what you learned or changed.

The budget exists because Action starves in the wild. Backstory feels safe to deliver — it is memory, not judgment — while describing your actions requires retrieval under pressure. So under stress, people pad the safe part. As the highest-scoring rambling-advice post we found on r/interviews — a 210-upvote post — puts it: "When your brain scrambles, your mouth rambles."

Here is the budget applied, timed at roughly 1:50. This is an illustrative example written for this guide, not a transcript of a real candidate:

"Last year our biggest client threatened to leave after a botched migration (0:00–0:15 — Situation). As the account lead, I owned the save (0:15–0:25 — Task). I got their CTO on a call within 24 hours and brought our own engineer with me instead of going alone, so questions got answered live instead of ping-ponging over email. We rebuilt the migration plan together on that call, and I set up a weekly written status update, because the root complaint was silence, not the bug itself (0:25–1:25 — Action). They renewed at a higher tier three months later, and the written-update format became standard for all our enterprise accounts (1:25–1:50 — Result)."

Now the same story the way it usually comes out — a 3:40 version, annotated with where the time leaks (also illustrative):

"So, a bit of background first: I joined the account team in 2023, and this client had actually been with us since before I started, they were our biggest logo, and the relationship had always been a little rocky because of some things that happened before my time… (45 seconds gone and nothing has happened yet — Situation bloat) …anyway, the migration went badly and they were upset. I basically got everyone on calls and we sorted it out over a few weeks. (the entire Action, the part being graded, compressed into one vague sentence) Another example of this kind of thing was a different client the next quarter where… (the second example — a new story starting inside the first one) …so yeah, communication is really important. (a theme, not a result, and the answer fades out instead of landing)"

Same candidate, same story, wildly different score. The difference is not talent — it is a budget.

How do you tell you're running long — while you're still talking?

You will not have a timer in the room, so use the Land-the-Plane Checklist — four in-the-moment proxies, named for the way people actually describe the problem ("I have trouble landing the plane in responses to questions. How do I stop yammering incessantly?" — verbatim from r/interviews):

1. The breath test. If you have not paused long enough for the interviewer to speak in the last three or four sentences, you are monologuing. Recovery: finish the sentence, then actually stop.
2. The second-example tell. The moment you hear yourself say "another example of that is…" — stop. One example per question. They will ask if they want more.
3. The body read. Note-taking stops, eyes drop to the next question, a small inhale like they are about to speak. Any of these: land the sentence you are on and close.
4. The backstory alarm. Thirty seconds in and still setting context? Skip straight to the action: "…long story short, the launch was at risk and I stepped in to rebuild the plan with their CTO."

Each tell pairs with a recovery move because the goal is not to freeze when you catch yourself — it is to exit gracefully mid-answer, which is a learnable maneuver, not a personality trait. If rambling is your core problem rather than an occasional slip, the guide to stopping rambling in interviews treats it in full — this section is the in-the-room version.

How should you end an interview answer?

Rambling is usually caused by not having planned the last sentence — so decide your closer before you start talking, and make it a check-in that hands the conversation back. Fenning's scripted version, which he built his whole argument around: "Would you like me to expand on any part of that?"

Closers you can take verbatim:

• "…so we shipped two weeks early and the client renewed. Happy to go deeper on any part of that."
• "…that's the short version — want me to expand on how we handled the pushback?"
• "…and that experience is most of why I'm sitting here. Does that answer what you were after?"

The check-in does three jobs at once: it ends the answer decisively instead of letting it fade out, it returns control to the interviewer, and it converts a monologue into a conversation. One warning: use it after complex answers, not after every question — deployed constantly, it becomes a tic and starts reading as approval-seeking.

When are longer interview answers actually right?

Honest caveat: in rubric-graded loops — Amazon-style behavioral interviews are the classic case — an ultra-compressed 60-second story can leave rubric boxes unchecked, and as of August 2026, Blind forum threads on STAR length genuinely split between "2 to 3 minutes, tight" and "4 to 5 minutes so nothing is missed." That second camp is not wrong about the mechanism: when an interviewer must document evidence against specific criteria, signal they never heard is signal you never get credit for.

Resolve the trade-off with one rule: Compress by Default, Expand on Invitation. Give the 2-minute version, end with a check-in, and let their follow-up questions pull out the depth. Follow-ups are not a sign your answer failed — they are the interview working. The interviewer asking "what happened with the second team?" is now steering you directly toward the rubric box they need filled, which beats you guessing at it for five minutes.

Only three situations justify going long uninvited: a technical walkthrough you were explicitly asked to give, an interviewer who says "take your time with this one," and case interviews where reasoning aloud is the answer being graded.

Should your answers be shorter on video calls?

On video calls, target roughly 15 to 20 percent shorter than your in-person lengths — silence reads as longer on a call, interruptions are clumsier, and the interviewer has fewer polite ways to signal "wrap up." This figure is a practitioner rule of thumb, not a measured statistic; the calibration logic is what matters. Pause deliberately at the end of answers to make room for follow-ups, because the natural conversational overlap that ends an in-person answer does not happen over Zoom. A 2-minute behavioral answer in a conference room is a 1:40 answer on a video call.

How do you calibrate your answer length before the real interview?

You cannot judge your own answer length while answering — everyone underestimates — so calibration has to happen in rehearsal, against a clock and ideally against a score. The protocol works fully solo — the practice-by-yourself guide covers the complete rep method if you want the long version:

1. Record yourself answering your five most likely questions out loud. A phone voice memo works.
2. Measure the raw time against the Seconds-to-Sentences Table above. Expect a gap like the one between the two versions of the client-save story earlier on this page: the same answer that feels like the 1:50 budgeted version from the inside can play back like the 3:40 rambling one.
3. Diagnose where the time went. It is almost always one of two leaks: Situation bloat or a second example.
4. Re-record until behavioral answers land at 2:00 plus or minus 20 seconds — by cutting words, not by talking faster. Rushed delivery at 180 words per minute reads as nerves, not efficiency.

This matches what frustrated candidates report about prep that does not transfer — as one r/recruitinghell poster put it, "no matter how many hours I … drill interview question banks … the second I log [on it falls apart]" (bracketed words reconstructed from a partially captured post). Reading about answer length changes nothing; measured reps change the habit.

Full disclosure before the next sentence: Interview Drills is our product. It exists because step 2 and step 3 are exactly what people skip when practicing alone — timing yourself feels awkward and self-diagnosis is unreliable. Interview Drills is an AI-powered interview training platform designed for people who have a real interview coming up: it diagnoses interview weaknesses with a free 3-minute quiz, prescribes a 14-day training track of practice drills, scores spoken answers on six dimensions in under 60 seconds, and personalizes scoring and feedback to the candidate's resume and target job. Two of those outputs do this page's job for you: Conciseness is one of the six scored dimensions (alongside Clarity, Confidence, Structure, Audience Awareness, and Delivery), and every voice drill reports your actual words per minute, filler words, and pauses — so "am I running long?" gets a measured answer instead of a guess. It covers behavioral, situational, strengths, weaknesses, and salary questions; it does not cover coding or technical interviews, and it is a training tool, not a live-interview assistant.

One rep tells you where you are. Three or four reps of the same answer against the table is what actually moves a 3:40 rambler to a 1:50 answer that lands the plane.

Practice this drill

What Are Your Weaknesses: 15 Answers + Free Scored Drill

Aim for ~45s worth of answer. Record with your voice for full metrics, or type it out to score on content alone.

Record my answerWrite my answer

Frequently asked questions

How long should a "tell me about yourself" answer be?

60 to 90 seconds: your present role, one or two proof points relevant to this specific job, and why you are in this room. At a conversational pace that is roughly 125 to 225 words. It is an opening, not an autobiography — if it passes 90 seconds, you are narrating your resume instead of framing it.

How long should a STAR answer be?

90 seconds to 2.5 minutes, with roughly half of that time spent on the Action step. A useful internal check: if the situation setup takes longer than the actions you took, rebalance the answer before worrying about total length.

Is a 30-second interview answer too short?

Not for factual, motivation, or salary questions — those should be 30 seconds or less. For behavioral questions a 30-second answer usually means the Action detail got skipped. If you are naturally brief, end with "happy to go deeper on any part of that" so the interviewer can pull for more instead of marking the answer thin.

How many words is a 90-second answer?

About 190 to 225 words at a conversational speaking pace of 125 to 150 words per minute — roughly two short spoken paragraphs. Most people are surprised how few words that is, which is why written scripts almost always run long when spoken aloud.

How long is too long for an interview answer?

Past 3 minutes without an interruption or a check-in, you are losing the room regardless of how good the content is. Even complex behavioral stories should land by 2.5 minutes; anything longer belongs in a technical walkthrough the interviewer explicitly asked for, broken up with check-ins.

How do I stop rambling in interviews?

Plan your last sentence before you start talking, cap yourself at one example per question, and rehearse against a clock with recordings — rambling is a calibration failure, not a knowledge failure, and calibration is trainable. Nobody can judge their own answer length while talking, so the fix is measured practice, not willpower.

Should every interview answer use the STAR method?

No. STAR is for behavioral questions — "tell me about a time…" Forcing Situation-Task-Action-Result onto "Why do you want to work here?" turns a 45-second answer into a three-minute one. Match the structure to the question type, and match the length to the structure.

How long should you pause before answering an interview question?

Up to about 10 seconds of thinking time is acceptable — that is Indeed's guidance as of June 2026 — and the pause does not count against your answer length. A deliberate pause reads as composure, not blankness, and if you need longer you can name it: "let me think about that for a moment." A paced answer after a pause beats an instant answer that rambles.