Presenting a Design Portfolio Review in an Interview
For product and UX designers, the portfolio review is usually the decisive round: 45 to 60 minutes presenting one or two projects to a panel. It's evaluated less on how polished the visuals are and more on how you think.
Pick fewer projects, go deeper
Two projects presented properly beat five skimmed ones. Choose one where you led and made hard trade-offs, and one that shows range (different platform, user, or constraint). A project that shipped and was measured is worth more than a beautiful concept.
A structure that works
- Context (2 min): the product, the users, your role and the team size. Be precise about what you did.
- Problem (3 min): what was broken, how you knew (data, research, support tickets), and what success would look like.
- Process (10 min): the two or three key decisions, the options you considered, and why you chose one. Show the messy middle: rejected directions are evidence of judgment.
- Outcome (3 min): what shipped, the measured result, and what you'd change now.
Handle critique like a collaborator
Panels will challenge decisions. That's the test. "Good question: we considered that, and here's why we didn't" is ideal when true. When it isn't, "I hadn't thought about that; here's how I'd evaluate it" is a strong answer. Defensiveness is the one clearly bad response.
Practical details
- Prepare a slide version even if you have a case-study site; it lets you control pacing.
- Blur or anonymise confidential work, and say that you did.
- Rehearse to 70% of the time slot so there's room for questions.
- End with one slide of open questions you'd explore next.
Disclosure: I contribute to Linkjob AI, which makes AI interview prep tools. Not specific to any product.