behavioral interview for investment banking
the technical side gets you in the door – the fit part decides whether you get the offer. “why investment banking”, “why this bank”, “tell me about a situation under pressure”: these questions look harmless, but this is exactly where candidates who haven’t prepared their stories fall short. on this page we show how to structure convincing, honest answers, which questions actually come up and what the person across the table is listening for.
why the fit part decides your offer
in the final round, most candidates are technically solid. the difference then comes down to the human side: can the team picture spending long nights in the deal room with you? do you come across as resilient, reliable and honest? bankers don’t hire résumés, they hire people – and the behavioral part is where that is decided.
the most common mistake is to underestimate the fit part and answer off the cuff. good candidates have three to five core stories ready that they can flexibly apply to different questions.
the STAR method for structured answers
for storytelling questions, STAR is the backbone of every good answer: situation (brief context), task (your responsibility), action (what exactly you did – the longest part) and result (the measurable outcome). the structure keeps you from rambling and ensures every story ends with a concrete result. prepare your core stories once cleanly in STAR format – then you can recall them flexibly in the interview.
getting the tone right
tone is what candidates most often misjudge, and it is not the same everywhere. some interviewers expect confident self-promotion; in front of other teams the identical delivery reads as put-on. the register that travels is specific and understated: concrete results, credit shared where it is due, and a realistic picture of the job – including the hours. anyone who romanticizes the work seems naive; anyone who describes it accurately and still wants it convinces. and if any round runs in a second language, rehearse your core stories in both – the technical vocabulary usually stays english even when the rest of the conversation does not.
example questions with worked solutions
“why this bank?”
solution: build the answer around two or three specific, verifiable reasons. example: “first, your M&A practice in industrials is a leader – exactly the area I want to work in. second, I spoke with [name] from the team, and the way you give analysts responsibility early convinced me. third, I value the team size: close enough to the deal to really learn.”
the test: would your answer fit any other bank just as well? if so, it’s too generic. the more specific, the more credible.
“tell me about a situation where you delivered under pressure.”
solution (STAR): situation – during an internship a competitive analysis had to be finished overnight and a team member dropped out. task – I was to complete the analysis on my own and prepare it to presentation standard.
action – I broke the task into blocks, prioritized the most important competitors, clarified open questions with the associate early, and worked from a clean template instead of starting from scratch. result – the analysis was on the desk by seven and went into the pitchbook without major changes. lesson: under pressure, prioritization and asking questions early matter more than speed.
“what is your greatest weakness?”
solution: name a real, non-disqualifying weakness plus a concrete step to improve. example: “I used to tend to optimize tasks on my own for too long instead of sharing interim results. in my last internship I got into the habit of actively sharing early drafts for feedback – it saves the team time and me nights.” avoid disguised strengths like “too perfectionist” – that sounds rehearsed and dishonest.
how to prepare the fit part
write your core stories in STAR format before you practice them out loud – writing forces clarity. the tone differs by target: for the internship genuine interest counts, while for the analyst interview resilience and maturity matter too. the full overview of both technical and fit is in the guide to IB interview preparation.
frequently asked questions about the behavioral part
STAR stands for situation, task, action, result. you briefly describe the context (situation), your responsibility (task), what exactly you did (action) and the measurable outcome (result). the method forces you into a clear structure instead of a rambling monologue – and ensures there is a concrete result at the end. ideal for all “tell me about a time when …” questions.
with concrete, verifiable reasons – not with flattery. name two or three specific points: a particular deal experience or sector the bank is strong in, a conversation with an employee that showed you something, or the team size and way of working. the more interchangeably your answer fits other banks, the weaker it is.
name a real weakness that isn’t disqualifying, and show how you’re working on it. avoid disguised strengths like “I’m too much of a perfectionist” – bankers see through that immediately. honesty plus a concrete step to improve comes across as more mature than an evasive answer.
very important. the technical side gets you shortlisted, but among several technically solid candidates, fit decides. banks hire people they want to sit next to in the deal team at two in the morning. anyone who comes across as likeable, resilient and honest about the reality of the work has a real advantage.
yes, and more than candidates expect. some interviewers want confident self-promotion; in front of other teams the same delivery lands as over-the-top. the register that travels is specific and understated – concrete results, honest about what you did and did not do yourself. and if a round runs in a second language, be able to tell your core stories fluently in both: the technical vocabulary usually stays english even when the rest of the conversation does not.
ask two or three thoughtful questions that show genuine interest – for example about the kind of deals the team does, the collaboration between analysts and associates, or what the interviewer personally finds appealing about their role. avoid questions whose answers are on the website, and questions only about salary or working hours. good questions are remembered.