UX Designer Interview Questions: 30 Questions, Portfolio Review and Design Challenge (2026)

UX designer interview questions test how you think more than what you can draw: how you frame a problem, choose research methods, make trade-offs with product and engineering, and defend decisions with evidence. The three questions you are most likely to get are "Walk me through a project in your portfolio", "How do you decide what research to do?" and "Tell me about a time stakeholders disagreed with your design."

Below are 30 questions grouped by skill, with what a strong answer shows for each, five sample answers we wrote, a guide to the portfolio review and the design challenge, and the usability and accessibility standards interviewers expect you to know, checked on the primary sources as of October 2026.

How a UX designer interview usually runs

Every company sets its own loop, and titles (UX designer, product designer, interaction designer) change the emphasis. A common shape:

1. Recruiter screen. Background, the kind of product work you want, portfolio link check, logistics.
2. Hiring manager conversation. Usually a design manager. One project in depth, how you work with PMs and engineers, what you want to learn.
3. Portfolio presentation (often 45–60 minutes). You present one to three case studies to a panel, then take questions.
4. Design challenge. Either a live whiteboard exercise (often 45–60 minutes) or a take-home assignment you present later.
5. Cross-functional interviews. A PM, an engineer or a researcher asks how you collaborate, handle feedback and make trade-offs.

Some teams skip the challenge for senior candidates; others add an app critique. Ask the recruiter for the format and time limits of each round, and whether the take-home has a time cap. Our guide to the take-home assignment interview covers scoping and presenting one.

The portfolio review: what the panel is scoring

The portfolio presentation is usually the round that decides the loop. Panels are not grading polish; they want to hear your reasoning. Structure each case study like this:

1. Context (1–2 minutes). The product, the users, the business goal, your role and team size.
2. The problem. What was wrong and how you knew: data, support tickets, research findings.
3. Process, with decisions. Show two or three moments where you chose between options and why. Rejected directions are often more persuasive than the final screen.
4. Constraints and trade-offs. Engineering limits, deadlines, accessibility, what you cut.
5. Outcome. A measured result if you have one, or what you learned from testing if it never shipped. Say plainly which.
6. Reflection. What you would do differently. Panels often ask this anyway.

The design challenge: a structure you can say out loud

In a whiteboard challenge the prompt is deliberately vague ("Design a parking app for a city"). Interviewers watch the first ten minutes most closely. A sequence that works:

• Clarify. Who is the user, what is the goal, what platform, any constraints? Ask three or four questions, then state your assumptions.
• Pick one user and one scenario. Narrowing is a decision, and making decisions is what they are scoring.
• Map the journey. Steps the user takes today and where it hurts.
• Sketch two or three directions at low fidelity, then choose one and say why.
• Cover edge cases and accessibility: errors, empty states, slow connections, screen readers.
• Say how you would test and measure it. One success metric and one usability test you would run first.

30 UX designer interview questions, grouped by skill

Process and portfolio

• Walk me through a project in your portfolio. Shows a clear problem, your specific role, decisions with reasons, and an honest outcome.
• What is your design process? Shows a process you adapt to the problem, not a fixed five-step diagram.
• Which project are you least proud of, and why? Shows self-awareness and what you changed afterwards.
• How do you know when a design is done? Shows you tie "done" to goals and test results, and accept iteration after launch.
• How do you balance user needs and business goals? Shows you look for designs that serve both and can name a time they conflicted.
• Tell me about a design decision you made with incomplete data. Shows you can commit, state your assumption, and plan to check it.

Research and usability

• How do you decide which research method to use? Shows you match the method to the question: interviews for why, analytics for what, usability tests for whether it works.
• How many users do you test with? Shows you know small rounds of qualitative testing find most major issues and that the right number depends on the goal.
• How do you do research with no budget? Shows scrappy options: guerrilla tests, support tickets, sales calls, internal users with caveats.
• Explain a usability heuristic you used recently. Shows you can apply a named principle, such as Nielsen's "visibility of system status", to a real screen.
• How do you turn research into decisions? Shows synthesis into a few clear insights tied to design changes, not a 40-page report.
• What would you do if research contradicted what the PM wants to build? Shows you bring evidence, propose a test, and respect that the PM may still decide.

Interaction, visual and accessibility

• How do you design for accessibility? Shows you build it in from the start: contrast, focus order, labels, touch targets, and testing with assistive technology.
• What is the minimum contrast for body text? Shows you know WCAG AA: 4.5:1 for normal text, 3:1 for large text.
• How do you use a design system, and when would you break it? Shows you value consistency and know how to propose a new component properly.
• Critique an app you use every day. Shows a structured critique: the user, their goal, what works, what doesn't, and a specific fix.
• How do you design empty, error and loading states? Shows you think beyond the happy path.
• How do you hand off designs to engineers? Shows clear specs, states, edge cases, and staying involved through build.

Collaboration and behavioral

• Tell me about a time stakeholders disagreed with your design. Shows you listen, separate taste from evidence, and find a test that settles it.
• Describe a time an engineer said your design couldn't be built. Shows you treat constraints as design input and find an alternative together.
• Tell me about critical feedback you received on your work. Shows you can take critique without defensiveness. See our critical feedback answer guide.
• How do you work with product managers? Shows shared goals, early involvement and clear decision rights.
• Tell me about a project that failed. Shows ownership and what you learned.
• How do you present work to executives? Shows you lead with the problem and decision needed, not the screens.

