How to walk through your UX portfolio in an interview
A portfolio walkthrough is not a presentation of pretty screens. It is a stress test of your judgement. Interviewers want to know how you framed the problem, what you ignored, who you involved, and whether the work changed anything that mattered. This guide gives you a reliable structure you can adapt for junior through lead-level conversations.
Choose one hero story, not five
Deep beats broad. Pick a case study with clear constraints, real collaborators, and an outcome you can discuss honestly. Have a second project ready if they ask for contrast — for example, a more strategic piece versus a rapid delivery piece — but lead with your strongest.
Open with context in under 90 seconds
Start with the situation, not the solution. Cover organisation, users, goal, constraint, and your role. Example: “A payments team needed to reduce failed applications for self-employed customers. I was the mid UX on a cross-functional squad with a six-week discovery window.” That framing helps the interviewer follow every later decision.
Show process as decision-making, not ceremony
Do not list methods chronologically like a textbook. Pair each method with the question it answered. “We shadowed contact-centre staff because analytics showed drop-off after the eligibility step, and we needed to see where language failed in real conversations.” Methods without rationale sound performative.
- What uncertainty were you reducing?
- What evidence changed the brief?
- Which idea died early, and why was that useful?
- Where did you intentionally stay low fidelity?
Make trade-offs visible
Senior interviewers lean in when you discuss compromise. Accessibility versus launch date. Ideal IA versus legacy navigation. Research desire versus recruiting limits. State the options you considered, the risks, and the call you made. Then name what you monitored afterwards.
Bring evidence of impact
Outcomes can be quantitative or qualitative. Completion rate, support contacts, time-on-task, stakeholder alignment, delivery unblocked, risk reduced — all count if you explain them carefully. If results are incomplete, say what leading indicators you tracked and what you would measure next. Pretending certainty is worse than owning ambiguity.
Anticipate sceptical questions
- Why that research method and not another?
- How do we know eight interviews were enough?
- What would a product analyst challenge in your conclusion?
- How did you handle pushback from stakeholders?
- What part of this was truly yours?
- If this launched poorly, where would you look first?
Practise answering these without defensiveness. A calm, specific reply builds more trust than a polished monologue.
Structure your live walkthrough
Use a simple arc: context → insight → options → decision → artefact → outcome → learning. Keep artefacts sparse. One journey slice, one key screen progression, one snippet of research evidence is usually enough. Narrate transitions. Pause for questions. Watch the interviewer — if they lean in on a detail, go deeper there instead of forcing your rehearsed sequence.
Common walkthrough mistakes
- Spending half the time on team logos and tools.
- Calling everything “user-centred” without evidence.
- Hiding your role inside collective “we” language.
- Showing only final UI and skipping dead ends.
- Overstating impact with unsupported percentages.
- Ignoring accessibility, content, or operational reality.
A rehearsal loop that works
Record yourself once. Note where you ramble. Cut the opening to 90 seconds. Practise one tough interruption in the middle of your story. Then run a mock interview where the interviewer is allowed to be sceptical. Use structured feedback: what worked, what to strengthen, and a revised take. Repeat until your best story feels natural under pressure.