On this page
Questions to practise
Pick one project from your portfolio and tell me about it.
They want to hear how you explain your work and your own decisions, step by step.
Start with the problem, not the screens. Say who the users were, what you did, and what changed. Use 'I' for your own work. Keep it to about two minutes, then stop and let them ask more.
Tell me about a design you improved after research with users.
They want proof that you use research to find problems and make better decisions.
Say what the problem was, what research you did, and what you changed. For example: 'Users could not find the search, so I tested with five users and moved it.' Explain why the research led to that change.
How did you know the new design worked?
They want to see that you check results with users and do not only guess.
Name how you checked it, like a second round of tests, user comments or fewer support questions. Be honest. If you could not measure it, say what you would check next time.
What did users say during your tests?
They want to know if you really listen to users and learn from what they say.
Share one or two real comments or behaviours you noticed. Then explain what you learned and what you changed because of it. Short, specific details help more than general words.
Tell me about a design that tested badly. What did you do next?
They want to see how you handle problems and learn from mistakes, calmly and openly.
Choose a real example. Say what went wrong in the test and what you changed. End with what you learned. Do not blame others. Show that testing helped you find the problem early.
Tell me about a time someone did not like your work.
They want to see how you take feedback and work with others without being defensive.
Give one real example. Say who gave the feedback, what they said, and what you did next. For example: 'A developer said my design was hard to build, so we found a simpler version together.'
How do you work with developers and product managers?
UX designers work in teams. They want to know you share ideas and solve problems together.
Talk about when you share designs, how you ask for early feedback, and how you agree on what to build. One short example of a good team moment makes your answer clear and real.
How do you make sure your designs work for everyone?
They want to know you care about accessibility and include all users, not only some.
Name one or two concrete steps. For example: 'I check colour contrast and test key screens with a screen reader.' You can also mention text size or keyboard use. Say when in your process you do this.
Can you give an example of an accessibility problem you fixed?
They want proof that your accessibility steps happen in real projects, not only in theory.
Describe the problem, like low contrast text or a button that did not work with a keyboard. Say how you found it and what you changed. Keep it short and specific.
Do you have any questions for me?
They want to see your interest in the team, the users and the way they work.
Prepare two or three questions. For example: 'How does the team do user research?' or 'How do designers and developers share feedback here?' Listen to the answer and say thank you.
Let me start with the problem we were trying to solve.
Clara
AI coach
Leo
AI coach
Lines to try
Let me start with the problem we were trying to solve.
We tested it with five users, and here is what we learned.
Because of the research, we changed the design in this way.
That is a fair point. Here is what I did next.
I think about accessibility from the start of a project.
Could you repeat the question, please? I want to answer it well.
Common questions
How long should my answers be?
Aim for about one to two minutes for most answers. Start with the main point, give one clear example, and then stop. If the interviewer wants more detail, they will ask. Short answers with real examples are easier to follow than long ones.
What if my English is not perfect?
That is fine. Speak slowly and use short sentences. It is okay to pause or ask the interviewer to repeat a question. Clear ideas and real examples matter more than perfect grammar. Practising your key stories out loud before the interview can help you feel calmer.
Should I talk about how my designs look?
You can, but do not stop there. Design managers want to hear why you made each decision. Link your choices to the problem, your research and what users said. Then explain what changed and how you checked it. This shows how you think as a designer.