Situational

• You have two weeks to redesign onboarding. What do you do first? Shows scoping: find where users drop off, talk to a few, test the riskiest change.
• Analytics show a feature you designed isn't used. What next? Shows curiosity: is it discoverability, value or usability? How would you find out?
• A PM asks you to copy a competitor's flow. How do you respond? Shows you check whether their users and goals match yours before copying.
• Leadership wants a feature that research says users don't need. What do you do? Shows you share evidence, propose a small experiment, and accept the decision if they proceed.
• You join a team with no design system. Where do you start? Shows you audit what exists and standardize the most-used components first.
• How would you improve our product? Shows you prepared: one specific, evidence-based idea with humility about what you can't see from outside.

Standards interviewers expect you to know (as of October 2026)

Sources: Nielsen Norman Group's 10 usability heuristics and the WCAG 2.2 specification at W3C.

Five sample answers (examples we wrote)

"What is your design process?"

Example (mid-level product designer): "It flexes with the problem, but the core is the same: understand, explore, decide, test. On a recent checkout redesign, understanding meant reading 200 support tickets and watching five session recordings. Exploring meant three very different flows in low fidelity. We decided with the PM and engineering lead using a simple effort-versus-impact grid, then tested the chosen flow with five users. Two of them missed the promo code field, so we moved it before launch. For a small UI fix I compress all of that into an afternoon."

"Tell me about a time stakeholders disagreed with your design."

Example: "Our head of sales wanted a long signup form to qualify leads. I wanted three fields. Instead of arguing taste, I asked what sales really needed: company size and use case. We agreed to run both versions for two weeks. The short form brought more signups, and we collected company size later in onboarding, which gave sales what they needed. The lesson for me was to argue about the goal, not the screen."

"How do you decide which research method to use?"

Example: "I start with the question. If we don't know why people churn, I do interviews. If we know the problem but not how big it is, I look at analytics or run a short survey. If we have a design and want to know if it works, I run usability tests. On my last project, analytics showed a drop on step three of setup; five usability tests showed why in one afternoon. The label on the main button was ambiguous."

"How do you design for accessibility?"

Example: "From the first wireframe, not as a final check. I check text contrast against WCAG AA, which is 4.5 to 1 for normal text. I design visible focus states, label every form field, never rely on color alone for errors, and keep touch targets large. Before handoff I tab through the prototype, and after build I test the key flow with a screen reader with an engineer. On one project that caught a modal that trapped keyboard focus."

"Tell me about a project that didn't go well."

Example (Situation, Task, Action, Result): "I designed a dashboard redesign that looked great in reviews but confused existing users after launch; support tickets went up the first week. My task was to fix it fast. I called six customers, found that we'd moved the export button they used daily, and shipped a fix within a week that restored it with a short tooltip. Tickets dropped back. Since then I always test redesigns with existing power users, not just new ones."

Questions to ask the interviewer

• "How early are designers involved: before or after the roadmap is set?"
• "How does the team do research today, and is there a dedicated researcher?"
• "How do design decisions get made when design and product disagree?"
• "What does a great first six months look like for this role?"

More options are in our list of questions to ask the interviewer.

How to practice for a UX designer interview

1. Rehearse your portfolio talk out loud, timed, at least twice. Cut anything that doesn't explain a decision.
2. Prepare for the questions after the presentation: "What would you change?", "How did you measure success?", "What did the engineer push back on?"
3. Do two practice design challenges with a 45-minute timer, speaking your reasoning the whole time.
4. Write four STAR stories (disagreement, failure, feedback, influence) with the free STAR story builder.
5. Run a mock interview. CoPilot Interview's Mock Interview builds questions from your résumé and the job description, reads them aloud, scores each spoken answer out of 10 with what to fix and a model answer, then gives a report card. The browser version at /ai-mock-interview needs no install and includes behavioral and product tracks.

For a round-by-round prep plan focused on the portfolio presentation, see our UX designer interview prep guide. Product designers should also skim our product manager interview questions, because PMs on the panel often ask product-sense questions.

FAQ

What are the most common UX designer interview questions?

Expect "Walk me through a project in your portfolio", "What is your design process?", "How do you choose a research method?", "Tell me about a time stakeholders disagreed with your design" and "How do you design for accessibility?".

How long should a UX portfolio presentation be?

Ask the recruiter, because formats vary. Many panels give 45 to 60 minutes in total, so plan about 30 to 40 minutes of presenting one to three case studies and leave the rest for questions.

How do I approach a whiteboard design challenge?

Clarify the user, goal and constraints, state your assumptions, pick one user and scenario, map the journey, sketch two or three directions, choose one and explain why, cover edge cases and accessibility, and finish with how you would test it.

What accessibility facts should a UX designer know for interviews?

Know the four WCAG principles (perceivable, operable, understandable, robust), the A, AA and AAA levels, and that level AA requires a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text, per WCAG 2.2 as of October 2026.

What if my best project never launched?

Present it anyway and say so plainly. Explain the decisions, what testing showed, and why it stopped. Panels care more about your reasoning than whether it shipped.

How do I answer "How would you improve our product?"

Use the product before the interview, pick one specific problem, explain who it affects and what evidence you would gather, propose a fix, and acknowledge what you cannot see from outside the company.