Mock Interview Copilot Interview questions by role
UX designer interview questions
UX designer interviews centre on your portfolio: interviewers want to see how you understand a problem, what research you did, the decisions you made and why, and what happened after launch. Expect a case study presentation, questions on research and testing, handling feedback, working with product and engineering, and often a design exercise.
How the interview usually runs
The process usually runs from a recruiter screen to a portfolio review with a design manager, then a presentation of one or two case studies to a panel, and sometimes a whiteboard or take-home exercise. Panels often include a product manager and an engineer, who will ask very different questions from the designers.
The most common feedback after a failed design interview is that the candidate showed final screens but not the thinking. Interviewers want the messy middle: the options you rejected, what the research changed, and the constraints you designed around.
Common questions and what the interviewer is checking
Walk me through a project in your portfolio.
What they are checking: Your process and reasoning: the problem, the users, research, options explored, the decision and its outcome, and what your personal role was.
How did you know your design worked?
What they are checking: Evidence after launch or from testing: usability findings, behaviour changes, support tickets, metrics, and honesty when the results were mixed.
Tell me about a time research changed your design.
What they are checking: That you genuinely listen to users and are willing to throw work away.
How do you handle feedback you disagree with?
What they are checking: Separating taste from evidence, asking what problem the feedback is pointing at, and testing when opinions conflict.
How do you work with engineers when a design is hard to build?
What they are checking: Early collaboration, understanding constraints, and finding a simpler version that keeps the user benefit.
How do you design for accessibility?
What they are checking: Contrast, type sizes, focus states, clear labels, not relying on colour alone, and checking with real assistive technology users where possible.
What would you do with no time or budget for research?
What they are checking: Pragmatism: talking to support teams, reviewing analytics and recordings, quick guerrilla tests, and stating assumptions clearly.
Critique an app you use every day.
What they are checking: Structured critique tied to user goals rather than visual preference, and a realistic improvement.
How do you balance user needs with business goals?
What they are checking: That you see them as connected, and can argue for users with business language.
How to structure a strong answer
Tell each case study as a story with a clear problem and a clear decision. Spend more time on why than on what, and name the trade-offs. Keep it short enough that the panel has time to ask questions.
- The problem, the users and the business goal.
- What you learned from research and data.
- The options, the decision and the trade-off.
- The outcome and what you would change.
Example answer
Tell me about a time research changed your design.
We were redesigning the onboarding for a budgeting app, and the team assumed people dropped off because the form was too long. My first designs shortened it to a few steps.
Before building it, I ran usability sessions with five recent sign-ups. The length was not the problem. People stopped at the step asking them to connect their bank, because they did not yet trust the app. I reworked the flow so people could explore with sample data first and connect their bank later, with a plain explanation of what access the app gets. Completion of onboarding went up after launch, and the bank step moved from the biggest drop-off to one of the smallest. It taught me to test the assumption before polishing the solution.
Mistakes to avoid
- Showing beautiful final screens with no explanation of the problem or process.
- Saying "we" throughout so the panel cannot tell what you did.
- Presenting a case study for so long there is no time for questions.
- Getting defensive when the panel critiques your work.
- Having no evidence of whether the design worked after launch.
Frequently asked questions
What questions are asked in a UX designer interview?
Expect a portfolio walkthrough, questions about research and testing, how you measured success, handling feedback, working with engineers and product managers, accessibility, and often a design exercise or critique.
How long should a UX portfolio presentation be?
Follow the time the company gives you, and leave room for questions. One or two case studies told well are better than five rushed ones.
How do I talk about a project with no measurable results?
Use what evidence you have: usability test findings, qualitative feedback, changes in support requests, and be honest about what you would measure if you did it again.
What is the difference between UX and UI interview questions?
UX questions focus on research, problem framing and decisions; UI questions go deeper into visual design, systems and detail. Many roles combine both, so prepare for each.