How do you answer "why investment banking?" convincingly?

What Is Actually Being Scored

Excitement: Convey genuine passion. Your answer should sound like banking is where you want to build, not a steppingstone to somewhere else.

Intrigue: Say something specific to you. Avoid "fast-paced environment" and "steep learning curve." Both are true of the job and useless in an answer, because they are equally true of every other answer being given that day.

Understanding: Prove you know what the job actually entails. Not what it pays or where it leads — what a junior banker does on an ordinary Tuesday. If your answer implies the job is mostly deal strategy, you have told the interviewer you have not looked closely. Read Bankers Are Butlers before you write the Reason slot.

The Cliches

You hear these a lot. Any of them can work, but you have to justify them.

"It's fast-paced with a steep learning curve." It describes the job, not you.

"I want to work on impactful deals." There is a lot of high impact stuff. You could work at a weapons plant.

Better to focus on the things that are not removable from banking, like deals or client service at that level. That is stronger than saying you want to work on high impact stuff.

Where Evidence Comes From

Evidence is the only slot you cannot write the night before. It has to already exist.

Source it from specific people, books, experiences, or credible material. Three that work:

• "I read about CVS buying Oak Street Health and realized the interesting part was not the price, it was why a pharmacy chain wanted primary care."
• "I remember reading about the Scale AI deal in the news and thinking—that's the kind of work I want to do."
• "I read Moyer and took a class in debt, and it changed which part of the balance sheet I look at first."

If you do not have evidence yet, build it deliberately. Pick the part of the job you are most curious about and read into it until you can describe the mechanics rather than the outcome — M&A is the usual starting point. Then make one thing you can talk about for ten minutes: a model, a coverage note, a cluster of one company plus its deals plus the trend behind them. Then have the conversation, because a coffee chat is how reading becomes a named source. Evidence takes weeks to build and one sentence to deploy.

The Trap Your Own Answer Sets

Assume every specific noun in your answer is a question you have just invited.

Say M&A, and you should be able to describe what a sell-side process involves. Say restructuring, and you should be able to explain why creditors and shareholders want different things. Say you want to learn the craft of client service, and you should have read enough to know that the craft is mostly detail — the reprinted page, the wrong shade of blue, the bullet workshopped a fourth time.

This is the failure that costs the most, because it happens late — specific enough to be interesting, thin enough to collapse on the follow-up. Under-claim rather than over-claim. One true specific thing beats three you half know.

Once this one holds, the next two get harder, not easier: why this firm and why this group both need evidence you cannot get from reading. Then take all three into a mock interview and say them out loud, because an answer you have only written is an answer you have not tested.