Walk me through your resume.

The complete answer guide: what this question really tests, two example strong answers in different angles, the common weak answer rewritten, and the trap most candidates fall into. This is a background / intro archetype question — see the broader pattern guide for the structural shape.

What this question is really testing

The interviewer isn't asking you to recite your resume—they already have it in front of them. They're testing whether you can construct a coherent narrative that explains why you made each career move and where you're headed next. The specific signal they're looking for is pattern recognition: do your choices reveal consistent judgment, growing ambition, and logical progression, or do they suggest you're reactive, scattered, or running away from problems? They're also calibrating how you'll communicate with executives and stakeholders—can you synthesize complex information into a compelling story, or will you drown them in chronological details?

The binary read happens in the first 60 seconds. Either you sound like someone who makes intentional career decisions with clear reasoning, or you sound like someone who stumbled through a series of jobs without a unifying thread. The interviewer is particularly worried about red flags they can't directly ask about: job-hopping without growth, lateral moves that suggest stagnation, or gaps that indicate performance issues. Your narrative needs to preemptively address these concerns by framing each transition as a deliberate step toward building specific capabilities, not just taking whatever came next.

Two strong answers, two angles

Angle A: The capability-building narrative

"I've spent the last six years deliberately building end-to-end product skills in fintech. I started at Capital One as an analyst because I wanted to understand how financial products actually work from the inside—I shipped three features that increased credit card activation rates by 12%. I moved to Stripe as a PM because I wanted to see how a high-growth company builds infrastructure products, and I led the launch of their fraud detection API, which now processes $2B annually. Now I'm looking to join a company like yours where I can apply both the domain expertise and the platform-building experience to own a 0-to-1 product."

Angle B: The problem-obsession narrative

"I've been obsessed with supply chain efficiency since I worked in my family's restaurant and watched us throw away 30% of our inventory. That's why I joined Flexport after undergrad—I wanted to see freight forwarding from the operator side, and I built the first automated customs clearance workflow. After two years, I realized software was the bigger leverage point, so I taught myself to code and joined a logistics SaaS startup as an early engineer. We grew from 5 to 40 customers in 18 months. Now I'm ready to take on a technical lead role where I can shape product direction, which is why I'm excited about this position."

The common weak answer

"I graduated from State University with a degree in business, then I worked at Company A for two years in marketing, then I moved to Company B where I was a senior marketing manager for three years, and now I'm here interviewing with you because I'm looking for new opportunities to grow my career."

This fails because it's purely chronological recitation without causation—the interviewer learns job titles but has no idea why you made any decision or what you actually accomplished. It signals that you haven't reflected on your career arc and don't have a clear sense of what you're optimizing for. The phrase "looking for new opportunities to grow" is particularly weak because it's generic filler that every candidate says. A simple reframe: "I've spent five years testing different marketing channels to understand what I'm best at—I started broad at Company A, discovered I had a talent for performance marketing when I cut CAC by 40%, then moved to Company B specifically to scale paid acquisition, which I grew from $100K to $2M monthly spend."

The one trap most candidates fall into

The trap is treating each job with equal weight and trying to be comprehensive instead of selective. You feel obligated to mention every role, every responsibility, every project—after all, it's on your resume. But this creates a flat, meandering story where the interviewer can't distinguish what matters from what doesn't. The result is you spend 45 seconds on an internship from five years ago and rush through your most recent, relevant work.

The counterintuitive move is to be radically selective. If you have seven years of experience, you might spend 10 seconds total on your first two jobs ("I started in consulting to build business fundamentals") and invest 90% of your answer on the last two roles that directly connect to this opportunity. The interviewer will ask follow-up questions if they want more detail on something you skipped. Your job in the initial answer is to establish the throughline—the consistent thread that makes this interview make sense. If your early career doesn't serve that narrative, acknowledge it exists and move on. You're not hiding anything; you're respecting their time and demonstrating editorial judgment, which is itself a signal of seniority.

Common questions

Other background / intro questions