Investment Banking Associate Interview Questions

Prepare for an investment banking associate interview by explaining both the work you can do and how you help others deliver reliable work. Your examples should distinguish your analysis, your review decisions and the responsibilities held by other people. Technical fluency matters most when you can connect it to a decision.

The questions below are original preparation prompts. They are not a firm's question list or a universal hiring standard. Match your preparation to the vacancy and your own route, whether that involves an MBA programme, a lateral application or another background.

TL;DR

• Make your contribution clear in every experience example.
• Explain how you review assumptions, not just spreadsheet outputs.
• Show how you communicate conflicts before deadlines fail.
• Connect technical analysis to the client's decision.
• Use real experience without disclosing confidential information.

What changes when you prepare at associate level?

Use ownership as a preparation lens. Instead of stopping at “I built the analysis,” explain how the task was scoped, how the result was checked and how it reached the decision-maker. This is our coaching framework; actual responsibilities depend on the role.

Morgan Stanley's interview guidance says discussions depend on the role and can involve technical skills and past experiences. It encourages candidates to know their resume and explain relevant examples. That supports role-specific preparation, not a fixed associate interview format. Morgan Stanley interview preparation.

The career-path guide covers the broader role ladder. This page focuses on evidence you can use in an interview.

How should you walk through your resume or a deal?

Start with the purpose of the work. Then describe your responsibility, one difficult decision, the outcome and what you learned. Separate “the team advised” from “I analysed.” If you reviewed a model built by another person, explain the review rather than taking credit for building it.

Use public or appropriately anonymised information. Do not disclose private client details to make an answer sound credible. You can explain the type of problem, your reasoning and the checks you performed without sharing confidential figures.

If you have not worked on a transaction, use the closest genuine example and state its limit. An MBA project can demonstrate reasoning and teamwork; it should not be presented as a client mandate. The deal-discussion guide develops a clear structure for discussing transactions.

How do you answer a model-review question?

Original prompt: An analyst sends a valuation just before a review meeting. The conclusion differs sharply from the previous version. What do you do?

Begin by identifying what changed. Compare the assumptions, methodology and outputs before treating the new result as an error. A revised forecast may explain it; an inconsistent denominator may not. Prioritise the parts that could alter the recommendation.

Then explain the operational response. Work with the analyst to trace the issue, tell the work owner what is known and agree what can be delivered reliably. A deadline does not make an unexplained output defensible.

After resolving the immediate issue, identify the check that should have caught it. “Be more careful” gives the analyst little to use. A comparison of changed assumptions and resulting valuation ranges is a more concrete review step.

Practice inside this guide

Associate interview practice

Question 1 of 3

An analyst sends you a model with a material error near a deadline. What do you do?

Your answer

Reveal model structure

These three local prompts cover a model error, a client objection and several workstreams. They reveal authored structures for self-review. They do not simulate managing a live team or measure an employer's assessment of you.

How do you demonstrate technical fluency?

Explain the economic meaning before the calculation. For valuation, ask whether the earnings measure belongs to the whole enterprise or only equity holders. For a transaction model, explain how financing and operating assumptions affect the result.

Original example: Enterprise value is 600 million and EBITDA is 50 million, so EV/EBITDA is 12.0x. If an update changes EBITDA to 60 million while enterprise value remains 600 million, the multiple becomes 10.0x. That change is arithmetic, not proof that the business has become cheaper in the market.

A useful follow-up asks why EBITDA changed and whether the periods and adjustments remain comparable. An associate-style review answer connects the numerical change to the conclusion someone might draw from it.

Use the technical interview questions for topic coverage. Practise explaining how a changed assumption alters the recommendation, not only reciting a formula.

How do you answer leadership questions without exaggerating?

Choose a moment when your actions helped someone else do better work. Explain the problem, the feedback you gave and what happened next. If you did not formally manage the person, say so.

For example, you may have helped a project teammate replace an unclear analysis with a checkable sequence. The strongest evidence is the specific improvement, not a claim that you transformed the team's culture.

When discussing a failure, own your part. If your instructions were ambiguous, explain how you made later requests clearer. Avoid placing all responsibility on a junior colleague while describing yourself as the person who rescued the work.

How should you handle a client-judgement question?

First understand the objection. A client may disagree with an assumption, the risk tolerance or the objective itself. Those are different problems. Repeating the original analysis more forcefully does not resolve them.

State what evidence supports your recommendation, what remains uncertain and what alternatives exist. If new information changes the conclusion, explain that change clearly. If it does not, describe the trade-off without pretending the client has no choice.

In an interview example, be precise about your authority. Supporting a presentation is different from owning the client relationship. Both can provide useful evidence if described accurately.

How do MBA and lateral candidates adapt the preparation?

Associate preparation shares its foundation with the analyst round but is judged against delivery rather than potential. Work the technical questions and DCF walkthrough until the mechanics are automatic, then spend the remaining time on the behavioral practice set, which is where associate answers are actually separated. If you are coming in laterally, the off-cycle and lateral guide covers the story problem specifically.

Use the job requirements to identify the evidence you already have and the gaps you need to address. A lateral candidate may have direct transaction examples. An MBA candidate may need to connect prior work and academic preparation to the responsibilities in the vacancy. Neither label establishes one universal interview process.

The off-cycle and lateral guide separates recruiting routes. Here, focus on whether your examples demonstrate the judgement and technical reasoning you claim.

Frequently Asked Questions

Must every example come from banking?

Use relevant experience honestly. Explain what transfers to the role and what it does not demonstrate. Do not invent banking responsibility to fit a prompt.

Should I memorise a deal script?

Prepare a structure and know your facts. You should be able to answer follow-ups about your own contribution without returning to a memorised paragraph.

What if I have never managed an analyst?

Say so. Use a real coaching, collaboration or review example and make its scope clear. Do not imply a reporting relationship that did not exist.

Is there one associate interview format?

This guide does not claim one. Follow the employer's instructions and prepare for the responsibilities in the actual vacancy.

Sources

• Morgan Stanley: interview preparation (checked 5 September 2026).