Build an investment banking interview story bank

Start with the question this article answers

The best preparation is not memorising answers. It is knowing which real experiences you can explain from several angles.

This interview playbook is designed to help you make one decision more clearly. It separates what can be evidenced from what needs checking, so you can use the guidance without borrowing someone else’s story.

Prepare five types of story

Choose one example of analytical work, a difficult deadline, a disagreement, a mistake or lesson, and a moment you helped a team. Use your own experience, not a borrowed deal narrative.

Keep the technical centre visible

Explain the question, the information you used, the judgement involved and what you produced. A story can be concise without flattening the technical work.

Practise the follow-ups

For each story, write the question that would expose an unsupported claim. Then practise answering it plainly. This is preparation, not performance.

A way to use this in practice

Interview preparation should begin with real experiences, not a script. Choose moments you can describe accurately and that reveal something relevant to the work.

A useful answer connects the situation, your contribution, the evidence and the decision. Technical detail matters, but so does explaining why you chose a particular approach.

Practice should include the awkward follow-up: what was your role, how do you know, what would you change, and what did the result actually mean?

Before you finish

Read the page once for meaning and once for accuracy. On the second pass, look for a claim that sounds stronger than the evidence behind it, a term that needs context or a step that assumes knowledge the reader may not have.

For an application, check names, dates, qualifications, systems and figures against the source you would use in an interview. For a career decision, record the date and context of any market or qualification information so you know when it needs refreshing.

Then make the smallest useful change. A clearer verb, a defined date, a named decision or a question for the next conversation can do more for an application than another layer of polish.

The last check is whether the reader knows what to do next. If they need to compare routes, prepare a story, review a file or ask an employer a question, make that action explicit rather than ending with a general encouragement.

Finally, read the finished piece as a person with limited time. The headings should let them find the answer quickly, while the examples and explanation should reward them for staying. If a paragraph only repeats the heading, cut it; if a decision still feels unclear, add the missing context. A useful resource should leave the reader more capable, not merely more informed.