14 Interview Questions

Interview Questions for a UX Designer

To interview a UX Designer, center the conversation on their portfolio, research practice, and design judgment rather than tool proficiency. This set covers questions that surface how they frame problems, run research, defend decisions in critique, and balance user needs against business and engineering constraints, plus behavioral and situational prompts.

Anchor the interview in their real work: walk one project end to end and ask why at every fork. Then add a short live critique or whiteboard so you see thinking, not just polished case studies.

Craft: Research, Process & Critique

Walk me through one project in your portfolio from problem to outcome. Why did you make the key decisions you made?

What to look for: A clear problem definition, the reasoning behind decisions, evidence they considered alternatives, and honest reflection on what they'd change.

How do you decide what to research and which method to use before designing?

What to look for: Matching method to question (interviews for why, usability tests for can-they, analytics for what), and not over- or under-researching.

Show me a design you had to significantly change after testing. What did users do that surprised you?

What to look for: Genuine willingness to be wrong, learning from observed behavior, and translating a finding into a concrete design change.

Critique this screen of ours out loud. What works, what doesn't, and what would you test first?

What to look for: Structured critique tied to user goals and heuristics, specific not vague feedback, and prioritizing the highest-impact issue.

How do you design for accessibility, and where do you usually see teams cut corners?

What to look for: Beyond color contrast: keyboard nav, focus order, semantic structure, screen readers, and treating accessibility as baseline not polish.

When the data and your design intuition disagree, how do you resolve it?

What to look for: Respect for evidence, interrogating whether the metric measures the right thing, and a bias toward testing rather than ego or pure HiPPO.

How do you work with a design system: when do you follow it, and when do you break it?

What to look for: Valuing consistency and speed, but recognizing when a pattern fails the user and how to propose a system change rather than a one-off.

How do you measure whether a design actually succeeded after it shipped?

What to look for: Defining success up front, behavioral metrics tied to the user goal, and closing the loop with post-launch research.

Behavioral

Tell me about a time engineering said your design wasn't feasible. What happened next?

What to look for: Collaboration over insistence, finding the constraint early, and reaching a solution that still served the user.

Describe a time a stakeholder pushed a design choice you disagreed with. How did you handle it?

What to look for: Advocating with evidence and user empathy, knowing when to concede, and keeping the relationship intact.

Tell me about the most useful piece of critique you've ever received and what you did with it.

What to look for: Openness to feedback, separating self from the work, and a real behavior change as a result.

Situational / Problem-Solving

You're asked to redesign our onboarding but have no budget for research. How do you proceed responsibly?

What to look for: Scrappy research (support tickets, analytics, guerrilla tests), stating assumptions explicitly, and de-risking before launch.

A new feature must ship in two weeks. How do you scope the UX so it's good enough without cutting the wrong corners?

What to look for: Identifying the core user task, protecting critical-path usability, and being explicit about what's deferred.

Users say they want a feature, but you suspect it won't solve their real problem. What do you do?

What to look for: Digging past the stated want to the underlying job-to-be-done, and validating before building the literal request.

FAQ

Frequently asked questions

What should a UX Designer's portfolio review actually reveal? +
Thinking, not just visuals. The strongest signal is a designer narrating the messy middle: the problem they framed, the research that changed their mind, the constraints they navigated, and the trade-offs behind each decision. Polished mockups with no story behind them are a yellow flag.
Should I separate UX research and UI design in the interview? +
It depends on the role. For a generalist or product designer, test both in one flow. For specialized teams with dedicated researchers, weight the interview toward whichever the role demands while still checking they can collaborate across the boundary.
How do I run a fair design exercise without unpaid work? +
Use a short, abstract whiteboard or live critique focused on reasoning rather than a finished deliverable for your real product. Keep it under an hour, never ask for polished production work, and judge process over pixels.
What are red flags in a UX Designer interview? +
Defending a design with taste instead of user goals, no research in their process, inability to critique constructively, blaming engineering or stakeholders, and treating accessibility as an afterthought.
How much tool proficiency should I test for? +
Less than most teams assume. Figma fluency is quickly learnable and easy to verify with a quick screen-share. Judgment, research instinct, and the ability to defend decisions are far harder to teach and should drive the hiring decision.
Built for recruiters & hiring teams

See how much faster your team could hire

Get a personalized walkthrough of Pitch N Hire on your own roles and workflow. No slides, no obligation.

Prefer to talk? Book a demo · View pricing

Free 1-user plan · No credit card · Talk to a real hiring expert

One Hiring Infrastructure.
Zero Tool Chaos.

Demos are consultative. We respect privacy and enterprise
governance. No lock-ins.

Sign up free Book a demo