You’ve worked through ten decks of technical material, which means the harder half of the preparation is already behind you. This deck is about the other half: the questions that have nothing to do with valuation, and the delivery that decides whether your technical work ever gets seen. None of it is about performing a character, and nothing here will tell you what your story should be, because that part is yours. What it covers is what each question is really testing, the shape of an answer that lands, and how to stay steady when a conversation goes somewhere you didn’t plan for. Read it once early, then again the week of.
16 cardsInvestment bankingFree, no signup
Card 1 of 16
An interviewer opens with “so, tell me about yourself.” You have a resume walk prepared and ready to go. Are these the same question, and if not, how do they differ?
Tell me about yourself asks who you are now, the resume walk asks how you got here.
They overlap, but the scope is different. Tell me about yourself invites a short, present-tense framing: what you’re doing now, what pulled you toward finance, and what you’re looking for next, usually inside a minute. The resume walk is chronological and longer, tracing the decisions that connect one line of the page to the next. If you answer the opener with a full four-minute history you’ve misread the room, and most interviewers will politely let you keep going rather than stop you.
Card 2 of 16
“Walk me through your resume.” It’s the first question in most banking interviews, and it sounds like a formality. What is the interviewer actually testing, and how should the answer be shaped?
A resume walk is a story about choices, not a list of jobs, and it should end pointing at this seat.
Nobody needs the page read back to them, they have it in front of them. What’s being tested is whether your path has a logic to it and whether you can narrate something clearly under mild pressure, which is a fair share of what a junior banker does on a call. Move roughly forward in time, give the most airtime to the two most recent and most relevant experiences, and at each step say why you made the move rather than only what the role was. Land the last sentence on why that path leads here.
Card 3 of 16
“Why investment banking?” What does a credible answer actually contain, and which answers quietly hurt you?
A credible answer names the work you want to do, not the prestige, the pay, or the pace.
Two things are being checked: that you understand what the job really involves day to day, and that your reasons will survive a bad month. The answers that fall flat are the interchangeable ones, that you like finance, that you’ll learn a lot, that it’s fast-paced, because they would apply equally to a dozen other jobs. Stronger answers point at something specific: the analytical work of putting a value on a business, seeing how large decisions actually get made, a moment in a class or a role that made that concrete. Pay and prestige are real motivations, they just don’t predict who stays.
Card 4 of 16
You’re interviewing with a mid-sized bank on Thursday and a much larger one on Friday, and both will ask “why us?” How do you get specific without sliding into flattery?
Name something true about the bank that would change your actual day, not its reputation.
Telling a bank that it’s excellent tells them nothing, since every candidate says it. Useful specifics are the things that genuinely differentiate the seat: the group’s sector focus, the size of deals a first-year would touch, how lean the teams run, whether the programme is generalist or you’re placed straight into a group. Anything concrete you learned from someone who works there counts, provided you can say what you learned and not just who you spoke to. The simplest test is to paste a rival bank’s name into your answer, and if it still reads fine, you don’t have an answer yet.
Card 5 of 16
“What’s your greatest weakness?” Why does a polished answer like “I care too much about getting things right” usually cost you more than an honest one?
The weakness question tests self-awareness, so a disguised strength answers a different question badly.
Interviewers have heard the perfectionist answer hundreds of times and read it as either a genuine lack of self-knowledge or an unwillingness to be candid, and both matter in a job where you have to flag your own mistakes quickly and without being asked. A real answer names something true but survivable, ideally not the central requirement of the role, then spends most of its length on what you’ve done about it and what changed. Strengths work the same way in reverse: claim one, then give the evidence, because an adjective with nothing behind it is only a word.
Card 6 of 16
Your interviewer asks for a time you handled a difficult deadline. What’s the shape of a strong behavioural answer, and how do you use that shape without sounding like you’re reciting it?
Set the scene fast, spend the answer on what you personally did, then close on a concrete result.
Most behavioural answers work in three parts: a brief situation so the listener knows the stakes, then the actions you took, then the outcome. The common failure is two minutes of background and thirty seconds on your own contribution, when that middle stretch is the only part being assessed. Keep the setup to a couple of sentences, say I rather than we when describing what you did, and finish with something specific enough to picture, a number, a decision that got made, a deadline that got met. Rehearsing the shape is sensible, memorising the sentences is what makes an answer sound canned.
Card 7 of 16
“Tell me about a time you disagreed with someone on a team.” The interviewer will never check the story, so what are they actually listening for?
Conflict questions test how you talk about people you disagree with, not whether you won.
The substance of the disagreement matters far less than how you describe the other person. An answer that casts a teammate as lazy or slow tells the interviewer roughly how you’ll sound about a colleague at two in the morning in a deal room, which is exactly the risk being screened for. What lands is a story where the other side held a reasonable position, you did something concrete to understand or resolve it, and the working relationship came out intact. A real, modest disagreement beats a dramatic one, and a resolution where you changed your own mind is not the weak version.
Card 8 of 16
“Tell me about a time you failed.” Why does the reflection at the end of that answer carry more weight than the failure at the start of it?
The failure is only the setup, what you changed afterwards is the actual answer.
Everyone has failed at something, so the failure by itself carries almost no information. What the question separates is people who can own an outcome and learn from it from people who deflect, quietly blame someone else, or reach for something so trivial that nothing was ever at stake. Pick something that genuinely went wrong, state your own part in it without an alibi, then give the back half of the answer to what you understood afterwards and what you did differently the next time. In a job where juniors make real mistakes on live documents, that pattern is the entire point of asking.
Card 9 of 16
“Where do you see yourself in five years?” Analyst programmes typically run two or three, and everyone in the room knows it. What is the question really getting at?
Five-year questions test whether your ambitions and this job point in a compatible direction.
There’s an honest tension here and interviewers are aware of it: the programme is finite, plenty of people move on afterwards, and nobody expects someone in their early twenties to have the next decade mapped out. What’s being checked is that the next few years are a deliberate choice rather than a default, and that you aren’t describing a plan this seat plainly cannot serve. A workable answer commits to doing the analyst job well and being genuinely useful to a team, then describes the direction you’re drawn to in terms of the work rather than a job title. Claiming you’ll be a lifer tends to read as false.
Card 10 of 16
Halfway through the interview: “so, what deal or market have you been following?” How do you talk about it in a way that shows judgement rather than just recall?
Say what happened, why it happened, and what you think, with the last part carrying the weight.
Facts anyone could take from a headline prove nothing, because the interviewer has read the same headline. A good answer moves in three steps: what happened, in about two sentences, then why the buyer or the market did it, meaning the strategic or financial logic, then your own view, including where you think the risk sits or what would have to be true for it to work. Only that third step shows judgement. Choose something you actually find interesting and can hold up under two follow-up questions, rather than the biggest transaction of the year that you only skimmed.
Card 11 of 16
The interviewer glances at the clock and says “we’ve got five minutes left, do you have any questions for me?” What does the question you pick actually signal?
Your question shows what you think the job is, so ask something only this person could answer.
This is still part of the assessment, and passing entirely tends to read as indifference. Questions whose answers sit on the bank’s website, or that ask what an analyst does all day, suggest you haven’t done the reading. What works is drawn from the person in front of you: how a recent staffing actually ran, what surprised them in their first year, how feedback reaches juniors in their group, what they’d want a new analyst to be good at on day one. Ask because you want to know, then listen, because the follow-up you ask says more than the opening question did.
Card 12 of 16
Mid-interview you’re asked a multi-step technical question, and for a second your mind goes completely blank. How do you think out loud instead of freezing?
Say the first true thing you know out loud, then reason forward one step at a time.
Silence is the expensive part, because from the other side of the table thinking and drowning look identical. Buy a beat honestly, repeating the question back or asking a clarifying question is perfectly acceptable, then start from something you’re certain of and build outward one step at a time, naming each assumption as you make it. Being talked through a wrong turn is normal, and often reads better than a fast correct answer, since much of the actual job is reasoning aloud with someone more senior. Close by checking the result against common sense rather than stopping the moment a number appears.
Card 13 of 16
An interviewer asks you something technical you have genuinely never seen before. What’s the best available move, and why is answering confidently anyway the worst one?
Say what you don’t know, offer how you’d work it out, and let the interviewer take it from there.
Every interviewer knows there are things you haven’t covered yet, so one gap is rarely fatal on its own. Bluffing is closer to fatal, because it’s usually transparent, and it suggests you might do the same on a live model where a wrong number reaches a client. Say plainly that you’re not sure, then give whatever you do have, an adjacent concept, the logic you’d reason from, or how you’d go and find out. Then let it go and answer the next question well, because carrying the last one around with you costs more than the gap ever did.
Card 14 of 16
You’ve been invited to a superday: five back-to-back thirty-minute interviews with people at different levels. What does that format change about how you prepare?
Five interviewers compare notes afterwards, so it has to be the same story every time.
A superday is a run of short interviews on one day, and afterwards those people sit in a room and compare impressions before anyone gets a call. That makes consistency matter more than polish: if your reason for wanting banking shifts between the second conversation and the fourth, someone will notice it in the debrief. It also means each conversation starts from nothing, so repeating your best material is expected rather than lazy, and the energy you bring to the fifth counts as much as the first. Treat the repetition as an advantage, you get several attempts at landing the same point.
Card 15 of 16
You’re two sentences into an answer when the interviewer cuts across you and says flatly, “I don’t think that’s right.” What’s happening, and how do you handle it?
Pushback tests composure, so answer the challenge itself and ignore the tone it arrived in.
Sometimes the interviewer genuinely disagrees, sometimes they’re testing whether you collapse or dig in irrationally when someone senior pushes back, which happens constantly in the real job. Either way the move is the same: don’t rush to agree, and don’t defend by talking louder. Ask which part they’re questioning, restate your reasoning in a single sentence, and change your answer if their point is better than yours, saying so plainly. Being persuaded is a good outcome, and so is holding a position calmly with a reason attached. What reads badly is instant collapse, or visible irritation.
Card 16 of 16
Two candidates handle the technical questions equally well and only one gets the offer. What tends to separate them, and why does the other one usually never find out?
Most close rejections turn on whether people wanted you next to them at 1am, not a missed question.
Underneath the structure, interviewers are answering something unglamorous: would I want this person on my team at one in the morning on a Sunday. The things that quietly cost people offers are rarely technical, they’re being hard to talk to, treating a junior interviewer or a recruiter differently from a senior one, sounding so rehearsed that nothing about you is readable, showing no curiosity about the work, or being unable to say anything specific about why you’re there. Almost none of it gets fed back, because recruiting feedback is thin and the honest version is awkward to give. It’s also the most fixable part.
Reading is not the same as remembering. Study this deck with scheduled review so the cards come back before you forget them.