Core Questions

Interviewers decide how they feel about a candidate within the first few minutes, which makes this the single most consequential answer given in the entire interview. While a candidate talks, the interviewer is quietly forming a read on things that never get asked directly: does this person seem genuine, do they have the energy wanted on a demanding late night, would they be trusted in front of a managing director. This answer is the chance to show preparation, clarity under a small amount of pressure, and a confidence in one's own story that carries into everything that follows.

What's actually being tested is whether a candidate can tell a clear, connected story instead of reciting a resume that the interviewer is already holding. The interviewer is checking that the path builds toward banking, that each move was a real decision rather than something that just happened, and that the candidate can stay concise and composed with the floor entirely to themselves.

The answer works best built as one connected story in four beats, kept to roughly ninety seconds without running much past it. The first beat is a one-line intro: what the candidate is studying, their year, and where they're from, nothing more. The second beat is the spark, whatever first pulled them toward business or finance, which doesn't need to be finance itself but should connect naturally to what came next; a club, an early job, or a specific class works well, and from there the story should move into college and the experiences that got more serious.

The third beat is the core of the answer: the experiences in order, and for each one, reaching past what was done to what was actually taken from it and why the team needed that person there specifically, since that's what signals future analyst potential rather than past task completion. The contrast between experiences, what one was missing that the next one supplied, is what makes the path feel intentional rather than accidental, and that throughline doesn't need to have been felt at the time; explaining it honestly in hindsight is completely fine as long as the takeaway itself is genuine. The fourth beat ties it together: closing by connecting the story directly into why banking, and why this specific firm, ideally referencing an actual conversation already had with someone on the team, since that's the detail that makes the close land as specific rather than generic.

The most common failure is opening flat, background and school with no spark, so the interviewer is only half listening by the time anything interesting arrives. A close second is reciting the resume line by line rather than telling a story with actual reasoning behind each move, which reads as a list rather than a narrative. Experiences that don't build toward banking, presented as separate unconnected jobs with nothing showing why one led to the next, undercut the whole point of the exercise, as do vague takeaways like 'I learned a lot' that connect to nothing specific.

Two mistakes are more about delivery than content: overstaying on background or early history, which burns the ninety seconds before reaching the material that actually matters, and sounding rehearsed and robotic rather than like a person the interviewer would genuinely want sitting next to them on a live deal. An answer that could have been given by literally any other candidate, with no specific, memorable detail anywhere in it, has failed at the one thing this question is actually testing.

The answer should open with the specific moment or experience that first pulled you toward this kind of work, told as something that happened rather than a rehearsed line. It can be a class, a competition, a family business, or the first deal you followed closely in the news. The test is whether it sounds like it could only be yours: a line like 'I've always been interested in finance' fails immediately, because anyone could say it and it gives the interviewer nothing to remember.

Keep the whole answer to roughly 30 to 45 seconds. This question usually follows right after your background story, so it should read as one continuous conversation, not a second full narrative, which means the spark here can be brief, a sentence or two, before moving into the reasons that follow.

After the spark, name two or three specific things about the work that genuinely excite you, the kind of reasons a person who actually understands the job would give: the responsibility analysts get early relative to other entry-level jobs, the pace that forces fast growth, or being part of one of the biggest decisions a company makes. A little structure helps the interviewer follow you, something like signposting that it comes down to a few things and then walking through each one.

A reason stated on its own is just a claim, the same one every other candidate is making. What makes it credible is pairing it with a real moment: an internship where you saw a live deal up close, a class project where you got pulled toward valuation instead of the stock price, a summer where you went from barely following a model to building pieces of it yourself. The evidence is what shows the interest held up once you actually did the work, rather than staying a nice idea.

