UX interviews can feel like a test of how well you can memorize answers.

But that’s not really what a strong interview is looking for.

The interviewer wants evidence of your thinking, decisions, collaboration, impact, and reflection. 

Instead of preparing:

“What should I say?”

Prepare by asking:

“What is this question trying to understand about me?”

For example, when asked:

“Why did you choose this solution?”

Don’t simply say that it looked better.

Explain what you knew, what options you considered, what constraints existed, and why you chose that direction. Most importantly, talk about the trade-offs. 

When you’re asked about a difficult project, focus on the problem, why it was difficult, what you did, how you worked with others, and what happened. 

And if you genuinely don’t know?

You can say:

“I don’t know yet, but here’s how I’d find out.”

Then explain your approach—research, users, data, testing assumptions, or asking the team. 

A simple framework can help when you’re stuck:

C → P → D → O → R

Context — What was happening?
Problem — What needed to be solved?
Decision — What did you decide and why?
Outcome — What happened?
Reflection — What would you do differently?

The biggest shift is this:

Don’t prepare perfect answers.

Prepare real stories you can think with. 

UX Crumbs: Bite-sized, practical UX learning for designers.

Join the waitlist: get.uxcrumbs.app