Interview guide
UI/UX Designer Interview Questions & Answers Guide (2026)
A hiring-manager’s interview kit for ui/ux designers — with specific “what to look for” notes on every answer, red flags to watch, and a practical test.
Key facts
- Role
- UI/UX Designer
- Technical questions
- 15
- Behavioral
- 7
- Role-fit
- 5
- Red flags
- 8
- Practical test
- Included
How to use this guide
Pick 4-6 technical questions across difficulties, 2-3 behavioral, and 1-2 role-fit for a 45-minute interview. For senior roles, weight harder technical and role-fit higher. Always close with the practical test so you are hiring on evidence, not impressions. The “what to look for” notes are a scoring rubric: strong answers touch most points, weak answers miss them or replace them with platitudes.
Technical questions — Easy
1. Walk me through a recent flow from your portfolio — from brief to handoff. Focus on decisions and trade-offs.
EasyWhat to look for: Clear problem framing, explored options, chose one for stated reasons, specified every state, handed off cleanly. Not just screens. Red flag: skips states and only shows the happy path.
2. Show me a Figma file. How is it organized?
EasyWhat to look for: Pages structured (Cover, Explorations, In Review, Approved, Shipped, Archive), frames named, auto-layout used, components from library, variants for states, variables for tokens. Messy file = real signal.
3. Explain WCAG 2.2 AA color contrast and how you verify it in Figma.
EasyWhat to look for: 4.5:1 for normal text, 3:1 for large text and UI components. Uses Figma plugins (Stark, Able, Contrast) or manual ratio check. Does not guess.
4. How do you hand off to engineering through Figma Dev Mode?
EasyWhat to look for: Clean Dev Mode setup with variables linked, spec notes, interaction annotations, Loom for complex flows, Linear/Jira ticket per screen. Does not just link the Figma URL.
Technical questions — Medium
1. How do you design for loading, empty, and error states?
MediumWhat to look for: Treats them as first-class per screen: skeleton for load, teaching empty state, error with recovery path. Not "I add them at the end if there is time."
2. Walk me through how you decide between a modal, a drawer, and a full-page for a flow.
MediumWhat to look for: Specific heuristics: context preservation, step count, mobile behavior, destructive vs neutral action. Not "it depends."
3. How do you design keyboard navigation into a custom component?
MediumWhat to look for: Defines tab order, focus visible state, arrow-key patterns for composite widgets (menu, tabs, listbox), escape to dismiss modals. References ARIA Authoring Practices.
4. Walk me through extending a design system with a new component without breaking it.
MediumWhat to look for: Checks if need is real (reuse across surfaces), proposes with specs and states, files with the DS maintainer, documents variants and use cases. Does not build one-off.
5. How would you script a moderated usability test for a checkout flow?
MediumWhat to look for: Warm-up questions, scenario-based tasks in the user's own context, think-aloud prompting, no leading questions, debrief. 45-minute structure, 5–8 participants, recorded with consent.
6. What is the difference between your role and a Product Designer?
MediumWhat to look for: Honest: Product Designer owns product strategy + research + UI end-to-end; UI/UX executes flows within defined strategy. Knows they are not claiming the strategy layer.
7. Explain Nielsen's usability heuristics and how you use them in critique.
MediumWhat to look for: Names at least 5–6 (visibility of system status, match to real world, user control, consistency, error prevention). Applies them in design reviews with specific examples.
Technical questions — Hard
1. How do you design a data table that handles 10k rows, sorting, filtering, and inline editing?
HardWhat to look for: Virtualization, sticky header + first column, clear filter/sort UI, bulk-select patterns, inline edit with optimistic save and rollback, keyboard support.
2. Explain design tokens and how you would sync them from Figma to code.
HardWhat to look for: Color, type, spacing, radius, motion tokens in Figma variables. Synced via Tokens Studio or Style Dictionary to JSON/CSS/Tailwind config. Engineers consume from code, not by copying hex codes.
3. A usability test shows 60% task completion but SUS of 48. What do you do?
HardWhat to look for: Re-watches recordings for friction moments, interviews dissatisfied participants, iterates on specific pain points, retests. Does not just tweak visuals.
4. How do you design for dark mode without making it an afterthought?
HardWhat to look for: Semantic tokens (surface, text-primary) not hex codes, contrast verified in both modes, avoids pure black, tests real screens. Understands semantic naming.
Behavioral questions
1. Tell me about design feedback that felt unfair at the time.
What to look for: Listened first, looked for the real concern, iterated or pushed back with rationale. Not defensive. Not a doormat.
2. Describe a time you shipped a flow and usability testing showed it did not work.
What to look for: Specific issue, honest diagnosis, iterated, retested. Comfortable with negative results.
3. Tell me about collaborating with an engineer who pushed back on a design.
What to look for: Respects engineering constraints, separates craft from constraint, negotiated alternative. Did not say "that is their problem."
4. Walk me through a time you advocated for usability testing when no one asked for it.
What to look for: Proposed a scoped test (5 users, 2 days), ran it quickly, showed impact, built a habit. Not a 6-month research project.
5. Describe your process for design critique — giving and receiving.
What to look for: Specific, structured (What is the problem? What are the options? Why this one?), uses heuristics, receives without defensiveness.
6. Tell me about mentoring a junior designer.
What to look for: Specific examples — Figma reviews, critique guidance, helping them present. Generous posture.
7. How do you keep your craft sharp?
What to look for: Specific: follows designers, studies shipped products, Figma tutorials, redlines apps for fun, side projects. Active.
Role-fit questions
1. Are you comfortable executing flows defined by a PM or Product Designer, rather than owning strategy yourself?
What to look for: Yes with confidence — knows their craft layer. Red flag if they want strategy ownership but interviewing for an execution role.
2. How do you feel about being part of a design system rather than free-form visual design?
What to look for: Sees the system as leverage. Red flag if they resent constraints.
3. How hands-on do you want to be with research?
What to look for: Comfortable running 5–8 person tests themselves. Partners with a dedicated researcher on larger studies. Does not punt entirely.
4. How do you feel about design QA — finding spacing and color bugs in shipped builds?
What to look for: Accepts it as part of the job, has a process. Red flag if they consider it beneath them.
5. Individual contributor or eventually team lead?
What to look for: Honest answer. Either fine. Calibrates the role path.
Red flags
Any one of these alone is usually reason to pass, especially combined with weak answers elsewhere.
- • Portfolio shows only polished final screens — no wireframes, no states, no process.
- • Cannot name specific WCAG requirements.
- • Figma files with free-floating frames, detached components, inconsistent spacing.
- • Claims to own product strategy from a 2-year-experience level.
- • Never names a metric or usability result — design exists only for aesthetics.
- • Resents the design system.
- • Gets defensive under critique; interrupts feedback to explain.
- • Shows concept-only work (never shipped) as main evidence of capability.
Practical test
5-day take-home (4–6 hours of actual work, paid $150–$300). Brief: we provide an existing B2B SaaS design system (Figma library) and a one-page spec for a new flow — a multi-step form for importing CSV data with column mapping, validation errors, and a preview step. Deliverables: (1) a low-fi wireframe flow with 2 options and pros/cons; (2) high-fi Figma screens for every state (default, loading, validation error, partial success, success) using the provided design system; (3) an interactive prototype linking the happy path; (4) a short annotations page covering accessibility considerations (contrast, keyboard flow, ARIA); (5) a Loom walkthrough (5–8 minutes) explaining decisions; (6) a list of 3 usability-test questions you would ask participants. Graded on: problem framing and option exploration (20%), craft in Figma and design system fidelity (25%), interaction coverage including edge states (25%), accessibility annotations (15%), communication of rationale (15%).
Scoring rubric
Score each answer 1-4: (1) Misses most of the rubric or gives platitudes; (2) Hits some points but cannot go deep when pressed; (3) Covers the rubric and can defend the answer under follow-ups; (4) Adds unprompted nuance, trade-offs, or real examples beyond the rubric. Hire at an average of 3.0+ across technical, behavioral, and role-fit, with zero red flags, and a pass on the practical test.
Related
Written by Syed Ali
Founder, Remoteria
Syed Ali founded Remoteria after a decade building distributed teams across 4 continents. He has helped 500+ companies source, vet, onboard, and scale pre-vetted offshore talent in engineering, design, marketing, and operations.
- • 10+ years building distributed remote teams
- • 500+ successful offshore placements across US, UK, EU, and APAC
- • Specialist in offshore vetting and cross-timezone team integration
Last updated: April 12, 2026