Interviews

How Long Should an Interview Answer Be?

How long should an interview answer be? 30 seconds to four minutes, and about a minute for most stories. What makes an answer feel long, and how to fix it.

Cover for the post: How Long Should an Interview Answer Be?, a large clock-face ring bleeding off the edge with teal speech arcs, and the title set beside it.

How long should an interview answer be? Indeed's career guidance puts it between 30 seconds and four minutes, depending on the question (Indeed). For most questions, aim for about a minute, and rarely go past two. What makes an answer feel long is less the clock than where your point lands inside it.

That range is wide on purpose. A simple factual question deserves a short answer. A behavioral question needs a real story. So memorizing one number will not help you much. What helps is knowing how long each kind of question usually takes, and then making sure the point comes first.

How long an interview answer should be, by type of question

Indeed's range gives you the edges. Inside it, this is the working guide we use, which is our own judgment and not a measured standard:

  • Simple factual questions ("Do you have this certification?" "When could you start?"): the short end. One or two sentences, then stop.
  • Opening questions ("Tell me about yourself," "Walk me through your resume"): about a minute, and a little longer if you have a lot of roles to cover. Our post on walking through your resume shows how to keep it moving.
  • Behavioral questions ("Tell me about a time you..."): about a minute, up to two. This is where most people run long. A good example is meeting a tight deadline, where the decision belongs in the first sentence and the rest is evidence.
  • Opinion and motivation questions ("Why do you want this role?"): about a minute. One reason, said plainly, beats three reasons said quickly.

None of these is a rule. The interviewer's face is the better guide: if they are nodding and writing, you have room. If they glance at their notes or start to interrupt, you have run past what they needed.

Count sentences, not seconds

It is hard to feel the clock while you talk, and a timer in your head makes you rush. Sentences are easier to count. BetterUp's guide to the STAR method (Situation, Task, Action, Result) gives a sentence budget for each part: one or two for the situation, one or two for the task, three or four for the action, and two or three for the result (BetterUp).

Add those up and you get seven to eleven sentences. Said out loud at an easy pace, that is roughly a minute, which is our estimate and not BetterUp's. Notice where the budget goes: more than a third of it is the action, the part that is actually about you. The setup, where most answers grow, gets two to four sentences in all.

The problem usually isn't length. It's order.

Picture two versions of the same answer to "tell me about a time you improved a process." One spends forty-five seconds setting the scene (the team, the tool, the backstory) before finally saying what changed. Another says what changed in the first sentence, then spends the next forty-five seconds on the same details, now offered as support for a point the interviewer already has.

Both answers can be the same length. Only one of them feels long. An interviewer who has heard the point already has somewhere to put the details that follow: they are evidence. An interviewer who is still waiting for the point is doing something closer to guessing where the story is headed, and guessing reads as rambling even when the content is fine.

This is the actual lever: say the point first, then give the supporting reason. Not "here is everything that happened, and therefore here is my point," but the reverse. State the conclusion, then back it up. It costs you nothing in content. It changes everything about how the length feels. If you tend to circle before you arrive, how to stop rambling when you answer goes into the opening, the pauses and the ending in more detail.

A structure that scales to any length

"Point first, then one reason" is not just an opening trick. It holds up whether your answer needs to be twenty seconds or two minutes:

  • The point. One sentence. What do you want them to remember if they remember nothing else?
  • One reason or example. The concrete thing that makes the point credible: a number, a specific moment, a result.
  • Stop. If they want more, they will ask a follow-up question. That is a good outcome, not a sign your first answer was incomplete.

Notice what is missing: a mandate to cover every detail of the situation. The Situation part of STAR is where most answers get long, because it feels safe to over-explain the setup before getting to the part that is actually about you. Keep it to one or two sentences and trust the listener to ask if they need more context.

When a longer answer is fine

Two minutes is not a failure. A longer answer works when three things are true: the question asked for a story, your point came in the first sentence, and every added detail answers a question the interviewer is likely to have. Then the length is depth, and they can follow it.

It stops working the moment you add something only because it happened. The test is simple. For each detail, ask whether the interviewer would miss it if you left it out. If not, cut it. The shorter version is usually the stronger one, and you still have the detail ready if they ask.

The same rule in a meeting

Nothing here is only about interviews. A colleague who asks "where does this stand?" wants the same thing an interviewer wants: the point first, then the reason, then your voice stops. The order in how to give a status update in a meeting is the same order as a good interview answer. Practicing it for one setting helps in the other, because the habit that causes long answers, telling the story in the order you lived it, is the same in both.

A 60-second practice method you can do today

You do not need an app, a partner, or a mirror for this. You need your phone's voice recorder and about five minutes. (Our guide to practicing for an interview alone goes through the full method.)

  1. Pick one real question. Not a random one. Pick one you are actually likely to get: "Tell me about yourself" or "tell me about a time you had to convince someone" both work.
  2. Set a timer for 60 seconds and hit record. Answer out loud, at a normal pace, like you are actually in the room. Do not stop early if you finish sooner. That is useful information too.
  3. Before you listen back, write down what you think your point was, in one sentence, from memory. This is the part people skip, and it is the most useful step: you are checking whether your intended point matches what you actually said.
  4. Now play the recording and note the timestamp where you first said something that sounds like that point. Not implied it. Said it, in words a stranger could repeat back.
  5. Compare the timestamp to your total answer length. If your point landed in the first 15 seconds of a 60-second answer, you are in good shape regardless of the total length. If it landed at second 40, you have found the actual problem, and it is not that the answer was too long. It is that the useful part was too short relative to everything before it.

Do this with three or four different questions in one sitting and a pattern usually shows up fast: many people have one or two openings they default to ("So, I guess I'd say...", "That's a good question, let me think...") that quietly eat the first ten or fifteen seconds before anything answerable begins. Once you can hear that opening, it is easy to cut.

What this looks like measured, not guessed

The exercise above works with a stopwatch and your own judgment about "does this sound like the point." That is genuinely enough to improve on your own. It is also exactly the thing we built the answer line to show automatically: your answer drawn as one line, with the stretch where your point actually landed marked heavier than the rest, so you do not have to guess at the timestamp by ear. Same idea as the exercise above, just measured instead of estimated, and compared against your own Day 1 instead of a fixed target.

Sayforth is an iPhone app, coming soon, built around one question a day, answered out loud. You can see how a day of practice works step by step, including the Say it again button that lets you answer the same question once more in 30 seconds.

Practice with a stopwatch first. If you want it measured for you, that is what we built.

Frequently Asked Questions

How long should an interview answer be?

Between 30 seconds and four minutes, depending on the question, according to Indeed. For most questions, about a minute is a good aim, and two minutes is a sensible ceiling for a story. Put your point in the first sentence so the length never feels like waiting.

Is a two-minute answer too long?

Not if the question asked for a story and your point came first. Two minutes is long when the point arrives late, or when you add details the interviewer did not need. Cut anything they would not miss.

How long should an answer to "tell me about yourself" be?

About a minute is a good aim, as our own estimate, and a little longer if you have many roles to cover. Say who you are and what you do now in the first sentence, then give two or three pieces of evidence, and stop.

How do I know if I am talking too long?

Watch for the interviewer glancing at their notes, shifting, or starting to interrupt. When you practice, record yourself and note when you first said your point. If it was more than a third of the way in, the answer feels long no matter how many seconds it ran.

Launch list

Start the 30-day challenge on launch day.

Practice is free. Coaching is free for 7 days, no card. Founding price: $49.99 a year if you subscribe in the first 90 days after launch.