A UX interview can make you feel like you need to memorise everything.

Figma.

Design Thinking.

Research methods.

UX terminology.

Frameworks.

But knowing the vocabulary isn’t enough.

The real value is being able to explain how you think.

Don’t Just Tell Them What You Know

Consider these answers:

“I know Figma.”

“I use Design Thinking.”

“I always put users first.”

These statements tell an interviewer what you know about yourself.

They don’t necessarily show how you approach a problem.

A stronger answer connects:

What happened → What you thought → What you did → What changed. 

That’s where your actual UX thinking becomes visible.

Prepare Stories, Not Scripts

Instead of trying to memorise answers to every possible interview question, prepare stories from your experience.

Your stories can include:

  • A difficult design problem
  • A research decision
  • Conflicting feedback
  • Developer collaboration
  • A failure or mistake
  • An ambiguous problem
  • A difficult trade-off
  • A measurable outcome
  • Something you learned 

Then you can adapt those stories to different questions.

Tell the Story Behind the Portfolio

When an interviewer asks you to walk through your portfolio, don’t narrate every screen.

Talk about:

Problem → Decisions → Trade-offs → Outcome. 

Your portfolio isn’t just a collection of screens.

It’s evidence of how you approach problems.

Show How You Handle Ambiguity

Real UX work rarely starts with perfect clarity.

A strong answer can show a process like:

Clarify → Frame → Make assumptions → Gather evidence → Decide → Iterate.

You don’t need certainty to start making progress. 

Talk About Evidence, Not Just Opinions

When feedback conflicts, don’t make the conversation about:

“Who is right?”

Instead ask:

“What evidence can help us decide?”

And separate:

Opinions ≠ Evidence ≠ Constraints. 

That distinction demonstrates a much stronger approach to design decisions.

Prepare for Collaboration and Impact

If you’re asked how you work with developers, don’t make collaboration sound like something that starts at handoff.

Talk about:

Feasibility → Trade-offs → Communication → Iteration.

And when discussing success, don’t stop at:

“The design looked better.”

Talk about:

  • What changed for users?
  • What changed for the business?
  • What evidence would demonstrate success? 

Use Frameworks to Structure Your Thinking

For experience-based questions, the PDF recommends STAR:

Situation → Task → Action → Result

For situational questions, it introduces METEOR:

Muse → Enquire → Theorise → Endeavor → Outcome → Recap. 

These aren’t scripts.

They’re structures that help you communicate your thinking clearly.

The Most Important Shift

The goal isn’t to memorise answers.

Memorise the stories.
Practise the thinking.

That’s the mindset behind the entire cheat sheet.

Before your next interview, prepare stories that cover problems, research, conflict, collaboration, failure, ambiguity, trade-offs, impact, and learning.

Because a UX interview gets easier when you’re prepared to explain how you think, not just what you know.