What UX designer interviews actually test
UX interviews are as much about your process and communication as your design output. Most interviewers care less about whether your Figma files are beautiful and more about whether you can think clearly about user problems and work effectively with others.
The four things UX interviews consistently evaluate:
1. Design process — How do you go from a vague problem to a concrete solution? Do you do user research before designing? How do you handle discovery, ideation, testing, and iteration?
2. Portfolio presentation — Can you articulate the "why" behind your design decisions? The best portfolio walkthroughs explain the constraints you were working under, the options you considered, the trade-offs you made, and what you learned.
3. Cross-functional collaboration — UX designers work with PMs, engineers, researchers, and executives. Interviewers probe for how you handle pushback on your designs, how you work within technical constraints, and how you influence decisions without authority.
4. Communication and persuasion — Design is nothing if it doesn't get built. Can you build alignment, present findings from user research, and advocate for users when under commercial pressure?
Typical interview format:
- Recruiter screen: background and fit
- Portfolio review: walkthrough of 2–3 case studies
- Design exercise: a whiteboard or take-home challenge
- Cross-functional stakeholder interviews
- Sometimes: a presentation to the full team
Portfolio and process interview questions
"Walk me through a project you're proud of."
Don't lead with what it looks like — lead with the problem. Start with: what was the user problem, who were the users, what constraints were you working under? Then describe your process: what research you did, what you found, what ideas you explored, how you tested and iterated. End with: what shipped, what the impact was, and what you would do differently.
"How do you approach user research for a new feature?"
Show range: generative research (understanding the problem space — interviews, diary studies, field observation) versus evaluative research (testing solutions — usability tests, A/B tests). Explain how you recruit participants, how you analyse qualitative findings, and how you translate research into design decisions. Most importantly: show that you do research before designing, not to validate a design you've already committed to.
"Tell me about a time your design was pushed back on by engineers or a PM."
What they're evaluating: maturity and collaboration. The right answer shows that you understood the constraint (technical, timeline, or strategic), explored whether there was a middle ground, advocated for the user experience impact of the trade-off, and ultimately shipped something rather than holding out for perfection.
"How do you handle designing for a problem where you don't have access to users?"
Interviewers know research isn't always possible. Show you can use: heuristic evaluation, expert review, analytics data, customer support logs, and competitor analysis as proxies. And that you document your assumptions explicitly when you don't have direct user input.
"How do you decide when a design is ready to hand off to engineering?"
Key signals: core user flows are validated, edge cases are documented, component states are specified, and the engineer has reviewed for feasibility. "Ready" is a conversation, not a gate you pass alone.
Behavioural and stakeholder UX interview questions
"Tell me about a time you advocated for the user against business pressure."
This is a test of your values and your ability to influence. Show: how you grounded your advocacy in user data (not personal preference), how you communicated the risk of the business decision to the user experience, and what the outcome was — even if you lost the argument, show you made a principled, evidence-based case.
"How do you work with a PM who sets requirements before involving design?"
A common situation. Show that you don't just execute orders — you find ways to inject discovery earlier in the process. Tactics: regular sync to understand what's on the roadmap before it's finalised, sharing research that reframes the problem, and building trust by showing that early design involvement saves time downstream.
"Describe a design failure. What happened and what did you learn?"
The best answer is specific, honest, and shows growth. Vague answers ("I once made a design that didn't work as expected") are unconvincing. Tell the story of what went wrong, what you would do differently, and how it changed your process.
"How do you communicate with engineers who say your design is not buildable?"
First, understand: is it not buildable at all, or not buildable in the current sprint? Then explore: is there a technical constraint I don't understand, or a simpler design that achieves the same goal? Show curiosity and collaboration, not a fight for your original design.
"What would you do on your first 30 days in this role?"
Interviewers love this question for designers. Strong answer: spend time understanding the product (use it extensively), talk to users if possible, review existing design decisions and documentation, understand the engineering and product process, identify one quick win and one longer-term gap.
Questions to ask — and how to prepare with LoopCV
Questions to ask your interviewer:
- How is design involved in the discovery process — do designers participate in roadmap planning?
- What's the ratio of design to engineering on this team?
- How does the team handle the balance between design consistency and feature velocity?
- What UX research capability does the team have — dedicated researchers, or is it designer-led?
- What's one design decision the team made recently that you're not fully happy with?
How to prepare:
Prepare 3 strong case studies. For each: have a 5-minute version and a 15-minute version. Practise leading with the user problem, not the visual output.
For the design exercise: practise narrating your thinking out loud as you work. Interviewers don't just want to see the result — they want to see your process in real time.
Use LoopCV's interview preparation tool to practise your portfolio walkthrough and typical UX scenario questions before you're in front of a real panel.
On the applications side: LoopCV automatically applies to matching UX roles across job boards every day, so you maintain application volume while you're focused on portfolio preparation.