Your Story

Chronological, roughly ninety seconds, with a thread. Open with a sentence on where you started and what pulled you toward finance. Move through two or three experiences, and for each one say what you did and what it taught you that points toward banking. Close on why you are sitting here today and why this firm. The structure is: origin, two or three steps, and a landing.

Every experience should be doing work in the story. If you cannot say what a bullet contributes to why-banking, cut it. The best versions sound like a person explaining their reasoning, not a candidate reading a list. Land on the present and make the last sentence about them, not you.

• Reciting the resume line by line with no thread
• Running past two minutes
• Spending equal time on every role instead of weighting the relevant ones
• No mention of why banking or why this firm
• Starting in high school, or earlier

Pick a situation with genuine friction or a real deadline, not a smooth group project. Two sentences of setup: what the team was, what the goal was, what made it hard. Then your specific contribution, said in the first person singular. Then the outcome, with a number if you have one. Close with what you would do differently, which is what separates a story from a boast.

Specificity about what you personally did. "We" is fine for context and useless for assessment, so the middle of the answer should be "I". A concrete outcome beats an adjective, and one honest reflection at the end signals you actually learned something.

• Saying "we" throughout so your own contribution is invisible
• A frictionless story where nothing was at stake
• Taking credit in a way that implies the team was incidental
• No outcome, or an outcome with no measure
• Running past two minutes

A check on whether you know what you are signing up for. Be concrete: building and updating models, preparing pitch materials and CIMs, running comparable analyses, coordinating diligence, and a lot of formatting and version control. Acknowledge the unglamorous share honestly, then say what still appeals. A romanticized answer signals you have not spoken to anyone in the job.

Specific tasks rather than abstractions, and honesty that much of it is repetitive and detail-heavy. Saying you have asked analysts about this and repeating what they told you is the strongest version.

• Describing the job as constant high-stakes deal negotiation
• No mention of the formatting, checking and coordination reality
• Vagueness that shows you have not spoken to anyone doing it
• Sounding put off by the unglamorous parts
• Confusing the analyst role with a private equity or corporate development role

Same material as the standard walkthrough, stripped of the content. Give four or five transitions, each in one sentence of the form: I was doing X, I noticed or wanted Y, so I went to Z. Ninety seconds total. The point is that each move must be caused by the previous one, so the last transition lands on this job as the obvious next step rather than a leap.

A chain where each decision is explained by something you learned in the prior role, not by an opportunity that happened to appear. The strongest version admits one move that was partly luck and then shows what you deliberately did with it, because a story where every step was planned from age sixteen is not believable.

• Reciting duties again instead of answering the question asked
• Every transition explained as an opportunity that came along
• A move with no stated reason, which reads as something you are hiding
• The chain does not actually arrive at banking
• Claiming a ten year plan formed before you had any exposure

A timing question, not a motivation question, so do not re-answer why banking. Give two reasons: the training is front loaded and hardest to acquire later, and the analyst seat is genuinely entry level, so joining at thirty means competing with people who have had five years of reps. Then add the honest personal reason that this is the point in your life when the hours are cheapest for you to pay.

Treating it as a question about the shape of a career rather than about enthusiasm. Acknowledging that lateral entry exists but is narrower shows you have actually looked at how people get in, rather than assuming the analyst program is the only door.

• Repeating your why banking answer without addressing timing
• Implying banking is a two year stop before the real plan
• Claiming no other path could teach you anything
• No acknowledgment that the hours are a real cost to something
• Sounding as though the timing was decided for you by the recruiting calendar

Structure it around what you learned about their position before you argued, because that is the part candidates skip. Four beats: what they believed and why it was reasonable, what you did to understand it, the one piece of evidence or reframing that moved them, and the outcome. Ninety seconds. Choose a case where the other person was not obviously wrong, or the story proves nothing.

The persuasion working through evidence or through a reframe of the goal, rather than through persistence or seniority. Saying what you changed in your own position during the conversation is the strongest single line available, because it shows you were arguing to get to an answer rather than to win.

• Choosing an example where the other person was plainly wrong
• Persuasion by wearing them down or by going over their head
• No account of why they believed what they believed
• Never conceding a single point of theirs
• A vague outcome that does not say whether they actually changed

The trap is that unrequested extra work is often a nuisance, so the story has to show judgment as well as effort. Three parts: what you noticed that made the extra work worth doing, what you actually produced, and how you handed it over. The handover matters most: flagging it briefly rather than presenting it as a surprise deliverable is what separates initiative from overstepping.

Extra work that answered a question the requester was going to ask next, and was small enough to be checked quickly. Saying you asked first, or flagged it as optional when you sent it, shows you understand that senior people have limited attention and that unasked-for work spends it.

• Extra work nobody wanted or ever used
• Rebuilding or changing something without telling anyone
• Missing the original deadline in order to do the extra piece
• Framing it as proof you work harder than your colleagues
• No mention of how or whether it was received

Leadership does not require a title. Pick something where you took responsibility for an outcome that depended on other people. Set up what needed doing and why it was hard, describe how you got others moving, especially without formal authority, and give the outcome. The most interesting version involves persuading people who did not have to listen to you.

Concrete detail on how you actually influenced people. Naming a specific obstacle, a disengaged member or a disagreement about direction, and how you handled it, is far stronger than describing the project itself.

• Describing the project rather than your leadership of it
• Leadership by assignment only, with no real influence exercised
• No obstacle, so nothing was tested
• Taking sole credit for a group outcome
• No result

The more useful leadership question, because it is the only kind of leadership an analyst gets. Set up the situation in one line, then spend the answer on the mechanism: how you got people to do things when you could not tell them to. Usually one of three: you did the unglamorous coordinating work nobody wanted, you made the goal concrete enough to be worth joining, or you gave individuals ownership of a piece. Name which one.

A specific mechanism rather than a personality claim. The detail that lands hardest is the moment someone did not cooperate and what you did then, because leading willing people is not evidence of anything.

• A story where you actually did hold the title
• Attributing the result to being naturally persuasive
• No moment of resistance anywhere in the story
• Describing yourself doing all the work rather than leading
• Claiming credit for a group outcome in the first person throughout