Most interview advice tells candidates to prepare more. Very little of it tells them to say less. That gap explains why strong candidates often walk out feeling like they covered everything, then lose the role to someone who said half as much.
Length is not a proxy for depth. When an answer runs four or five minutes, the interviewer stops following your reasoning and starts waiting for the end.
What Actually Happens When You Run Long
Interviewers take notes. Most are filling out a scorecard with a handful of competencies and limited space under each one.
If your best point is buried inside six minutes of setup, someone has to do the extraction work for you. Most will not. They write down whatever they can summarize quickly, and that summary becomes your evaluation.
There is a pacing cost too. A 45-minute conversation has room for maybe six to eight substantive questions. Spend nine minutes on the first two and you have quietly removed your own chances to show range.
The 90-Second Benchmark
For most behavioral and experience questions, aim for 90 seconds to two minutes. Technical deep dives and system design problems earn more; "tell me about a project you are proud of" does not.
Ninety seconds is longer than it feels. Read a paragraph out loud and you will use roughly 20 seconds. Five or six tight paragraphs is a complete answer.
The goal is not to rush. It is to arrive somewhere before attention starts drifting.
Lead With the Answer, Not the Setup
The biggest cause of bloated answers is chronological storytelling. Candidates start at the beginning: how they joined the team, who reported to whom, what the quarterly goals were, and then, eventually, the thing they actually did.
Flip it. Open with the outcome or the decision, then add just enough context to make it land.
Compare two openings for "tell me about a time you handled conflict on a team."
The long version: "So I joined this team in 2023, and at that point we had about eight engineers plus two designers, and there was a reorg happening, and my manager at the time..."
The tight version: "I had to resolve a disagreement between our design lead and a backend engineer over API ownership. I ran a 30-minute working session and we had a decision within a day. Here is how it went."
The second one hands the interviewer a headline they can write down immediately. Everything after that reads as supporting evidence rather than a search for the point.
Four Things Worth Cutting
Some material shows up in nearly every overlong answer and almost never earns its space.
Org chart detail. Nobody needs your skip-level manager's title. Say "a cross-functional team of six" and keep moving.
Timeline padding. "This was around Q2, or maybe early Q3" costs you seconds and adds nothing to the substance.
Preambles. "That is a great question, let me think about how to frame this" is dead air. A two-second pause reads as thoughtful. A verbal warm-up reads as filler.
Hedging. "I mean, it was not entirely my project, but I did contribute somewhat" hurts you twice: it weakens the claim and stretches the sentence. Name what you owned, credit who else was involved, and stop.
Build One Reusable Skeleton
You do not need a script for every possible question. You need a shape you can pour any story into.
Try this one: the situation in a single sentence, your specific actions in two or three, the result in one, and what you would change in one. That is six sentences, which lands close to 90 seconds at a natural speaking pace.
Write four or five of your strongest stories into that shape. Do not memorize them word for word; scripted answers sound flat and fall apart under follow-up questions. Memorize the beats instead.
Practice Out Loud, With a Timer
Reviewing answers silently will not fix this. The gap between what you plan to say and what comes out of your mouth only shows up when you speak.
Record yourself answering five questions. Play it back with a stopwatch and mark the exact second where you first fully answered the question. If that moment lands at 2:40 and you kept going until 4:15, those last 95 seconds were working against you.
This is where repeated practice reps help most. A transcript makes your filler patterns obvious in a way that replaying the conversation from memory never does.
Hand the Interviewer the Steering Wheel
A short answer is not an incomplete one. It is an answer with an explicit offer attached.
Close with a check-in: "That is the short version. Happy to go deeper on the technical trade-offs if that is useful." Now the interviewer steers the follow-up toward whatever they still need to assess.
This does two jobs at once. It keeps you concise, and it shows you can read a room and adjust, which is itself a point in your favor.
When Longer Is the Right Call
Concision is a default, not a rule. Some questions genuinely need more room.
If you are asked to walk through a system design, a debugging process, or a complicated analysis, the reasoning is the answer, and compressing it hides the exact thing being evaluated. If an interviewer asks a direct follow-up, they have invited detail; give it to them.
The distinction is simple. Length should be a response to the question, not a habit you bring to every question.
A Drill for This Weekend
Pick the three questions you are most likely to face. Answer each one twice on video: once with no constraint, once capped at 90 seconds.
Watch both versions back. In almost every case the capped one is the answer you wish you had given, and the act of deciding what survives the cut is what makes you sharper when it counts.