The Short Answer
UX interviews test three things: can you design, can you think, and can you communicate.
The process usually has 3-4 rounds:
- Portfolio review
- Design challenge (whiteboard or take-home)
- Behavioral interview
- Team fit conversation
Here are the questions you’ll face and how to answer each one.
Portfolio Questions
“Walk me through your portfolio”
This is almost always the first question. Here’s how to nail it:
The wrong answer: Clicking through every project, showing screens, talking about colors.
The right answer:
“I’ll walk through [project name], which best represents my approach to [specific skill, e.g., ‘user-centered problem-solving’]. This was a [type of project] where the challenge was [problem]. I started by [research approach], which revealed [key insight]. From that, I [design decisions], and the result was [outcome/metric].”
Structure:
- Context (what, who, when)
- Your role (be specific)
- The problem (what were you solving?)
- Your process (research → design → test)
- The outcome (metrics, learnings, impact)
- What you’d do differently
Keep it to 5 minutes. The interviewer will ask follow-ups.
“What project are you most proud of?”
They’re looking for:
- Does it show real impact?
- Can you articulate why it matters?
- Does it demonstrate growth?
Good answer:
“My meal planning app redesign. I started with zero users, ran 15 interviews, discovered the real problem was decision fatigue (not recipe discovery), redesigned the flow, and increased weekly active users by 40% in three months.”
Bad answer:
“The one where I redesigned Spotify. It took 8 weeks and I used Figma. The colors are warm and the typography is clean.”
“What’s the weakest part of your portfolio?”
This tests self-awareness. Don’t dodge it.
Good answer:
“My second project is weaker because I didn’t have time for proper user testing. I know the process and I’d do it differently now, but I included it to show growth in my early work. I’m actively working on adding research depth to my practice.”
Design Challenge Questions
“Design an [X] for [Y audience]”
You’ll get a whiteboard prompt or a take-home assignment. Here’s how to approach it:
The Framework
-
Understand the problem (5 min)
- Ask clarifying questions
- Define scope and constraints
- Identify the user
-
Research and empathize (10 min)
- Sketch user personas
- Identify pain points
- Map the user journey
-
Ideate (15 min)
- Brainstorm 3-5 solutions
- Sketch wireframes
- Choose the best approach
-
Design (20 min)
- Create low-fidelity wireframes
- Show key screens
- Explain your reasoning
-
Validate (10 min)
- Describe how you’d test
- Mention key metrics
- Note potential risks
-
Summarize (5 min)
- Review your solution
- Acknowledge trade-offs
- Suggest next steps
What Interviewers Are Looking For
- Do you think about users? (Not just screens)
- Do you ask questions? (Clarifying scope, constraints)
- Can you think iteratively? (Testing, refining)
- Can you communicate your thinking? (Explaining decisions)
- Do you consider constraints? (Time, tech, business)
The Biggest Mistake
Jumping straight to solutions. Always start with the problem. The best designers spend more time defining the problem than solving it.
“How do you prioritize features?”
Good answer:
“I use a combination of frameworks depending on context. For prioritization, I look at:
- Impact: How many users does this affect? How significant is the benefit?
- Effort: How complex is it to build?
- Strategic alignment: Does this match our product goals?
I typically use RICE scoring (Reach, Impact, Confidence, Effort) for data-driven decisions, and MoSCoW (Must have, Should have, Could have, Won’t have) for stakeholder alignment. The key is being transparent about assumptions and iterating as we learn more.”
“How do you measure UX success?”
Good answer:
“It depends on the product, but I use a mix of quantitative and qualitative metrics:
Quantitative:
- Task completion rate
- Time on task
- Conversion rate
- Error rate
- SUS (System Usability Scale) score
Qualitative:
- User satisfaction (CSAT)
- User quotes and feedback
- Observational insights
The best approach ties UX metrics to business outcomes. For example, improving checkout UX from 60% to 80% completion rate directly impacts revenue.”
Behavioral Questions
“Tell me about a time you failed as a designer”
They’re looking for:
- Self-awareness
- Ability to learn from mistakes
- Growth mindset
Good answer:
“On my last project, I designed a checkout flow based on what I thought users wanted. I didn’t test it first. When we launched, 70% of users dropped off. I went back, ran usability tests, discovered the trust signals were missing, and redesigned. We fixed the issue and conversion went up 25%. It taught me to never skip testing, no matter how confident I am.”
“Tell me about a time you disagreed with a stakeholder”
Good answer:
“A stakeholder wanted to add a pop-up on our landing page for a promotion. I had data showing pop-ups increased bounce rate by 40%. Instead of just saying ‘no,’ I showed them the data, proposed an alternative (a subtle banner), and A/B tested both. The banner outperformed the pop-up. The stakeholder appreciated the data-driven approach and we moved forward collaboratively.”
“How do you handle conflicting feedback from users?”
Good answer:
“When users give conflicting feedback, I look for patterns and underlying needs. User A says they want feature X. User B says they hate feature X. The real question is: what problem is each user trying to solve? Usually, the surface-level requests conflict but the underlying needs align. I dig deeper through follow-up questions and find the common thread. For example, users might say they want a bigger search bar, but they actually want faster results.”
Company-Specific Questions
“What do you think about our product?”
Do this:
- Use the product for 10-15 minutes before the interview
- Note 2-3 strengths
- Note 1-2 improvement opportunities
- Come with specific, constructive suggestions
Good answer:
“I’ve been using your app for the past week. I love how clean the onboarding flow is — you clearly reduced friction compared to competitors. One thing I noticed is the settings navigation could be easier to find. I think adding a search function in settings would help power users. Overall, it’s a well-designed product with room for improvement in discoverability.”
“Why do you want to work here?”
Do this:
- Research the company’s mission and values
- Connect your experience to their challenges
- Show genuine interest (not just “I need a job”)
Good answer:
“I’m drawn to your focus on accessibility. As someone who’s worked extensively with WCAG guidelines, I see real alignment with my values and expertise. I also admire how you’ve approached [specific product feature or initiative] — it shows a user-first mindset that I want to be part of.”
Questions They Ask About You
“What’s your design process?”
Good answer:
“My process follows five stages: Empathize, Define, Ideate, Prototype, and Test. But it’s not rigid — I adapt based on project constraints. For a startup with a 2-week timeline, I’d focus on rapid research and low-fi testing. For a large product, I’d invest more in user research and data analysis. The core principle is always the same: understand the user, validate assumptions, iterate based on feedback.”
“What tools do you use?”
Good answer:
“Figma is my primary design tool — I use it for everything from wireframing to prototyping to design systems. For research, I use Miro for collaboration and Maze for usability testing. For analytics, I’m comfortable with Hotjar and Google Analytics. I also use Zeroheight for design system documentation. I keep my toolkit focused on what works and adopt new tools only when they solve a specific problem.”
“What’s your favorite design trend?”
Avoid: Talking about trends superficially.
Good answer:
“I’m most excited about AI-assisted design tools. Not because they’ll replace designers, but because they’ll handle the repetitive work — icon generation, layout variations, accessibility checking — freeing us to focus on the things AI can’t do: empathy, strategy, and judgment. The best designers in 2025 will be those who learn to collaborate with AI rather than compete with it.”
Questions YOU Should Ask Them
Never say “I don’t have any questions.” Asking smart questions shows you’re thinking critically.
Good Questions to Ask
- “What does a typical day look like for a UX designer here?”
- “How does the design team collaborate with product and engineering?”
- “What’s the biggest UX challenge your product team is facing right now?”
- “How do you measure the impact of design at this company?”
- “What does career growth look like for UX designers here?”
- “Can you describe your design process and how it evolved?”
- “What’s one thing you’d change about your product’s UX?”
Bad Questions to Ask
- “What do you do?” (You should already know)
- “How much vacation time do I get?” (Ask after getting the offer)
- “Is the pay competitive?” (Discuss compensation later)
The Whiteboard Challenge: Step by Step
You’re given: “Design a bike-sharing app for a city.”
Step 1: Clarify (2 min)
“Before I start designing, I want to understand the scope. Is this for the user side, the admin side, or both? Who are the primary users? What are the key constraints?”
Step 2: Define Users (3 min)
“I’d start by identifying the user segments. Here are three I’d focus on:
- Commuters — need fast, reliable bikes
- Tourists — need navigation and exploration features
- Casual riders — need flexibility and pricing clarity”
Step 3: Problem Framing (3 min)
“The core problem is: ‘People need reliable transportation but don’t know where bikes are, how much they cost, or how to unlock them.’ My job is to solve that.”
Step 4: Ideate (5 min)
Sketch 3 solution directions:
- Map-first approach
- List-based approach
- Hybrid approach
Step 5: Choose and Design (7 min)
“I’d go with a map-first approach because location is the primary decision factor. Here are the key screens: map view, bike details, unlock flow, and payment.”
Step 6: Validate (3 min)
“I’d validate this by testing with 5 users. Key metrics: task completion time, error rate, and user satisfaction. I’d also A/B test different map styles to optimize for discoverability.”
The Bottom Line
Great UX interviews aren’t about having the right answers. They’re about showing how you think.
The formula:
- Understand the problem (ask questions)
- Show your process (research, design, test)
- Explain your decisions (rationale over opinions)
- Acknowledge limitations (humility builds trust)
- Learn from everything (growth mindset)
Practice with friends. Record yourself. Review your answers. The more you practice, the more natural it becomes.