The most common failure leads with money, even when it's true, since stating compensation as the primary motivation tells the interviewer nothing about fit and reads as if the real work was never considered. A close second is a fully generic answer, wanting to learn a lot, work with smart people, or be in a fast-paced environment, that could be recited for consulting or any other competitive industry with one word swapped. A third is over-rehearsing to the point the answer sounds scripted rather than conversational; a natural, slightly imperfect answer that clearly reflects real thought reads better than a flawless one that sounds memorized.

This answer is also usually the direct setup for why this firm, so keep it consistent with whatever comes next: the general reasons given here should be the same ones a firm-specific answer later points at one particular bank and group.

A credible 'why this bank' answer requires specific, current knowledge: recent deals the firm or the specific group has worked on, the firm's particular strengths (a leading restructuring practice, a strong TMT franchise, a distinctive regional presence), and ideally something learned directly from a networking conversation with someone at the firm, which signals the candidate did real homework rather than reading only the firm's own marketing materials.

Generic praise ('great culture,' 'top bank') that could be said about any firm on a target list is the clearest signal of a candidate who hasn't done this homework, the fix is concrete: name a specific deal, a specific group's reputation, or a specific detail from an actual conversation with someone at the firm.

Beyond naming facts about the firm, the strongest answers explain why those specific traits matter to the candidate personally, for example, why a smaller analyst class and more direct deal exposure (typical of a boutique) appeals to someone who values hands-on learning, or why a firm's specific coverage strength in an industry connects to the candidate's own stated interests from earlier in the conversation.

This is also where the earlier 'why banking' and 'why this bank' answers should reinforce each other rather than feel disconnected, if a candidate says they're interested in industrials but pitches a firm mainly known for its TMT practice without addressing that mismatch, an attentive interviewer will notice the inconsistency.

A frequent, sharper follow-up asks a candidate to distinguish the firm from its closest competitors directly, testing whether the candidate's interest is genuinely specific or whether any similar firm would receive the identical pitch. The strong response draws a real distinction (a specific group's reputation, a particular deal type the firm is known for, feedback from actual conversations with people there) rather than deflecting or admitting the firms are interchangeable.

Handled well, this follow-up is an opportunity to demonstrate depth rather than a trap, a candidate with genuinely specific reasons for a firm will find this question easy; a candidate reciting a templated answer usually stumbles here first.

This is the same underlying answer as 'tell me about yourself,' built around the same four beats: an intro, the spark, your experiences in order, and a close tying it to banking. A resume walkthrough should be a concise (60-90 second), forward-moving narrative that connects each major experience to the next, explaining not just what you did, but why each step led to the next one, ending naturally at 'and that's what led me to want to pursue investment banking.' It is not a recitation of every bullet point on the resume; it's a story that the interviewer can follow without needing to look down at the paper.

Practicing this out loud, multiple times, is essential, a walkthrough that only exists as bullet points in your head tends to come out disorganized in the moment, while one that's been rehearsed as connected narrative flows naturally even under mild nerves.

A resume with a major or career pivot, a gap, or an unconventional path doesn't need to be hidden, it needs a clear, confident explanation of the reasoning behind the change, framed as a deliberate decision rather than something that happened to the candidate. Interviewers are generally far more comfortable with an honest, well-reasoned explanation of a pivot than with a walkthrough that visibly avoids or rushes past an obvious gap in the story.

The goal is coherence, not a spotless narrative, a candidate who can explain why they left one path for another, and connect that decision logically to their current interest in banking, comes across as more self-aware than one whose story has no complexity at all.

Every line on the resume is fair game for a follow-up question, and interviewers frequently drill into whatever specific detail catches their interest rather than staying on the high-level narrative, a listed project, a specific internship task, or even a hobby. The practical preparation is being ready to go two levels deep on anything listed: not just what a past role or project was, but specifically what you did in it and what you learned.

This is also why nothing should appear on the resume that the candidate isn't prepared to discuss in real detail, an inflated or vague bullet point is far more likely to produce an uncomfortable moment than to impress, since it invites exactly the kind of drill-down question it can't withstand.