How to Answer \"Walk Me Through Your Resume\" (Finance)
The interviewer says "walk me through your resume," and you freeze, because it sounds like an instruction to read the page back to them top to bottom. It isn't. They want a two-minute story that starts in your past and arrives, by logical steps, at why you're sitting across from them for this finance or consulting role. This guide gives you the connect-the-dots structure, a filter for picking which two or three experiences make the cut, and a full worked student example you can copy the shape of. It's a close cousin of "tell me about yourself," but not the same answer, and the difference matters.
What the interviewer is actually testing
In early-cycle finance, consulting, and investment banking interviews, "walk me through your resume" is usually the Wave-1 opener, the question that replaces "tell me about yourself" the moment things turn serious. It frequently shows up even earlier, on the recruiter phone screen, before you ever meet a banker.
They are not testing your memory. They already have the page. Two things are graded. First, can you separate signal from noise: given six lines of resume, do you know which two or three matter and which are wallpaper? Second, does your path make sense: when you connect your experiences in order, do they build toward wanting this job, or is it a random walk that happened to land here?
Reciting the resume fails both tests at once. It shows you can't prioritize, and it never explains why any of it points at this room.
The connect-the-dots structure
The whole trick is that this is a walk, not a list. A list is "I did A, then B, then C." A walk is "I did A, which made me want B, which is why I did C, and that's what brought me here." The transitions are the answer. Without them you have a resume read out loud with extra steps.
Run it in four beats:
- The starting point. One or two sentences: your year, your major, and the spark that got you interested in this direction. Keep education brief. This is a launch pad, not a chapter.
- Experience one, and what it pushed you toward. What you did, then the hinge: what it made you curious about or want next.
- Experience two (and maybe three), each handing off to the next. Same move every time. Each experience closes with a sentence that opens the next one.
- Why this firm and this role, now. The walk arrives. The momentum you've built should make wanting this internship feel like the obvious next step, not a hard pivot.
The sentences connecting the beats are where you win or lose. "That made me want X, which is why I did Y" is the shape you repeat. Say it three times and the interviewer stops hearing a resume and starts hearing a person with a direction.
Which 2-3 experiences to pick
Here's the selection rule, in one line: keep an item only if it advances the "why this path" thread toward this role. If an experience doesn't hand off to the next dot or explain why you wanted the next thing, cut it, however impressive it looks on paper.
That means two or three experiences, not six, ordered so the story moves forward in time. Chronological, earliest relevant dot to now. Zig-zagging between years makes the interviewer rebuild the timeline you were supposed to hand them.
Impressive-but-irrelevant is the hardest thing to cut. A prestigious club presidency unrelated to markets earns a mention only if it hands off to a dot that does. Relevance beats shine.
When your resume has no finance on it
Most students interviewing for a first finance or consulting internship have no finance on the page, and that's fine. You build the same arc from non-finance material. Each of these earns a slot if it advances the thread:
- A quantitative class. An intro econ, statistics, or accounting course that switched something on. The dot isn't the grade, it's "this made me want to see how it works with real money."
- A stock-pitch or investment club. Even a small one. Building or defending a pitch is the closest thing to the job you can point at, so it usually deserves a beat.
- A customer-facing or execution job. Retail, serving, a summer sales gig. It shows you can carry a workload under pressure, and it hands off cleanly to "I wanted work with more analytical weight behind it."
You never apologize for any of this. You thread it.
A worked student example
Here's one full answer, roughly two minutes, from a thin resume: an intro econ course, a self-taught valuation project, an investment club, and a summer coffee-shop job. The connective tissue is labeled so you can see the handoffs.
"I'm a third-year economics major at State. I came in without a clear plan, but an intro macro course my first year was the thing that got me hooked, specifically the sessions on how capital actually gets allocated. starting point
That pushed me to try it hands-on, so over a summer I taught myself the basics of valuation and built a rough DCF on a retailer I actually shop at. It was messy and I got some of the assumptions wrong, but figuring out why my number was off taught me more than the course did. experience one, hands off to wanting to do it with other people
Wanting to pressure-test that against people who knew more, I joined our student investment club and eventually pitched that same company to the group. Defending my assumptions when someone challenged the growth rate was the part I liked most. experience two, hands off to wanting real stakes
Alongside all that I worked at a coffee shop over the summers, which sounds unrelated, but running the morning rush taught me to stay organized and calm when five things are happening at once. experience three, hands off to wanting analytical work under real pressure
Putting those together, I want to do the analytical work I've been doing on my own, but on live deals and with a team that can teach me, which is exactly why I applied to this analyst internship. why this role, now"
Notice the numbers are vague and clearly the student's own: "a rough DCF," "some assumptions wrong." Nothing reads as a benchmark, because nothing is one. Every beat ends by opening the next. That's the whole trick.
The traps that sink this answer
- Reciting line by line. "In 2024 I did X, in 2025 I did Y." They have the page. This wastes your two minutes proving you can read.
- The full life history. Nobody in a banking interview needs your childhood or why you loved numbers as a kid. Start at the first relevant dot.
- Four roles nobody remembers. Cram in every bullet and none of them land. Two or three dots, threaded, beats six dots listed.
- Zig-zagging in time. Jumping between years forces the interviewer to rebuild your timeline. Go forward, once.
- Apologizing for a non-finance background. "I don't really have finance experience, but..." plants doubt before you've made your case. Thread the econ class and the club instead.
Frequently asked questions
Is "walk me through your resume" the same as "tell me about yourself"?
They're close, and often interchangeable, but the default shape differs. "Tell me about yourself" is a thematic answer that starts in the present and runs present, past, why-this-role in about 60 to 90 seconds. "Walk me through your resume" is chronological: you start in the past and connect the dots forward, and it runs a little longer, closer to two minutes, with a finance or consulting frame.
How long should "walk me through your resume" be?
Aim for about two minutes, roughly 200 to 300 spoken words. That's a convention, not a stopwatch rule: long enough to build a genuine arc across two or three experiences, short enough that you don't lose the room. Time yourself once so you know where you land.
How do I answer with no experience, or no finance experience?
Build the same arc from what you have: a quantitative class, a stock-pitch or investment club, a customer-facing job. Each earns a slot if it hands off to the next dot. Lean on the thread and on what you're learning now, and don't apologize. First-time interns aren't expected to arrive with finance on the page.
What order should I go in, chronological or reverse?
Chronological. The point is momentum: earliest relevant dot to now, each experience pushing you toward the next. Reverse order breaks the "that's why I did the next thing" logic that makes it a walk instead of a list.
What should I not include?
Anything that doesn't advance the thread. Cut the childhood origin story, the line-by-line recital, and impressive-but-irrelevant roles that don't hand off to a relevant dot. If an item doesn't explain why you wanted the next thing, it's noise.
Tonight: write your timeline out in full, then cut it to two or three experiences using the filter, keeping only the dots that hand off to the next one. Say it aloud against a timer until it lands near two minutes and the transitions sound like you talking, not reading. If you're on the consulting track, do the same prep for the case interview and the rest of the interview questions. Then keep applying so you get more reps: browse internships while early-cycle recruiting is still open.