How to talk about your resume in an interview

"Walk me through your resume" sounds like the easiest question in the interview — it's just your own history, after all. But most people answer it badly, either by reciting job titles and dates the interviewer already has in front of them, or by rambling through every role with no sense of why any of it matters for this job. The resume walkthrough is a story with a point, not a recap. Here's how to tell it well.

Why this question isn't really about the facts

The interviewer can already see your titles, companies, and dates — reading them back adds nothing. What they're actually testing is whether you can narrate your own career with a clear thread: does one role lead sensibly to the next, do you understand why you made the moves you made, and can you connect your past to the job you're interviewing for right now. It's as much a test of self-awareness and communication as it is a history lesson.

A framework: Context → Contribution → Connection

1. Context. One sentence on what the role or company was, enough to orient someone who's never worked there. Skip the parts already on the page.
2. Contribution. What you actually did and the outcome, in specific enough terms that it sounds like you, not a job description. One clear example beats a list of responsibilities.
3. Connection. Why that role led to the next one — what you learned, outgrew, or wanted more of. This is the thread that turns a list of jobs into a story.

Repeat that three-beat pattern per role, spend more time on the roles most relevant to the job you want, and compress the rest. A five-year-old internship gets one sentence; your most recent, most relevant role gets several.

A worked example

"I started on the support team, which is where I learned the product inside out by talking to customers every day. After about a year I noticed the same three issues kept coming up, so I put together a breakdown for the product team and ended up being pulled into product work part-time. That's what made me want to move into product full-time, which is what I've been doing for the last two years — and it's also why a role like this one, closer to the customer-facing side of the roadmap, feels like a natural next step rather than a pivot."

Context (support team, briefly) → contribution (noticed a pattern, acted on it, got pulled into product) → connection (that's the thread to the role they're interviewing for). No job titles recited, no padding.

Handling gaps, jumps, and short stints

Not every resume reads as a clean line, and trying to force one onto a messy history usually sounds rehearsed. If there's a gap or a stretch that doesn't fit the thread, say what happened in one honest sentence and move on — dwelling on it signals insecurity more than the gap itself ever does. If you've had a layoff or an unusually short stint, a short, factual explanation works better than either over-apologizing or skipping it and hoping nobody asks. The goal isn't a perfect story; it's an honest one that still has a thread running through it.

Common mistakes to avoid

• Reading the resume out loud. Titles and dates they can already see add nothing. Narrate the why, not the what.
• Equal time for every role. A chronological march through every job, including the ones with nothing to do with this role, buries the parts that matter.
• No thread between roles. Jumping from job to job with no sense of why makes a genuinely coherent career sound random.
• Overexplaining a gap or a short stint. One honest sentence; then move forward. Lingering makes it sound bigger than it is.
• Ending without connecting to the job. The walkthrough should land on why this role, specifically, is the next logical beat — not just stop at "and that's where I am now."

Bottom line

Your resume already tells the interviewer what you did. Your job in this question is to tell them why it matters and where it's going — a short, honest thread from role to role that ends at the job you're sitting in front of them for. Context, contribution, connection, repeated per role, is enough to turn a list of jobs into a story worth listening to.

Related: How to explain being laid off or fired · How to end an interview strong · Common interview mistakes to avoid