Skip to main content
Career insights

How to Present Your UX Portfolio in an Interview (Even With No Experience)

5 min read

The portfolio review is 30 to 45 minutes of you presenting your work to the hiring team. Understanding what they are actually evaluating is the most important thing you can do before you walk in. They are not looking at how polished your screens are. They are watching how you think — how you made decisions under constraints, what tradeoffs you navigated, and whether you can explain your reasoning clearly under pressure.

The case study structure that works

Every strong portfolio presentation follows the same arc: Problem, Research, Insights, Design decisions, Final solution, Results or learnings. Start by explaining the problem you were solving and for whom. Move into the research you did and what you learned. Explain the insight that shaped your design direction. Walk through the key design decisions — not all of them, just the ones with the most interesting tradeoffs. Show the final solution. End with what happened or what you would do with more time.

How long to spend on each section

A 30-minute portfolio review does not mean 30 minutes of you talking. Pace yourself: spend roughly 2 minutes on the problem, 3 minutes on research, 5 minutes on process and key decisions, 5 minutes on the solution, and 2 minutes on outcome or learnings. That leaves room for questions, which is where hiring managers often form their strongest impressions.

The question you will always get

Every interviewer will ask some version of "what would you do differently?" The trap is either undermining your own work ("honestly the whole thing could be better") or being defensive ("I think it was pretty solid given the constraints"). The right answer is specific, grounded, and forward-looking: name one real thing you would change, explain what you know now that you did not know then, and connect it to what you would do next. That answer shows self-awareness without undermining your credibility.

Three case study mistakes to avoid

Starting with the solution rather than the problem is the most common mistake — it signals you are thinking about deliverables rather than users. Not explaining why you made each decision is the second: showing the final screens without the reasoning is just a visual tour, not a demonstration of design thinking. The third is claiming sole credit for work that was clearly a team effort. Interviewers know design is collaborative. Being specific about your contribution — "I led the research phase and designed the checkout flow, while the visual design was a collaboration with the brand team" — is more credible than presenting everything as if you did it alone.

For career changers: lead with your competitive advantage

If you are transitioning from another field, identify the project in your portfolio where your prior domain expertise made the design meaningfully better. A former nurse who redesigned a patient intake flow understands the real friction in a way a new grad cannot. A former teacher who improved an e-learning product knows what good learning design actually looks like. Lead with that project. Your domain knowledge is your competitive advantage — make sure your portfolio presentation makes it visible.

Keep learning

Ready to make the move?

Explore structured learning paths for every non-coding tech role — free to start, no signup required.

Browse all roles
← All articles