UX Designer mock interview

What the loop usually looks like

1. Portfolio

   45 min

   One project from problem to shipped UI.

2. Whiteboard or critique

   45 min

   Improve a flow, or critique an existing one.

3. Collaboration

   30 min

   Working with product and engineering when the design cannot be built as drawn.

What interviewers score

• Problem framing
• Evidence
• Trade-offs
• Collaboration

10 ux designer interview questions and model answers

1. Domain

   1. How do you decide what to learn before you draw?

   What they are testing: Research judgment.

   I write the decision the design has to support. If I cannot make it without knowing how people do the task today, I watch or interview a few of them. I do not run a large study to decorate a decision that is already made.

2. Behavioral

   2. Tell me about a design that research changed.

   What they are testing: Evidence over taste.

   I expected users to want more filters. Three of five could not find the existing search. We fixed search and delayed filters. I kept the recording clip in the review so the change was not just my opinion.

3. Situational

   3. Engineering says your flow is a month of work and you have a week. What do you cut?

   What they are testing: Scope.

   I keep the path that completes the task, including the error state, and I cut secondary settings and animation. I mark what we did not solve so it is not mistaken for a finished design.

4. Domain

   4. How do you present a design critique without defending every pixel?

   What they are testing: Collaboration.

   I ask what problem the reviewer thinks the screen fails. If they are right, I change it. If they are asking for personal taste, I say which user goal I am protecting. I do not narrate every padding choice.

5. Behavioral

   5. Describe a time you shipped something you thought was worse than your first concept.

   What they are testing: Maturity.

   The first concept needed data we did not have. The shipped version used a field that already existed and solved the urgent case. I wrote down what the better version needed so it was a sequence, not a loss.

6. Technical

   6. How do you design for empty, loading, and error states?

   What they are testing: Completeness.

   They are part of the flow, not a follow-up ticket. I specify what the user can do in each state. A happy path alone is not ready for engineering.

7. Situational

   7. A stakeholder wants the homepage to promote six things. How do you respond?

   What they are testing: Prioritization.

   I ask which action is the job of the page. The other five can be reached, but they cannot all be the primary action. I show one hierarchy and the metric that would change my mind.

8. Behavioral

   8. Tell me about accessibility feedback you acted on.

   What they are testing: Inclusive design.

   A keyboard user could not reach a custom control. I replaced it with a native control and checked the flow without a mouse. I added that check to the design checklist so it was not a one-time fix.

9. Domain

   9. How do you work with a design system that does not have the component you want?

   What they are testing: Systems thinking.

   I try to compose it from what exists. If I cannot, I propose a component with the states and the reason the existing ones fail. I do not paste a one-off that the next designer cannot find.

10. Situational

    10. You disagree with product on the user. How do you settle it?

    What they are testing: Shared evidence.

    I write both users and the task each has. We pick the primary user for this release in the open. If we cannot, we need one more conversation with a real user, not another opinion meeting.

Frequently asked questions

Keep practicing

• Product Manager mock interview
• Frontend Developer mock interview
• Project Manager mock interview
• Marketing Manager mock interview
• Behavioral interview practice
• How AI mock interviews work
• Case interview practice
• All role mock interviews