9 role-specific questions
UI/UX Designer Interview Questions & Answers
Design interviews centre on your process and your portfolio: how you understand problems, research with users, test and iterate, design accessibly, collaborate with engineers, and measure whether a design worked.
Free, no sign-up. 54 questions in this role's practice pool, including behavioural, HR and situational questions.
UI/UX design interview questions
Design process, research, usability testing, accessibility, design systems and portfolio questions.
1.
Walk me through your design process.
BeginnerRole knowledgePractise this question and get feedbackWhat the interviewer is evaluating
Whether you follow a user-centred process and adapt it to constraints.
Key points a strong answer covers
- Understand the problem. Start by understanding the problem, goals and constraints.
- Research. Research users and existing data.
- Ideate & prototype. Explore options, wireframe and prototype.
- Test. Test with users and iterate.
- Deliver & measure. Hand off, ship and measure outcomes.
Suggested answer structure
- State your approach in one sentence.
- Walk through the steps or criteria you use.
- Give a real example from your work.
- Say how you measure whether it worked.
Common mistakes
- Describing a rigid textbook process you don't really follow.
- No mention of measuring results.
Likely follow-up questions
- How does your process change with a tight deadline?
- Tell me about a time research changed your design direction.
Example strong answer
It depends on the project's size, but the shape is consistent. First I make sure I understand the problem: the business goal, who the users are, the constraints, and how we'll measure success. Then research — existing analytics and support tickets, a few user interviews, and a look at how others solve it. I explore several directions with sketches and low-fidelity wireframes before committing, then build a prototype and test it with five or so users, iterating on what confuses them. I work closely with engineers during handoff — design tokens, states, edge cases — and after launch I check the metrics we agreed on. Under a tight deadline I compress research, but I never skip testing entirely.
2.
How do you plan and run a usability test?
IntermediateRole knowledgePractise this question and get feedbackWhat the interviewer is evaluating
Practical research skills.
Key points a strong answer covers
- Goals & tasks. Define what you want to learn and realistic tasks.
- Participants. Recruit representative participants (often ~5 per round).
- Neutral moderation. Ask them to think aloud; avoid leading questions.
- Measure. Record task success, errors, time, and observations.
- Synthesis & action. Synthesise findings by severity and turn them into changes.
Suggested answer structure
- State your approach in one sentence.
- Walk through the steps or criteria you use.
- Give a real example from your work.
- Say how you measure whether it worked.
Common mistakes
- Asking users whether they 'like' the design.
- Leading questions like 'Was that easy?'
Likely follow-up questions
- Moderated or unmoderated — when would you choose each?
- How do you handle stakeholders who disagree with the findings?
Example strong answer
I start with the research questions — for a checkout redesign, 'can people apply a discount code and change delivery without help?' — and turn them into realistic tasks with a scenario, not instructions that give away the answer. I recruit five or six participants who match the target users with a short screener. In the session I ask them to think aloud, stay neutral, and avoid helping or asking leading questions like 'was that easy?'. I note task success, errors, time and where they hesitated. Afterwards I cluster observations, rate issues by severity and frequency, and share a short readout with clips, so the team sees the problems directly, along with recommended changes.
3.
How do you design for accessibility?
IntermediateRole knowledgePractise this question and get feedbackWhat the interviewer is evaluating
Inclusive design as standard practice.
Key points a strong answer covers
- Contrast & colour. Sufficient contrast and never colour alone to convey meaning.
- Keyboard & focus. Visible focus states and logical keyboard order.
- Text & touch targets. Readable, resizable text and large touch targets.
- Screen readers & content. Labels, alt text, heading structure — annotated for developers.
- Standards & testing. Follow WCAG and test with assistive technology users.
Suggested answer structure
- State your approach in one sentence.
- Walk through the steps or criteria you use.
- Give a real example from your work.
- Say how you measure whether it worked.
Common mistakes
- Treating accessibility as a final check.
- Relying on colour alone for errors.
Likely follow-up questions
- How would you design an accessible error state on a form?
- How do you get accessibility prioritised on a busy team?
Example strong answer
I build it in from the start rather than checking at the end. Text and essential UI meet WCAG contrast — 4.5:1 for body text — and I never use colour alone: errors have an icon and a message too. I design visible focus states and a logical order, and annotate keyboard behaviour for complex components like menus. Text must work at 200% zoom, touch targets are at least around 44 pixels, and motion respects reduced-motion settings. In handoff I annotate headings, labels, alt text and what screen readers should announce. Our design system bakes most of this into components, and I test with screen readers and, when possible, with disabled users.
4.
What is a design system, and how would you build or maintain one?
IntermediateRole knowledgePractise this question and get feedbackWhat the interviewer is evaluating
Systems thinking and collaboration with engineering.
Key points a strong answer covers
- What it is. Reusable components, tokens, patterns and guidelines — documented.
- Tokens. Design tokens for colour, type and spacing shared with code.
- Engineering partnership. Built with engineers so design and code stay in sync.
- Governance & adoption. Contribution, versioning and adoption processes.
- Value. Consistency, speed and built-in accessibility.
Suggested answer structure
- State your approach in one sentence.
- Walk through the steps or criteria you use.
- Give a real example from your work.
- Say how you measure whether it worked.
Common mistakes
- Describing it as just a UI kit in Figma.
- No plan for keeping design and code aligned.
Likely follow-up questions
- How do you decide whether something becomes a new component?
- How do you measure a design system's success?
Example strong answer
A design system is the shared language of a product: design tokens for colour, typography and spacing; reusable components with their states and variants; patterns for things like forms and empty states; and guidelines on when to use what — kept in sync between Figma and code. I'd start with an audit of what already exists and the inconsistencies, define tokens, then build the most-used components with engineers so the Figma library and the coded components — documented in something like Storybook — match. Governance matters as much as the components: a clear way to propose additions, versioning and deprecation. Success shows in adoption, faster delivery and fewer accessibility bugs.
5.
How do you measure whether a design is successful?
IntermediateRole knowledgePractise this question and get feedbackWhat the interviewer is evaluating
Outcome orientation: whether you judge design by its effect, not by approval.
Key points a strong answer covers
- Define success upfront. Agree success criteria before designing.
- Behavioural metrics. Behavioural metrics: conversion, completion, drop-off, errors.
- Attitudinal metrics. Attitudinal metrics: SUS, CSAT, feedback.
- Experiments. A/B tests where traffic allows.
- Qualitative too. Combine numbers with qualitative insight.
Suggested answer structure
- State your approach in one sentence.
- Walk through the steps or criteria you use.
- Give a real example from your work.
- Say how you measure whether it worked.
Common mistakes
- Judging success by stakeholder approval alone.
- Picking metrics after launch.
Likely follow-up questions
- What if the metric improved but users complain?
- How do you measure a design with too little traffic for A/B testing?
Example strong answer
I agree what success means before designing, ideally as a hypothesis: 'if we simplify the sign-up form, completion will rise from 40% to 50% without hurting lead quality'. Then I use behavioural metrics — completion and conversion rates, where people drop off in the funnel, error rates, support tickets about the flow — and attitudinal ones like a System Usability Scale score or CSAT. Where there's enough traffic I A/B test; where there isn't, I compare before and after and run usability tests on the new version. I always pair numbers with qualitative insight from session recordings or interviews, because metrics tell you what changed, not why.
6.
How do you handle critical feedback on your designs?
BeginnerBehaviouralPractise this question and get feedbackWhat the interviewer is evaluating
Collaboration and ego management.
Key points a strong answer covers
- Listen & understand. Listen and ask questions to understand the concern.
- Separate taste from evidence. Bring it back to goals and evidence rather than taste.
- Example. A real example.
- Outcome. What changed as a result.
Suggested answer structure
- Situation — one or two sentences of context.
- Task — what you were responsible for.
- Action — what you did, step by step (say “I”).
- Result — what changed, with a number if you can back it up.
- Reflection — what you learned or would do differently.
Common mistakes
- Getting defensive.
- Accepting every opinion without questioning it.
Likely follow-up questions
- What do you do when a senior stakeholder insists on a design you believe is wrong?
- How do you run a design critique?
Example strong answer (a fictional story — use your own)
I see feedback as part of the job, so I try to understand it before reacting — asking what problem they're seeing, because a request like 'make the button bigger' usually hides a real concern, such as people missing the main action. Then I bring the discussion back to the goals and evidence rather than taste. For example, on an onboarding redesign our head of sales felt the new flow hid pricing. Instead of debating, I ran a quick five-user test of both versions; people did look for pricing earlier than I'd assumed, so I added a pricing summary to step one. Completion stayed the same and sales calls about pricing dropped. I learned to test disagreements quickly rather than argue them.
7.
Which research methods do you use, and how do you choose?
IntermediateRole knowledgePractise this question and get feedbackWhat the interviewer is evaluating
Choosing the right method for the question.
Key points a strong answer covers
- Generative vs evaluative. Generative research explores problems; evaluative tests solutions.
- Qualitative methods. Interviews, contextual inquiry, diary studies.
- Quantitative methods. Surveys, analytics, A/B tests, card sorting, tree testing.
- Choose by question & constraints. Choose by the question, project stage and constraints.
Suggested answer structure
- State your approach in one sentence.
- Walk through the steps or criteria you use.
- Give a real example from your work.
- Say how you measure whether it worked.
Common mistakes
- Using surveys to answer 'why' questions.
- Running research without a clear question.
Likely follow-up questions
- When would a card sort help?
- How do you do research with almost no budget?
Example strong answer
I choose by the question and the project stage. Early, when we don't yet understand the problem, I use generative methods: user interviews, contextual inquiry where I watch people work, or diary studies for behaviour over time. When I need numbers — how common is a problem, which option do people prefer — surveys and product analytics. For information architecture, card sorting and tree testing. To evaluate a design, usability tests, and A/B tests once it's live. Interviews and observation tell me why; analytics and surveys tell me how many. With no budget I use guerrilla tests with five people, support tickets, sales call notes and existing analytics.
8.
How do you work with developers to make sure designs are built correctly?
BeginnerRole knowledgePractise this question and get feedbackWhat the interviewer is evaluating
Cross-functional collaboration.
Key points a strong answer covers
- Involve early. Involve developers early on feasibility.
- Complete specs. Specify all states: empty, loading, error, responsive.
- Shared components & tokens. Use shared components and tokens.
- Review the build. Review builds in staging and pair on fixes.
Suggested answer structure
- State your approach in one sentence.
- Walk through the steps or criteria you use.
- Give a real example from your work.
- Say how you measure whether it worked.
Common mistakes
- Handing over only the happy path.
- First seeing the build after release.
Likely follow-up questions
- What do you do when a developer says a design is too hard to build?
- How do you document interactions and animations?
Example strong answer
I involve developers early — in kickoff and early sketches — so feasibility issues come up before details are polished. My handoff covers more than the happy path: empty, loading and error states, long text and edge cases, responsive behaviour, and focus and keyboard behaviour, annotated in the file. I use our design system's components and tokens, so most of the UI maps to existing code. During the build I stay available for questions, and I review the work in staging, logging issues by importance rather than nitpicking pixels. If something is too costly, I'd rather find a simpler design together than insist on the original.
9.
Walk me through a project in your portfolio you're proud of.
IntermediateBehaviouralPractise this question and get feedbackWhat the interviewer is evaluating
Storytelling, your specific contribution and impact.
Key points a strong answer covers
- Context & problem. The context and the problem.
- Your role. Your specific role.
- Process & decisions. Key decisions and why.
- Outcome. The measurable outcome.
- Reflection. What you learned.
Suggested answer structure
- Situation — one or two sentences of context.
- Task — what you were responsible for.
- Action — what you did, step by step (say “I”).
- Result — what changed, with a number if you can back it up.
- Reflection — what you learned or would do differently.
Common mistakes
- Showing only final screens without the reasoning.
- Saying 'we' throughout, hiding your contribution.
Likely follow-up questions
- What would you do differently?
- What was the hardest trade-off?
Example strong answer (a fictional story — use your own)
I redesigned the appointment booking flow for a physiotherapy clinic network, where 38% of people started booking online but gave up. I was the only designer, working with a PM and three engineers. Analytics and session recordings showed people dropping at the practitioner step — they didn't know whom to choose — so I interviewed six patients and found they cared about the soonest slot near them, not the person. I tested two prototypes; the one that led with 'first available near you' won clearly. The trade-off was that some clinics wanted to promote specific practitioners, so we kept that as a filter. After launch, completion rose from 62% to 79% in two months. Next time I'd involve clinic staff earlier.
Ready to answer them out loud?
Run a timed ui/ux designer mock interview, type or speak your answers, and get a score breakdown with what to improve.