UX Designer mock interview
Answer common UX designer interview questions out loud, from “Tell me about yourself” to research, trade-offs and your portfolio, then get feedback on what you said.
- Free, no account
- Answer by voice or by typing
- About 10 minutes
What they assess
What UX Designer interviews look for
Design process
How you get from a problem to a solution: research, framing, ideas, testing and iteration, and how you adapt the process to the time you have.
User research
Whether your decisions come from evidence about users, and how you gather it when time and budget are tight.
Craft and judgement
The quality of your interaction and visual decisions, and whether you can explain why you made them.
Collaboration
Working with product managers, engineers and other designers: sharing work early, taking critique and designing within constraints.
Impact
Whether your work changed something measurable for users or the business, and how you know.
Questions
8 common UX Designer interview questions, and how to answer them
- Opening
Tell me about yourself.
What they’re looking for: A short summary of the designer you are: the products you’ve worked on, the part of the process you’re strongest in, and one piece of work that made a difference.
How to answer: Start with your current role and the kind of products you design. Give one project and what it changed for users. Finish with why this team and product appeal to you.
- Behavioural
Walk me through a project in your portfolio.
What they’re looking for: A clear story of your process and decisions: the problem, what you learned from users, the options you considered, and the outcome.
How to answer: Set up the problem, the users and your role in a sentence or two. Spend most of the time on the main decisions and what informed them, including what you rejected. End with the result and what you’d change.
- Behavioural
Tell me about a time user research changed your design direction.
What they’re looking for: That you let evidence overrule your assumptions, and can explain what you learned and how.
How to answer: Describe what you originally planned and why. Explain the research you did and what surprised you. Finish with how the design changed and what happened after launch.
- Behavioural
Tell me about a time you disagreed with a product manager or engineer about a design.
What they’re looking for: That you can speak up for users with evidence while respecting business and technical constraints.
How to answer: Say what the disagreement was about and what each side cared about. Explain how you made your case (research, a prototype, a test). End with how it was resolved and what you learned.
- Role-specific
How do you decide what research to do when time is short?
What they’re looking for: Pragmatism: choosing methods that answer the riskiest question quickly, rather than skipping research or insisting on a full study.
How to answer: Start by naming the biggest unknown or risk. Describe quick methods you’d use (a handful of user interviews, informal usability tests, existing analytics or support tickets). Say how you’d share findings so they shape the decision.
- Role-specific
How do you measure whether a design is successful?
What they’re looking for: That you agree success measures before launch and look at both behaviour and user feedback.
How to answer: Explain that you agree goals with the team up front. Give examples of measures: task completion, time on task, conversion, errors, support contacts, satisfaction. Finish with how you’d follow up after launch.
- Role-specific
How do you make sure your designs are accessible?
What they’re looking for: Accessibility as part of normal work: contrast, keyboard use, screen readers, clear language, and testing with real people where possible.
How to answer: Describe what you check during design (contrast, focus states, text size, labels) and the guidelines you follow, such as WCAG. Mention how you work with engineers to get it built correctly and how you test it.
- Motivation
Why do you want to work here?
What they’re looking for: That you’ve used or studied the product, understand its users, and have a view on where design could help.
How to answer: Mention something specific about the product and its users, and one thing you admire or would explore. Connect it to your experience. Keep any critique respectful and framed as curiosity.
More UX Designer interview questions to practise
- Walk me through your background and how you got into UX.Opening
- What kind of design team do you do your best work in?Motivation
- Why are you looking to move on from your current role?Motivation
- Tell me about a time you received tough critique on your work.Behavioural
- Tell me about a time you had to design within serious technical constraints.Behavioural
- Tell me about a design decision that didn’t work. What did you do?Behavioural
- Tell me about a time you had to balance user needs against business goals.Behavioural
- Tell me about a time you worked on a project with no clear brief.Behavioural
- How do you plan and run a usability test?Role-specific
- What’s the difference between UX and UI design, in your view?Role-specific
- How do you present design work to stakeholders who aren’t designers?Role-specific
- How do you work with engineers during handoff and build?Role-specific
- How would you improve the onboarding of an app you use every day?Role-specific
- How do you use a design system, and when would you break from it?Role-specific
- What design work do you admire, and why?Role-specific
- What questions do you have about how design works here?Closing
All 24 questions on this page are in the practice above; each round picks five.
Mistakes to avoid
- Showing polished final screens without explaining the problem, the research or the decisions behind them.
- Saying “we” throughout a portfolio walk-through, so the interviewer can’t tell what you did.
- Running over time on one project and never reaching the outcome.
- Criticising the company’s current product without understanding the constraints behind it.
Questions
About UX Designer interviews
How the practice works and what happens to your answers: about this mock interview.
What is a UX designer interview usually like?
Most include a recruiter or hiring manager call, a portfolio presentation, and conversations with designers, product managers or engineers. Some companies add a design exercise or an app critique. This practice covers the spoken parts: behavioural questions and explaining your process and decisions.
How long should a portfolio walk-through be?
Ask how much time you have and plan to it. Two or three projects told well usually land better than many told quickly, and leave room for questions. Spend most of the time on decisions and outcomes, not on every screen.
What if my best work is under an NDA?
Check what your previous employer allows you to share, and remove or blur anything confidential. You can also talk through the process and decisions without showing final screens. Interviewers are used to this and mainly want to hear how you think.