UX Designer Interview Questions and Answers (With What Hiring Managers Actually Want)

UX interviews have a quiet test running underneath the obvious one. They are checking whether you can defend a design decision without getting defensive. The candidates who get hired are the ones who can talk about a user's problem and a business constraint in the same breath.

Here are the questions that come up most often, with answers that work and what interviewers are really listening for.

The questions that decide the hire

"Walk me through a project in your portfolio"

This is the question you will be asked, so prepare for it. Pick one project and tell it as a story with five beats: the problem, the constraint, the process, the solution, the result.

"The checkout was losing people at the payment step. The constraint was that we couldn't change the payment provider. I ran five user sessions and found the friction was the address form, not the payment. I consolidated it into one field with autocomplete. Drop-off at that step fell from 40% to 22%."

That answer names the problem, the constraint, the evidence, and a number. It sounds like a designer who has shipped.

"How do you decide what to test?"

Interviewers want to see that you don't test everything. "I test the things that are expensive to get wrong. If a button label is cheap to change later, I ship it and watch the data. If a flow restructure is hard to reverse, I test it with five users first. I'd rather spend a day testing than a month building the wrong thing."

"Tell me about a time you disagreed with a developer"

This is the collaboration test. The wrong answer is that you always agree. The right answer shows you can negotiate a trade-off. "He wanted to ship the simpler version, I wanted the version that solved the edge case. We looked at how often the edge case actually happened, it was about 8% of users, and agreed to ship the simple version first with the edge case in the next sprint. The thing I learned is that 'later' has to be a date, not a hope."

"How do you handle feedback that your design is wrong?"

They are listening for whether you take it personally. "I ask what they're seeing that I'm not. Most of the time the feedback is about a constraint I didn't know about, like a technical limit or a brand rule. Once I know that, the redesign is usually quick. If I still disagree, I test it and let the data decide."

Questions about method

"Walk me through your research process"

They want to see you start with the question, not the method. "I start with the decision I'm trying to make. If the decision is whether to ship, I test with five users. If the decision is which of three directions, I test with more. I write the hypothesis before the script, because otherwise you end up testing whatever the interview turns into."

"How do you prioritise what to design next?"

Name a framework, but use it. "I rank by user impact and effort. High impact, low effort goes first. The trap is only doing the quick wins, so I keep one strategic piece on the list at all times."

Questions to ask them

• How early does design get involved in a project here?
• What is the relationship between design and research?
• Can you tell me about a recent decision design drove that you're proud of?

What to avoid

• Don't describe a project without naming a result, even a rough one.
• Don't claim a method you can't talk through with an example.
• Don't treat the portfolio review as a slideshow. Make it a conversation.

Before you go in

Pick one project and rehearse the five beat version out loud. If you can't get through it in two minutes, it's too long. The interviewer will ask follow-ups, so leave room.

Want to practise with feedback? Try the mock interview tool, and check our UX designer CV examples so your portfolio and your CV tell the same story.