UX interviews aren’t just about knowing design tools.

They’re about understanding how you think.

An interviewer may ask you to talk about your portfolio, a difficult design problem, research, conflicting feedback, developer collaboration, success metrics, ambiguity, or how you keep learning.

But beneath these questions is a bigger question:

How do you make decisions?

A strong answer doesn’t simply explain what happened.

It explains:

Context → Thinking → Decision → Evidence → Outcome → Learning

Prepare stories, not memorized answers

Instead of writing 10 perfect responses, prepare five adaptable stories:

01 — A difficult problem
What was happening? What made it difficult? What did you decide?

02 — A research insight
What did you need to learn? What evidence changed your thinking?

03 — A disagreement
How did you handle conflicting perspectives?

04 — A design mistake or changed decision
What did you believe initially? What changed your mind?

05 — A measurable outcome
What changed for users or the business?

These stories can become building blocks for many interview questions. 

Make your thinking visible

Don’t just say:

“I redesigned the checkout flow.”

Explain:

What happened → What you considered → Why you chose the direction → What evidence informed it → What changed → What you learned

That’s what turns an answer from a task description into a demonstration of your problem-solving ability.

Don’t try to sound perfect.

Show how you think.