To answer “walk me through your resume” as a software engineer, give a guided tour of about 60 to 90 seconds, not a reading of the page. Open with one line on who you are today, move through each relevant role or project in order, give one concrete result and one reason for each move, then finish with a bridge to why this role is the logical next step. The interviewer already has your resume open. What they want is the story between the lines: why you made each choice, how your scope grew, and which item they should ask about next.
Below: what interviewers listen for, a timed structure, when to go chronological or thematic, three example outlines (new grad, mid-level, career switcher), how to explain gaps and short stints, and how to prepare for the follow-up on every bullet.
What the interviewer wants from a resume walk-through
This question is close to “tell me about yourself,” but not the same. Our “tell me about yourself” guide covers the present-past-future pitch. A resume walk-through follows the document itself, so the interviewer can map what you say onto what they are reading. That makes the transitions the most important part: what you were doing, why you moved, and what you took with you.
| They are listening for | What it tells them | What weakens it |
|---|---|---|
| Trajectory | Whether your scope and ownership grew over time | Every role described at the same level of responsibility |
| Reasons for each move | Whether you make deliberate choices | “Then I got a job at…” with no why |
| One result per chapter | Whether your work had impact you can name | A list of technologies with no outcome |
| Relevance to this role | Whether you understand what they are hiring for | Equal time on everything, including unrelated jobs |
| Communication | Whether you can summarize your own work clearly | Running past three minutes without a pause |
Who asks changes the emphasis. A recruiter is checking fit, level and logistics, so keep it high level and mention the skills in the job posting. A hiring manager wants scope and judgment: team size, what you owned, decisions you made. An engineer on the loop will often use the walk-through to pick a project for a technical deep dive, so make sure the project you most want to discuss gets one memorable sentence.
The 90-second structure
Plan the time before you plan the words. A walk-through that runs long is usually spending too much time on the oldest chapters.
| Part | Time | What goes in it |
|---|---|---|
| Opener | About 10 seconds | Who you are now in one line: “I’m a backend engineer with four years in payments infrastructure.” |
| Earliest relevant chapter | 15 to 20 seconds | Degree, first job or first project; one thing you built or learned; why you moved on |
| Middle chapters | 15 to 25 seconds each | Scope, one result, the reason for the next move |
| Current role | 20 to 30 seconds | What you own, the most relevant recent project, what you are learning |
| Bridge | 10 to 15 seconds | Why this role is the next step, tied to something specific about the team or product |
Three rules keep it tight:
- One result per chapter. Pick the bullet with the clearest outcome and say it in plain words. The rest of the bullets are there for follow-ups.
- One “why” per transition. “I wanted to work closer to customers,” “the team was winding down,” “I wanted to own a service end to end.” Short, honest and forward-looking.
- End with a hand-off. “Happy to go deeper on any of these; the payments migration is probably the most relevant to this role.” This tells the interviewer where your best material is and gives them an easy next question.
If invited to take longer, add a second result to the current role, not more detail on the early chapters.
Chronological or thematic?
“Walk me through” implies order, and most of the time order is the right choice. But it is not the only option.
| Order | Best for | How to open it |
|---|---|---|
| Chronological (oldest first) | New grads and early-career engineers with a clear progression | “I’ll start with school, since that’s where I got into distributed systems.” |
| Reverse chronological (current role first) | Senior engineers with long careers, where the latest role is the most relevant | “I’ll start with what I do now and work backward, briefly.” |
| Thematic (grouped by skill or domain) | Career switchers, contractors, people with many short stints or a non-linear path | “My path wasn’t linear, so I’ll group it into the two threads that matter for this role.” |
Whichever you choose, say it in the first sentence, so the interviewer can follow along on the page. Reverse order also helps when your earliest experience is the least relevant.
Three example outlines
These are example outlines we wrote to show the shape, not scripts to memorize. Swap in your own roles, details and numbers you can defend.
1. New grad (chronological, about 75 seconds)
- Opener: “I’m graduating in May with a CS degree, and most of my experience is in backend and data work.”
- School: “I got into systems through an operating systems course and then joined a research lab building a tool that profiled slow database queries.”
- First internship: “That led to a summer internship on an internal tools team, where I built a dashboard on-call engineers used to triage alerts. My mentor pushed me to write tests for everything, which changed how I work.”
- Second internship: “Last summer I wanted production traffic, so I interned on a payments team and shipped a retry change to a service that handles refunds.”
- Bridge and hand-off: “I’m looking for a backend role where I can keep working on reliability, which is why this team stood out. Happy to go deeper on the refunds project.”
Notice what is missing: GPA, every course and every club. If something is on the resume but not in the walk-through, the interviewer can still ask about it. For what the page itself should contain, see our new grad resume guide.
2. Mid-level engineer (chronological, about 90 seconds)
- Opener: “I’m a software engineer with five years of experience, mostly on high-traffic web backends.”
- First role: “I started at an agency building client sites, which taught me to ship fast and talk to non-engineers. I left because I wanted to work on one product long enough to see it scale.”
- Second role: “At my current company I joined the checkout team, then took over our order service when the original owner moved teams. My biggest project was splitting it out of the monolith, which I led with two other engineers.”
- Now: “Today I own that service and mentor the two newest engineers on the team.”
- Bridge and hand-off: “I’m looking for a role with more cross-team design work, which is what drew me to this platform team. The monolith split is probably the most relevant thing to dig into.”
3. Career switcher (thematic, about 90 seconds)
- Opener: “I moved into software engineering two years ago after six years in supply-chain analysis, so I’ll group my background into two threads.”
- Thread one, the domain: “As an analyst I spent most of my time in spreadsheets and SQL, forecasting inventory. I started automating reports in Python, and that is what pulled me toward engineering.”
- Thread two, engineering: “I studied full-time for a year, built an inventory-tracking app that a local business still uses, then joined a logistics startup as a junior engineer, where I work on the shipment tracking API.”
- Bridge and hand-off: “This role sits right where both threads meet, since your product serves warehouse teams. I’m happy to talk through the tracking API or the app I built while I was retraining.”
The switcher version treats the earlier career as an asset, not a detour. Say what transfers (domain knowledge, working with stakeholders, data skills) in one sentence and move on; more on this in our career changer prep guide.
Explaining gaps, short stints and moves
The walk-through is where every transition gets noticed, so prepare one honest, short sentence for each one, then move forward. Interviewers mostly want to know that the reason makes sense and that you are ready now.
| Situation | Example line |
|---|---|
| Layoff | “My team was cut in a company-wide layoff last spring. Since then I’ve been [what you have done], and I’m looking for a team where I can [goal].” |
| Short stint (under a year) | “The role turned out to be mostly maintenance on a product being sunset, and I wanted to build. I learned [one thing] and moved on quickly.” |
| Career break (caregiving, health, travel, study) | “I took a year off for family reasons. I kept my skills current with [course or project], and I’m ready to be back full-time.” |
| Several quick moves | Group them: “The next two years were contract roles, all on React front ends for e-commerce clients.” |
| Back to school | “I went back for a master’s to go deeper on machine learning, which is why my last project is the recommendation work.” |
Keep each explanation to a sentence or two and never criticize a former employer. For longer versions, see “Why are you leaving your current job?” and our guide to explaining a career gap.
Prepare for the deep dive on every line
The walk-through is often the start of a longer conversation. Anything on the page is fair game, so prepare three layers for each bullet:
- What: the problem and what you built, in one sentence.
- How: the design, the tools, and your part versus the team’s.
- Why: the trade-off you made, what you would change, and how you measured the result.
| If your bullet says… | Expect… |
|---|---|
| “Reduced latency by X%” | “How did you measure it? What was the bottleneck? What did you try first?” |
| “Led the migration to…” | “How many people? What went wrong? How did you roll it out safely?” |
| “Built a service for…” | “Walk me through the architecture. How does it fail?” |
| A technology you list but barely used | A specific question about it. Remove it or be ready. |
If a number is on your resume, know where it came from. If the result was a team effort, say “we” for the outcome and “I” for your part. For the full STAR treatment of your best project, see “Describe a challenging project” for software engineers.
Common mistakes and how to practice
- Reading the bullets aloud. They can read. Add the why and the result.
- Starting too early. High school, your first website at age twelve, a job unrelated to the role: skip them unless they explain something.
- No bridge at the end. Ending on your current job leaves the interviewer to guess why you are talking to them.
- Same version for every company. Change which project you emphasize to match the job description.
- Running past three minutes. If you are not sure, stop and offer to go deeper.
- Memorizing a paragraph. Memorize the outline and the transitions; let the sentences vary.
To practice:
- Write a five-line outline: opener, chapters, bridge. Add one result and one “why” per chapter.
- Time yourself out loud. Cut whatever pushes you past 90 seconds.
- Rehearse the three-layer deep dive for the two projects you named in your hand-off.
- Run a free AI mock interview: CoPilot Interview builds questions from your resume and the job description, reads them aloud, and scores each spoken answer out of 10 with what to fix and a model answer, so you can see whether your walk-through and the follow-ups land. If the resume itself needs work for a specific posting, the Resume Builder tailors it from the job URL.
More behavioral prep, including the stories interviewers ask for after the walk-through, is on our behavioral interview help page.
Practice your walk-through out loud
Paste your resume and the job description, answer an AI interviewer out loud, and get a score out of 10 with what to fix and a model answer for each question. Free for 15 minutes a day, no credit card.
Try a free AI mock interviewFAQ
How long should my answer to "walk me through your resume" be?
Aim for about 60 to 90 seconds for the first telling, and up to two or three minutes only if the interviewer invites a longer version. End by offering to go deeper on the most relevant project.
What is the difference between "walk me through your resume" and "tell me about yourself"?
Tell me about yourself is a short pitch that usually starts with the present. Walk me through your resume follows the order of the document, so the interviewer expects you to cover each relevant role and explain the transitions between them.
Should I start with my education?
If you are a new grad or your degree explains your direction, yes, briefly. If you have several years of experience, mention education in one sentence or skip it and start with your first relevant role.
Do I have to mention every job on my resume?
No. Give the most time to the roles that match this job, group short or unrelated roles into one sentence, and let the interviewer ask about anything you skipped.
How do I explain a gap on my resume?
Give one honest sentence on the reason, one on what you did to stay current, and one on why you are ready now. Then keep going with the walk-through rather than dwelling on it.
Should I go in reverse chronological order?
It works well if you have a long career and your current role is the most relevant. Say so up front, keep the older roles brief, and still end with a bridge to why you want this role.