Design

UX Designer mock interview

Expect to defend interaction decisions against a plausible-sounding alternative the interviewer invents on the spot. Holding a position with user evidence, or updating cleanly, both score.

Design loops centre on the portfolio review, and the work is not what is being assessed — the reasoning behind it is. Expect to justify decisions you made years ago to someone who will ask what you rejected.

Practising this out loud matters more here than almost anywhere, because a portfolio you know intimately is very easy to narrate badly under time pressure.

The rounds you can practise

Each round is run by the interviewer built for it, with its own scoring axes — not one generic interviewer asked to change subject.

Customer insight, prioritization, product judgment, and execution trade-offs.

Scored on User-first framing · Prioritization & execution · Product judgment & influence

Customer insight, prioritization, product judgment, and execution trade-offs.

Scored on User-first framing · Prioritization & execution · Product judgment & influence

Customer insight, prioritization, product judgment, and execution trade-offs.

Scored on User-first framing · Prioritization & execution · Product judgment & influence

UX Designer interview questions

Six you can expect, in the register interviewers actually use. Answer them out loud before you read the next section — reading a question and answering one are different skills, and only the second is marked.

  1. Defend this interaction against the alternative I am about to suggest.
  2. How do you handle a pattern users are familiar with but that tests badly?
  3. When do you break a convention?
  4. How do you design for the error state?
  5. How do you work with an engineer who says it is not feasible?
  6. What accessibility decision changed your design?

The same question, answered badly and well

The gap between these two is most of your score, and it is easier to see than to be told.

Defend this interaction against the alternative I am about to suggest.

What loses marks

Either abandoning your design immediately or defending it on personal preference. Both fail — the first shows no conviction, the second shows no evidence.

What scores

Take the alternative seriously and name what it is genuinely better at, then give the user evidence for your choice, then say what would change your mind. Holding a position with evidence and updating cleanly both score; only defensiveness fails.

Why UX Designer candidates get cut

The post-mortem nobody sends you. These are specific to this loop rather than general interview advice.

Preference presented as principle, with no user evidence behind it.
Folding on the first challenge, which reads as work you did not reason your way to.
Error and empty states treated as an afterthought when they are most of real usage.

Start with a general round

For UX Designer, a general round runs with Leila customer insight, prioritization, product judgment, and execution trade-offs. It is the fastest way to find out which round you actually need to work on. The first session is free.

Practise a UX Designer interview →

Question guides

Before you practise, it is worth reading how the common rounds are marked: tell me about yourself, behavioral questions and STAR, and system design.

Similar roles

All roles