GhostpilotHome · Interview questions · UX Designer
UX Designer interview questions
UX interviews revolve around your portfolio. Interviewers want your reasoning: what you learned, what you rejected, and what changed for users.
What interviewers look for
- Process. Research, options and iteration, not just final screens.
- Reasoning. Why you made a decision.
- Collaboration. Working with product and engineering.
How the interview usually runs
- Recruiter call.
- Portfolio presentation.
- Design exercise.
- Team interviews.
Stages vary by company, so ask the recruiter what to expect before you start preparing.
8 UX Designer interview questions, and how to answer them
1. Walk me through a project in your portfolio.
What they want to see: Storytelling and process.
How to answer: Cover the problem, your role, research, options, decision and result.
2. How do you decide what research to do?
What they want to see: Method choice.
How to answer: Choose by the question, time and risk.
3. Tell me about a design that failed in testing.
What they want to see: Learning.
How to answer: Show what users did and what you changed.
4. How do you handle feedback you disagree with?
What they want to see: Collaboration.
How to answer: Ask what problem it solves, and test options where you can.
5. How do you measure design success?
What they want to see: Impact.
How to answer: Agree metrics up front, such as task success.
6. Redesign the checkout of an app you use.
What they want to see: Live thinking.
How to answer: Clarify the goal, find the friction and sketch a focused change.
7. How do you design for accessibility?
What they want to see: Inclusive design.
How to answer: Cover contrast, focus order, labels and testing.
8. How do you work with engineers?
What they want to see: Delivery.
How to answer: Involve them early, and agree what happens in edge cases.
A sample answer
Tell me about a design that failed in testing.
I designed a single-page signup to reduce steps. In testing, five of eight people stalled at the long form, unsure why we needed the details. I split it into three short steps with a reason next to each field. Completion rose noticeably in the next test, and we shipped that version.
A made-up example to show the structure. Use your own experience and real numbers.Common mistakes
- Showing polished screens with no process.
- Saying "users want" without evidence.
- Talking for too long about one project.
- No measured outcome.
Practise this out loud
Run a mock interview for an UX Designer role. Questions change every time, you answer by voice or typing, and each answer gets a score with feedback.
Frequently asked questions
How many portfolio projects should I present?
Two or three in depth is usually better than many. Ask how long you have, and practise to that time.
Do UX designers need to code?
Usually not, but understanding what's hard to build helps you work with engineers.