The useful question is not “how long can I talk.” It is “when does the next sentence stop earning attention.” Interviewers give you that signal with their eyes, a follow-up, or a glance at the clock. You will not see it if you have never heard your own answer end.
Short answers, and what they are for
“Tell me about yourself,” “why this job,” a weakness, and a culture question are done in 45 to 90 seconds. The shape is present, relevant past, and the reason this conversation exists. One proof is enough. A second proof is usually a repeat with different nouns.
If you finish in thirty seconds, you probably named a title and stopped before the work. Add one decision you made and how you knew it landed. Do not add another employer.
Behavioral answers
Plan on 60 to 120 seconds. Say the situation in one or two sentences. If you are still describing the company at second forty, skip ahead to the day you did something. The result needs a number or a concrete change, and it needs to arrive before the two-minute mark. Past that, people remember the setup and forget the ending.
Coding and design
The spoken part of a coding answer, before you disappear into the editor, is about 90 to 180 seconds: restate, naive solution, the approach you will write, and the cost. System design gets 180 to 420 seconds for the first pass so you can name users, the API, the data, and one bottleneck. Leave the rest for their questions. A monologue that covers the whole diagram leaves them nothing to ask, which feels worse than a gap.
How to practice the length
- Pick the question type so the range is on screen.
- Answer once without watching the clock.
- If you are short, add the result, not more background.
- If you are long, delete the first two sentences and start again.
- Stop when you hit the top of the range, even if you had a nicer ending in mind.
The timer above is set for a behavioral story. Change the type if you are practicing an introduction or a design pass. Random question pulls a prompt from the company hub so you are not always answering the one you wrote for yourself.
FAQ
Is two minutes too long for a behavioral answer?
Two minutes is the top of the usual range, not the goal. If the action and the result need it, stay. If you are still in the situation at ninety seconds, you are long.
How long should “tell me about yourself” be?
Sixty to ninety seconds. Present role, the path that matters for this job, and why you are here. Leave the rest for follow-ups.
Should I talk for the whole system design interview?
No. Use three to seven minutes for a first pass, then let them steer. The timer’s system design range matches that first pass, not a forty-minute round.