UX Designer Interview Questions and How to Answer Them

Designers often expect to be asked about tools and instead spend the hour explaining decisions. This section lists the process questions that appear in most UX loops and what each is really testing. The short version: every question asks how you know your design is right.

• "Walk me through your design process." They want a real, adaptable process, not a textbook diagram of five stages applied to every project.
• "How do you decide what research to do?" Explain choosing between interviews, usability tests, surveys, and analytics based on the question and the deadline.
• "Tell me about a time research changed your design." Name what you believed, what you learned, and what you changed.
• "How do you measure whether a design worked?" Tie the design to a behaviour metric such as task completion or drop-off, not to stakeholder approval.
• "How do you design with no research budget?" Show scrappy methods: hallway tests, support tickets, and existing analytics.

You present two or three projects over a shared screen and the panel interrupts with questions. Pick projects that show range, and structure each one as problem, constraints, your role, key decisions, outcome, and what you would change.

A product designer interviewing at a fintech company might present an onboarding redesign. The strongest version names the drop-off the team was chasing, the two concepts that were tested, why the simpler one won, and the constraint from engineering that shaped the final flow. Interviewers remember the decision, not the mockup.

Expect follow-ups such as "What did the engineers push back on?" and "What would you do differently now?" Have honest answers ready.

In a whiteboard or app challenge you get a vague brief, for example "design a way for commuters to split ride costs". Spend the first part asking questions: who the user is, what the constraints are, and what success looks like. Then sketch flows before screens, and state your assumptions out loud.

A design critique asks you to review an existing product. Structure it: the user goal, what works, what creates friction, and one change you would test first. Avoid pure visual opinions without a user reason.

Take-home challenges are also common for UX roles; the interview types hub covers the format.

Rehearse the walkthrough out loud with a timer, because running long is the most common failure. Then practise the behavioural questions: disagreement with a product manager, a design that shipped against your recommendation, and a project that failed. Spoken practice with an AI interviewer that asks follow-ups is on the mock interview page.

On live video calls, SubcueAI can surface structured points from what the interviewer asks. It has limits: while you share your screen for a walkthrough, anything visible on that screen is visible to the panel, and recorded or proctored sessions are out of scope. Your resume should match the projects you present; the resume builder helps keep the two aligned.