Interview questions · UX/UI Designer

UX/UI Designer interview questions

UX/UI hiring managers look for designers who ground every visual and interaction decision in user research and measurable outcomes, not aesthetic preference. They want to see a rigorous design process — from problem framing through testing — and evidence that you can translate complex user needs into interfaces that are both beautiful and functional. Strong candidates also demonstrate the ability to advocate for users when business or engineering pressures push in a different direction.

Walk me through a project where you identified a significant usability problem through research and drove a design change.

Recruiters want to see that your design decisions are grounded in evidence, not intuition.

Model answerDuring usability testing of our mobile checkout, five of six participants abandoned on the address-entry screen. Session recordings showed they were confused by the split between billing and shipping fields. I proposed a 'same as shipping' default toggle, built a prototype in Figma, and tested it with eight users — all eight completed checkout without confusion. After launch, checkout completion rate on mobile rose 19 percentage points, adding approximately $2.1M in annual revenue.

How do you handle conflict between your design recommendation and what engineering says is feasible?

Design-engineering tension is inevitable; recruiters want designers who collaborate rather than capitulate or escalate.

Model answerFor a complex data-visualization feature, engineering said animating transitions at 60fps would take four additional sprints. I audited which transitions were essential for comprehension versus decorative — about 30% were critical. I redesigned the remaining 70% as static states and used an existing CSS library for the critical ones. We shipped in the original timeline at nearly identical perceived quality, and the engineering lead cited the collaboration as a model for future sprints.

Describe your process for designing for accessibility from the start of a project.

Accessibility is increasingly a legal requirement and a quality signal; recruiters want it built in, not bolted on.

Model answerAccessibility enters my process at the component level, not the QA stage. I use a color-contrast checker during color-palette selection, design focus states alongside hover states, and annotate Figma files with ARIA roles and reading order. On a government-portal redesign, this early approach meant we passed WCAG 2.1 AA audit with zero critical issues — the previous version had 47 — and avoided a costly remediation sprint.

Tell me about a time you had to design under significant ambiguity, with unclear requirements or shifting goals.

Design projects rarely start with perfect briefs; recruiters want to see structured sense-making under uncertainty.

Model answerWe were asked to 'redesign onboarding' with no user data, no defined success metric, and a two-week deadline. I ran five 30-minute problem-framing interviews with customer-success reps the first two days to surface the top three drop-off points, then defined success as 'user completes first core action within 10 minutes of sign-up.' With that north star, I built a three-screen onboarding flow in prototype form by day seven. The guided approach improved activation rate from 31% to 54% in the A/B test.

How do you present and defend your design decisions to stakeholders who have strong personal opinions about visual style?

Stakeholder management is a critical design skill; recruiters want to see principled confidence over people-pleasing.

Model answerA marketing VP wanted to use a high-contrast neon-green CTA that failed contrast accessibility standards and conflicted with our design system. I presented three versions in a structured review: his preference with a note on accessibility risk, a compliant version using our established coral accent, and a third hybrid. I showed heatmap data from a comparable page showing the coral button outperformed the neon version by 11% in click-through. He chose the compliant version and later referenced the data in a leadership review.

Describe how you have contributed to building or maintaining a design system.

Design systems are the connective tissue between design and engineering; ownership here signals seniority and systems thinking.

Model answerI led the componentization of our legacy UI into a Figma design system with 140 components, documented usage guidelines, and a Storybook integration so engineers could pull components directly into code. I ran bi-weekly component council meetings to manage contributions and deprecations. Adoption across five product teams reached 87% within four months, and our design-to-development handoff time dropped from an average of 4.5 days to 1.8 days.

How do you decide which research method to use for a given design problem?

Method selection reveals research maturity — recruiters want evidence you choose the right tool for the question, not just the most familiar one.

Model answerI map the question to the appropriate method using an 'attitudinal vs. behavioral' and 'qualitative vs. quantitative' axis. For a navigation restructure where we needed to understand mental models, I ran a card sort with 40 participants and followed up with five tree-testing sessions. For a checkout optimization where we already had a hypothesis, I went straight to an A/B test. This approach ensures we spend research budget on the right question type rather than defaulting to interviews for everything.

Tell me about a design you shipped that you would change now and why.

Reflective practice and intellectual honesty are markers of a mature designer; this question also reveals how you handle critique.

Model answerWe shipped a notification center I designed that gave users 12 toggle controls for granular preferences. I was proud of the control it offered. Post-launch data showed that 68% of users never opened it and notification fatigue actually increased. If I redesigned it today I would start with three smart defaults based on usage frequency, offer a 'quiet mode' one-tap option, and surface individual controls only on demand. More control is not always better UX.

Tips for this role

Practise for THIS role

Paste your job offer, pick a recruiter, and run a mock interview with a detailed coaching report.

🎤 Start an interview

Everything you can do