How to Prepare Your UX Case Study for a Design Interview

The real problem

A case study is not only a portfolio page. It is also interview preparation. When a reviewer opens your case study, they start forming questions. A strong case study anticipates those questions and gives you a clearer way to talk through your work.

This becomes a problem in the interview room specifically. When the reasoning is not on the page, the interviewer has to probe for it. That puts you in a reactive position, answering questions about gaps rather than guiding the conversation through your thinking. A case study that makes the reasoning visible gives you a cleaner path through the presentation.

What to focus on instead

The interview version of your case study has a different job than the portfolio version. The portfolio needs to earn attention in the first 30 seconds. The interview version needs to hold a 15-minute conversation. For that to work, you need to know exactly which decisions you would defend under pressure, and which trade-offs you can explain clearly out loud.

Key principles:

• Prepare a two-minute summary of the project.
• Know your role and contribution clearly.
• Explain one important trade-off.
• Prepare one decision you would defend.
• Prepare one thing you would improve today.

A practical structure

Use this simple flow:

1. Context: Can you describe the product and team in two sentences?
2. Problem: Can you state the core problem without jargon?
3. Role: Can you explain your specific contribution without defaulting to “we”?
4. Decision: Which decisions are you prepared to defend in detail?
5. Reasoning: Can you explain the evidence or trade-off behind each key choice?
6. Outcome: What changed, and are you confident enough in that claim to be challenged on it?

This doubles as an interview outline. If you can answer all six points out loud, you have a stable scaffold for the presentation. The questions that come after will almost always land on one of these six points. Knowing where in the framework they land helps you answer without losing the thread.

Example framing

Weak framing:

I redesigned the flow and improved the user experience.

Stronger framing:

I focused on the onboarding step where users were unsure what to do next. Instead of adding more explanation, I simplified the sequence and made the next action more visible. This helped the team align around a clearer first-use experience.

The stronger framing holds up when an interviewer asks a follow-up. If you can name the specific decision and the reasoning behind it, the conversation stays grounded. If you have only a general outcome claim to offer, any follow-up question will surface the gap.

What to avoid

• Do not turn the case study into a gallery of screens.
• Do not hide your role behind vague “we” language.
• Do not overclaim impact if you do not have evidence.
• Do not describe every step equally; highlight the decisions that mattered.
• Do not copy another designer’s case study structure without adapting it to your own project.

Final thought

The case study that works in a design interview is the one you can actually talk through. If you can explain the situation, describe the decision, name the trade-off, and say what changed, that case study will carry the conversation. The portfolio page is just the entry point.

More case study guides

• what hiring managers look for in UX case studies
• writing a UX case study without metrics
• showing your contribution in a team project