Answer the question, then stop
By Michael Song · Wharton MBA · ex-Greenhill · investment banking interview coach
5 min read · updated July 26, 2026
Run enough mock interviews and a pattern shows up fast. The most common note is almost never "that was wrong." It is "that was too long."
People over-prepare content and under-prepare length. They walk in with a genuinely good answer, deliver ninety seconds of it, then keep going for another ninety out of nerves. The extra time adds nothing and costs plenty.
The target lengths
These are the numbers to actually rehearse against.
| Question | Target | Notes |
|---|---|---|
| Walk me through your resume | ~2 minutes | A narrative with a direction, not a recital of bullets |
| Why investment banking | 60 to 90 seconds | Two strong reasons, not five weak ones |
| Why our bank | 60 to 90 seconds | Specifics, and what you learned from the people you spoke with |
| A behavioral story | 60 to 90 seconds | With a 2 to 3 minute version ready if they ask for more |
| Walk me through the three statements | 30 to 60 seconds | This one should be a reflex, not a performance |
| A deal you have been following | 60 to 90 seconds | High level. Size, rationale, synergies, risks |
If your answer is running past those by half again, you do not have a knowledge problem. You have a structure problem.
Answer the question, then stop. The single most reliable improvement most candidates can make is to cut the last thirty percent of every answer. Not the first thirty percent, which is where your structure lives. The last thirty, which is almost always restating a point you already made.
Why long answers actively cost you
It is worth being precise about the damage, because "be concise" on its own has never changed anyone's behaviour.
You lose questions. A first round is often thirty minutes. Every extra minute you spend is a question you never get asked, and questions are how you score points. Candidates who ramble through the fit half regularly run out of clock before the technicals, which is the half that decides it.
Length reads as judgment. Knowing what matters and what does not is a real part of the analyst job. An interviewer listening to you take four minutes on a two-minute question is learning something about how you will summarise a diligence call to a VP at 11pm.
You talk yourself into follow-ups. The longer you go past the point, the more surface area you give them. Plenty of candidates have handed over a weak flank in the sentence they added because the silence felt uncomfortable.
Treating brevity as rushing. They are not the same thing, and the fix for one makes the other worse. Rushing is talking fast. Brevity is saying fewer things. Speak at a measured pace, deliberately slower for the first minute or two while the adrenaline settles, but cover less ground. An answer delivered calmly in 75 seconds beats the same content sprinted through in 75 seconds.
Lead with the textbook, then add the colour
There is a reliable ordering trick for any question you might over-answer.
Give the short, correct, almost boring version first. Then add the nuance if there is room. Asked to walk through the statements, name the three in order and give the clean flow before you start volunteering exceptions. Asked why banking, lead with your two reasons before the story that made them true.
This does two things at once. The interviewer gets a complete answer inside the first thirty seconds, so if they cut you off you have still fully answered. And if they want more, they will ask, which means the extra detail arrives as a response to their interest rather than as padding.
The reverse ordering, building slowly to a payoff, is how good answers get marked down. If they stop you at the sixty second mark and the real answer was going to arrive at ninety, you have said nothing.
The two places length runs away from you
Technicals, when you are unsure. Uncertainty makes people add words. If you know the answer, give it and stop. If you do not, say what you do know, say how you would reason toward the rest, and stop there too. Both are better than a slow circle around the topic hoping to land on it.
Stories, always. Behavioral answers are where length gets out of control fastest, because a story has no natural stopping point the way a formula does. A formula ends when the formula ends. A story ends when you decide it does, and under pressure most people do not decide.
That one is not a discipline problem, it is a missing piece of structure, and it has its own fix: STAR is missing a step. Give a story an ending it cannot help but arrive at, and it stops running long on its own.
How to actually fix it
Reading target lengths does nothing. You have to hear yourself go over.
Time yourself out loud, on your phone, once per answer. Not in your head, out loud. Silent reading runs roughly twice as fast as speech, so every estimate you make in your head is wrong by about half. Most people discover their "90 second" answer is a little over two minutes.
Do it once for your resume walk-through, once for why banking, once for why this bank, and once for the three statements. Four recordings, about ten minutes total. Then cut, and record again.
The cut is almost always in the same place: not the beginning, where your structure is, but the stretch near the end where you are re-making a point you already made. Once you have heard that happen in your own voice three or four times, you start hearing it live, in the room, in time to stop.
Frequently asked
- How long should an investment banking interview answer be?
- It depends on the question. The resume walk-through runs about two minutes. Why banking and why this bank run 60 to 90 seconds each. A behavioral story runs 60 to 90 seconds by default, with a two to three minute version ready if they ask for more. A core technical like the three statements should be a 30 to 60 second reflex. Anything materially longer is costing you, not helping you.
- Why do interviewers penalise long answers?
- Three reasons. A first round is usually only 30 minutes, so a rambling answer eats questions you would have scored on. Length reads as poor judgment about what matters, which is a real part of the analyst job. And the longer you talk past the point, the more surface area you give them for a follow-up you cannot defend.
- Is it bad to give a short answer in an interview?
- Far less risky than the opposite. A short, complete, well-structured answer reads as confidence and good judgment, and if the interviewer wants more they will simply ask. The failure mode to worry about is not brevity, it is padding: restating a point you already made because the silence felt uncomfortable.
- Should I talk faster to fit more in?
- No. Brevity and speed are different things and the fix for one makes the other worse. Rushing is talking fast; brevity is saying fewer things. Speak at a measured pace, deliberately slower for the first minute or two while the adrenaline settles, but cover less ground.