How to answer: “Walk me through your resume.”

What they’re actually asking

This is an editing test disguised as a history lesson. They have your resume in front of them; they don't need it read aloud. They want the narrative thread: why each move made sense and what it was building toward.

How to structure your answer

Tell it as cause and effect, not chronology. For each role, one line on what you owned and one line on why you moved. The word "so" is your friend: "I learned X, so I went looking for Y." Land the story at this interview as the obvious next step.

Example answer

“I started in QA, where I got obsessed with why bugs shipped, so I moved into a dev role to fix them at the source. Two years there taught me I care most about what users actually touch, so I shifted to frontend. Now I've hit the ceiling of what a solo frontend dev owns at a small shop, and this team's design-system role is exactly the next problem I want.”

What sinks people

• Reading the resume top to bottom in a monotone list
• Spending equal time on every job instead of weighting recent and relevant
• Leaving the moves unexplained, which makes them look random