The short answer: UX and UI designer interviews test whether you can solve the right problem for real users and explain your decisions. The center of most loops is a portfolio walkthrough, followed by questions on your design process, user research, usability principles, accessibility, visual design and design systems, collaboration with developers and product managers, and how you measure success, plus a design challenge or app critique. Pick two or three case studies, and for each one be ready to explain the problem, your role, the key decisions and trade-offs, and the outcome.
Sample answers are illustrations, not quotes from real candidates.
The job market
The U.S. Bureau of Labor Statistics reports a median annual wage of $104,000 for web and digital interface designers in May 2025 (web developers: $92,650). It projects employment of web developers and digital designers to grow 5% from 2025 to 2035, faster than average, with about 13,600 openings a year.
UX vs UI: what each interview emphasizes
| UX-focused roles | UI-focused roles | |
|---|---|---|
| Core question | Are we solving the right problem, and does the flow work? | Is the interface clear, consistent and pleasant to use? |
| Typical questions | Research methods, user flows, information architecture, usability testing | Visual hierarchy, typography, color, components, interaction details |
| Portfolio evidence | Research insights, journey maps, iterations based on testing | High-fidelity screens, design system work, motion and states |
Many roles (often titled product designer) cover both, so prepare for both.
The portfolio walkthrough
“Walk me through a project you’re proud of.”
Use a simple structure and keep it to about 10 minutes per case study:
- Context: the product, users and business goal.
- The problem: what wasn’t working, with evidence (data, research, support tickets).
- Your role: what you did versus the team.
- Process and key decisions: what you explored, what you tested, what you rejected and why.
- Outcome: the result, measured if possible, and what you’d do differently.
“Our checkout had a 68% drop-off on mobile. I led design, working with a PM and two engineers. Session recordings and five usability tests showed people couldn’t find the promo code field and thought shipping costs were hidden. We tested two layouts; the one that showed total cost earlier and moved the promo field into a collapsible row won. Mobile checkout completion rose by 9 points over the next quarter. If I did it again, I’d test with returning customers too, since they behaved differently.”
Interviewers will interrupt with “Why?” Expect it and welcome it.
Process questions
- “What’s your design process?” Describe a real one (understand, define, explore, test, refine, ship, measure) and stress that it adapts to the project: a small fix doesn’t need weeks of research.
- “How do you handle a project with no time for research?” Use what exists (analytics, support tickets, past research, quick guerrilla tests), state your assumptions, ship, and plan to measure.
- “How do you prioritize design work?” By user impact and business value, agreed with product, with quick wins balanced against bigger bets.
User research questions
- “Which research methods do you use, and when?” Interviews and contextual inquiry to understand needs; surveys for scale; usability testing to evaluate designs; analytics and A/B tests to measure behavior; card sorting and tree testing for information architecture.
- “How many users do you test with?” For qualitative usability tests, several small rounds with a handful of users each beat one big study: test, fix, and test again.
- “Tell me about a time research changed your design.” Have a concrete example where users surprised you.
- “How do you avoid leading questions?” Ask about past behavior (“Tell me about the last time you…”), not hypotheticals or opinions about your design.
Usability principles questions
“How do you evaluate the usability of a design?”
Mention testing with users plus expert review. Nielsen Norman Group’s 10 usability heuristics are the most common checklist:
- Visibility of system status
- Match between the system and the real world
- User control and freedom
- Consistency and standards
- Error prevention
- Recognition rather than recall
- Flexibility and efficiency of use
- Aesthetic and minimalist design
- Help users recognize, diagnose, and recover from errors
- Help and documentation
Being able to name two or three and give an example from your work (“We added a progress indicator to the upload flow for visibility of system status”) shows you design from principles, not taste.
Accessibility questions
“How do you design for accessibility?”
The W3C’s Web Content Accessibility Guidelines (WCAG) are the standard. WCAG 2.2 was published on 5 October 2023, and the guidelines are organized under four principles: perceivable, operable, understandable and robust, with testable success criteria at three levels (A, AA and AAA). Many organizations target level AA.
In practice: sufficient color contrast, not relying on color alone, visible focus states, keyboard navigation, text alternatives for images, clear labels and error messages, touch targets large enough to tap, and testing with a screen reader. Mention that accessibility starts in design, not at QA.
Visual design and design system questions
- “How do you create visual hierarchy?” Size, weight, color, contrast, spacing and position, so the most important thing is noticed first.
- “What is a design system, and have you built or used one?” A shared library of components, patterns, tokens (colors, type, spacing) and guidelines that keeps products consistent and speeds up design and development. Explain how you contributed or how you handled a component that didn’t exist yet.
- “How do you design for different screen sizes?” Mobile-first layouts, flexible grids, breakpoints based on content, and platform conventions for iOS and Android.
- “Which tools do you use?” Name them (for example, Figma for design and prototyping) and focus on how you use them: components, variants, auto layout, prototyping.
Collaboration questions
- “How do you hand off designs to developers?” Involve engineers early, annotate edge cases and states (empty, loading, error), use the design system’s components, stay available during build, and review the implementation.
- “A developer says your design is too hard to build. What do you do?” Understand the constraint, find what matters most to users, and agree on a version that keeps it.
- “How do you handle feedback from stakeholders who disagree with your design?” Bring it back to user evidence and goals, and test when opinions conflict. See how to answer “How do you handle criticism?”.
Measuring design success
“How do you know a design worked?” Name metrics tied to the goal: task success rate, time on task, error rate, conversion or completion rates, retention, support tickets, and satisfaction scores. Set the metric before the launch, not after.
Design challenges and app critiques
- Whiteboard challenge (“Design a parking app for a busy city”): clarify the users and goal, define the problem, sketch a flow before screens, talk through trade-offs, and leave time to explain how you’d test it. The interviewer is assessing your thinking, not the polish.
- Take-home exercise: keep to the suggested time, show your process, and state your assumptions. It’s reasonable to ask how long it should take and how it’ll be used.
- App critique (“What’s an app you like, and how would you improve it?”): pick one you know well, name a specific user problem, and suggest an improvement with how you’d validate it.
Behavioral questions
- “Tell me about a design decision you had to defend.”
- “Tell me about a project that failed or didn’t ship.”
- “Tell me about a time you balanced user needs with business goals.”
- “How do you stay current with design trends and tools, including AI?”
Use the STAR method and end each story with the result.
Questions to ask the interviewer
- “How is design involved in deciding what to build?”
- “What’s the ratio of designers to engineers and product managers?”
- “How does the team do research, and who runs it?”
- “Is there a design system, and who maintains it?”
- “How is design success measured here?”
Related guides: graphic designer interview questions, product manager interview questions, digital portfolios vs resumes and iOS developer interview questions.
Frequently asked questions
What questions are asked in a UX/UI designer interview?
How do I present my portfolio in a UX interview?
What are Nielsen's 10 usability heuristics?
What accessibility standard should UX designers know?
How do I prepare for a UX whiteboard challenge?
Sources
- U.S. Bureau of Labor Statistics, Web Developers and Digital Designers, Occupational Outlook Handbook. Read on 2 October 2026.
- Nielsen Norman Group, 10 Usability Heuristics for User Interface Design. Read on 2 October 2026.
- W3C Web Accessibility Initiative, WCAG 2 Overview. Read on 2 October 2026.
