What this round tests
The portfolio walkthrough is one of the most weighted rounds in the modern UX interview pipeline. The interviewer or panel is testing four things simultaneously. Can the candidate hold the room? Can they walk through their thinking out loud as competently as they wrote about it? Can they handle pushback on specific decisions? Do they sound like someone the team would want to work with day to day?
The round usually runs 60 to 90 minutes for senior roles; 45 to 60 for mid-level. The candidate is expected to present one or two case studies in depth, fielding questions throughout. The full pipeline view of where this round sits is in interview preparation guide. The companion piece on deck preparation specifically is interview presentation guide; this article focuses on the walkthrough delivery itself.
Presentation structure
How to spend the time
- Opening (3–5 min). Candidate introduction (60 seconds), what you'll cover (60 seconds), hook into the first case study.
- Case study 1 — strongest work (20–25 min). Context, problem framing, two or three significant decisions, outcomes, reflection. Field questions throughout.
- Case study 2 — supporting work (15–20 min). A second case study showing a different muscle. Shorter than the first; the depth signal has already been established.
- Q&A (15–20 min). Open questions from the panel about either case study, broader portfolio, or working approach.
- Candidate questions (5–10 min). Two or three substantive questions for the panel.
Adjust proportions for 30 and 45 minute walkthroughs. The Q&A allocation is the most commonly under-budgeted; candidates who plan for 5 minutes of Q&A often lose the round because the panel wanted 25.
Storytelling for case studies
Walking through a case study verbally is different from reading it on a page. The reader can re-scan a paragraph; the listener can't. The structure that works in writing — hero summary, context, decisions, outcomes, reflection — still works verbally, but each section needs different pacing.
The opening 90 seconds of each case study are disproportionately important. Strong opens: "I'm going to walk you through the international transfer onboarding redesign at Monzo, because it was the project where I had to navigate the most stakeholder disagreement and the project I learned the most from. The problem was [one sentence]. The outcome was [one sentence]. I'll cover the three decisions I made under most constraint." That structure earns the next 20 minutes of attention.
The decisions section is where the panel will spend the most time. Plan for each significant decision to take 5 to 8 minutes including likely questions. Two or three decisions per case study is the right depth; four or five becomes a list rather than a story.
The reflection at the end of each case study should be specific and short. Two minutes maximum. The strongest reflections name a pattern the candidate is working to change, which gives the panel something concrete to follow up on in Q&A.
Slide design
Slides for the walkthrough should support the candidate's voice rather than compete with it. Three patterns work consistently.
One idea per slide. Each slide carries one specific decision, one specific screen, or one specific point. Slides with bullet lists spanning the whole screen tend to be read silently by the panel while the candidate speaks; the dual-track loses both signals.
Real product screenshots over mockups. Where shipped work can be shown, show it. Real screens read as real product; mockups read as portfolio polish. The exception is NDA-blocked work, where redacted screens with explanatory annotation beat abstract mockups.
Decision slides. The most predictive slide pattern in strong walkthroughs: a single slide showing the decision the candidate made, the alternative considered, and the trade-off accepted. Three bullets, no more. The panel engagement increases visibly on these slides.
Tooling: Gamma has become the most common starting point for interview decks in 2026. The pattern that works: outline the deck in prose first, generate the structured deck with Gamma, then refine the slides that need precise control. A deck that would take 8 to 12 hours to build manually can usually be built in 2 to 3 hours this way, with comparable or better visual quality. Particularly useful for candidates running two or three parallel interview processes who need to compress preparation time.
Time management
Time management under interruption is the single most diagnostic delivery skill in the walkthrough round. Strong candidates manage the clock visibly — naming when they're moving sections, checking time without anxiety, finishing each case study 2 to 3 minutes early to absorb questions.
The framing that works: assume the panel will interrupt every 2 to 3 minutes. Plan accordingly. If you scripted 25 minutes of content for the first case study, expect to deliver 18 minutes of script with 7 minutes of interruptions. Candidates who plan 30 minutes of script and try to deliver all of it usually run 10 minutes over and lose the round.
The recovery move when running long: skip the second case study's depth section, summarise the case study in 90 seconds, and protect Q&A time. Panels remember candidates who managed time gracefully more than they remember candidates who delivered every planned slide.
Handling questions
The pattern that works: acknowledge the question specifically ("you're asking about why I chose X over Y"), state the assumption you were proceeding on ("I assumed Z, which informed the choice"), engage with the alternative being implied ("if Z is wrong, you're right that Y would be the stronger choice"), and either revise or hold ("I think Z is reasonable in this brief, so I'd hold the choice", or "I think you've identified a stronger framing, and I'd revise").
The collapse-vs-defend balance is the most diagnostic moment in the round. Candidates who collapse — "you're right, I shouldn't have done it that way" — lose. Candidates who defend without engagement — "no, X is definitely correct" — also lose. The middle path of engaged judgement is what converts.
Specific moves that work: "That's the right question to push on, and I'd say"; "I don't know the answer; my best guess is X, and what I'd do to validate is Y"; "I think there's a stronger framing than the one I used — let me think about that in real time". Each communicates judgement under pressure.
The walkthrough rounds I remember as a hiring panellist were the ones where the candidate disagreed with us politely and then defended their reasoning. Almost every candidate who did that got an offer. The candidates who agreed with whatever we pushed back on lost the round in that exchange, regardless of the strength of their slides.
Executive audiences
When the panel includes executive stakeholders (VP design, head of product, CTO), the walkthrough takes a slightly different shape. Executives are testing strategic thinking and senior-room presence more than craft.
Three adjustments work for executive audiences. Lead each case study with the business context before the design context — the executive needs to know what the project was for the business, not just for the user. Spend more time on outcomes and less on process. Be ready for "if you had your time again" questions which test honest reflection.
The pace is usually slightly slower. Executives ask fewer but more strategic questions. Candidates who try to fit the same volume of content into an executive walkthrough as into a peer walkthrough usually finish their script with the executive looking bored. Less content, more depth, more business framing.
Stakeholder audiences
Stakeholder panels (PMs, engineering leads, research leads, content leads) test cross-functional collaboration. The walkthrough should surface evidence of working across disciplines: how the candidate brought engineering into a design decision, how they translated research findings into a recommendation, how they handled a content disagreement.
The framing that works: name the cross-functional moment explicitly in each case study. "The engineering lead pushed back on the API call we needed; here's how we navigated that." The panel reads this as confirmation the candidate operates the way they operate — across functions rather than within design alone.
Remote interviews
Most UX interviews in 2026 are remote or hybrid. Remote walkthroughs add three constraints: latency on screen-sharing, harder reading of panel reactions, and reduced informal rapport-building before the round.
Three remote-specific moves work. Open with a 30-second pause for camera/audio check rather than launching straight in. Test screen-sharing of the actual deck before the call rather than assuming it'll work. Plan slightly slower pacing throughout — remote audiences process more slowly than in-room audiences, and the latency adds real seconds to every interaction.
For the full pipeline view, see interview preparation guide. For deck-specific preparation, see interview presentation guide. For the broader case study structure that underpins the walkthrough, see case study examples, case study template, and case study before and after. For portfolio-side preparation, see portfolio examples, junior or senior level references. For the salary and offer stages that follow, see salary negotiation guide and UX designer salary UK. For broader career context, see how to get your first UX job and how to become a UX designer in 2026.
Frequently asked questions
How long is a UX portfolio presentation in an interview?
60 to 90 minutes for senior roles; 45 to 60 for mid-level. Plan 25–35% of the time for Q&A.
How many slides should a UX portfolio presentation have?
12 to 18 slides for 30 minutes; 20 to 30 for 60 minutes. Lower density outperforms dense slides for portfolio narratives.
How should I handle questions during a UX portfolio presentation?
Acknowledge specifically, restate your assumption, engage with the alternative, either revise or hold with reasoning. Treat interruptions as engagement, not disruption.