Top 30 Design & UX Interview Questions and Answers
30 multiple-choice questions on Design & UX, of the kind that come up in a technical interview, drawn from 30 bites in the Design & UX library. Answer them here or read straight down. Every question carries the correct option, why it is correct, and a link to the bite it came from.
UI design, UX research, and design systems
30 questions. Pick an answer, or open “Show the answer” to read it.
Answers are graded in your browser. Nothing is saved, and no XP or streak is earned here. The app keeps score.
Question 1 of 30
Which statement best describes the primary engineering purpose of conducting UX research before development begins?
Show the answer
Answer: b · It validates real user needs and exposes unknown requirements while changes are still cheap.
Pre-development UX research is fundamentally an engineering risk-mitigation tool that validates real user needs and uncovers unknown requirements before code is written, when changes are cheapest. Option D is tempting because prototype testing is valuable, but the card explicitly states that the primary purpose of pre-development research is discovery and alignment, not post-hoc validation.
Read the full bite: What is the primary purpose of UX research before starting development?
Question 2 of 30
Which of the following best describes how a design system enforces consistency at scale?
Show the answer
Answer: b · It integrates reusable coded components, design tokens, and documentation across both design tools and code repositories
A design system enforces consistency by uniting coded components, tokens, and documentation across design and engineering, not just through design assets. Calling it merely a shared Figma file is a common misconception because it misses the engineering adoption and version-controlled code that actually standardizes implementation.
Read the full bite: What is a design system's purpose and how does it enforce consistency?
Question 3 of 30
What key elements elevate a component library into a full design system?
Show the answer
Answer: a · Reusable coded components, design tokens, documentation, and governance processes
A design system is engineering infrastructure that combines reusable components with design tokens, documentation, and governance. Option B describes only a mature component library, which is a common misconception that omits the tokens, docs, and processes required for a true system.
Read the full bite: What is a design system and its primary engineering components?
Question 4 of 30
Why should a migration CLI README place a comparison table against alternatives before the detailed configuration reference?
Show the answer
Answer: a · Developers evaluating tools need to justify switching costs before they will invest time learning configuration details
Developers must understand competitive differentiation and justify switching before investing in configuration details, matching the attention-to-trust adoption funnel. Option C raises a valid docs concern but misattributes the ordering rationale, since the sequence serves persuasion rather than maintenance ease.
Read the full bite: Outline README sections for a migration CLI and explain persuasion
Question 5 of 30
Which approach best follows Nielsen's visibility of system status heuristic when handling a button-triggered API call?
Show the answer
Answer: a · Disable the button with a spinner, then transition to success or error states based on the API result
The card describes proper feedback as immediate local changes like a disabled button with a spinner, followed by resolution to success or error states. Waiting until the API responds leaves the user staring at a frozen screen, which violates the visibility of system status heuristic.
Read the full bite: Explain UI feedback and implement immediate feedback for API calls
Question 6 of 30
Your team needs to understand why developers rarely use a new CLI flag. Which method produces qualitative user data?
Show the answer
Answer: b · Sitting with developers as they run commands and narrate their thought process
Sitting with developers as they narrate their thought process is qualitative because the researcher is directly observing and listening to behaviors and attitudes. An open-ended questionnaire is a tempting distractor because it relies on an instrument and confuses question format with the direct-versus-indirect distinction.
Read the full bite: Explain qualitative vs quantitative user data with engineering examples
Question 7 of 30
Which approach best demonstrates progressive disclosure applied specifically to UI copy and tooltips?
Show the answer
Answer: d · Use short tooltips for common cases and hide advanced details behind clearly labeled expanders or secondary sheets
Option D correctly applies progressive disclosure by splitting primary tooltips from secondary details, which reduces cognitive load and error rates for novices while keeping experts efficient. Option B is tempting but wrong because dumping all help text inline eliminates clicks at the cost of overwhelming novices with irrelevant details.
Read the full bite: How would you apply progressive disclosure to UI copy and tooltips?
Question 8 of 30
A team documents brand colors and voice, yet engineers rebuild every button from scratch. What best describes their design infrastructure?
Show the answer
Answer: b · They have a style guide but lack the coded reusable components and cross-team workflow of a full design system.
Documented colors and voice rules fit the narrow scope of a style guide, while the absence of production-ready, reusable code means they are missing the component library and holistic standards that define a design system. The most tempting distractor assumes a style guide alone constitutes a complete design system, but the card emphasizes that a design system must also include coded components and shared workflows.
Read the full bite: Component library vs style guide vs design system
Question 9 of 30
A team is running a usability study across three two-week sprints. How should this research work be managed in the product backlog?
Show the answer
Answer: a · Maintain one backlog item across all three sprints, marking individual tasks done as they are completed.
The card emphasizes that research should live as a single backlog item that stays open across sprints while bite-sized tasks are completed, making B correct. Option D is tempting because it follows strict sprint boundaries, but forcing a research story closed at sprint end regardless of study status is explicitly flagged as a common mistake.
Read the full bite: How does UX research integrate into a two-week agile sprint?
Question 10 of 30
During a 10 MB video upload that requires server processing after transfer, which frontend approach most effectively prevents abandoned sessions and duplicate submissions?
Show the answer
Answer: a · A determinate progress bar with percentage and bytes transferred, explicit phase labels for uploading and processing, dynamic time estimates, and chunked error recovery offering retry or resume
Option A is correct because it combines granular progress, distinct phase labels, dynamic time estimates, and resilient error handling to close the gulf of evaluation. Option D is tempting because it shows a progress bar and prevents duplicate clicks, but it wrongly conflates the network transfer with overall completion and hides server-side processing from the user.
Read the full bite: How would you show system status during a multi-megabyte file upload?
Question 11 of 30
Which scenario best illustrates a design system delivering value beyond a simple UI kit?
Show the answer
Answer: b · Updating a single color token automatically updates every component across all consuming apps without modifying any product code.
This reflects the card's concrete example where design tokens decouple visual decisions from product code, enabling safe cross-app theming. Option D is tempting because it mentions consistency and shared code, but it reduces the system to a CSS framework and ignores tokens, living docs, and workflow integration.
Read the full bite: What are the main benefits of consuming a design system?
Question 12 of 30
Which documentation strategy best protects both users and the business for an API endpoint that triggers irreversible data loss?
Show the answer
Answer: b · Use a distinct WARNING admonition that names the hazard, states the consequence, and gives an escape route using direct imperatives.
A distinct WARNING admonition following the SAFE method—Signal, Hazard, Consequence, Escape—applies the correct severity level for irreversible data loss and uses direct imperatives that are legally defensible and actionable. Option D is tempting but wrong because DANGER is reserved for life-threatening scenarios, and over-warning desensitizes developers while diluting the impact of truly critical alerts.
Read the full bite: How would you document a destructive API endpoint safely?
Question 13 of 30
After releasing an MVP export feature, a team wants to know if users can successfully complete exports. Which research approach fits best?
Show the answer
Answer: b · Measuring task success and observing friction while users try the export flow
Once an MVP exists, evaluative research such as usability testing measures task success and solution fit. Observing how reports fit into workflows is a generative method meant to uncover needs before design begins, so it does not validate whether the new export flow actually works.
Read the full bite: Generative versus evaluative research: when to use each
Question 14 of 30
Which approach is most effective for securing leadership buy-in when proposing a new design system?
Show the answer
Answer: a · Audit current inefficiencies with metrics, tailor benefits to each stakeholder's priorities, and contrast total investment including maintenance against projected savings.
The card stresses that a credible business case requires audited inefficiencies, stakeholder-specific pitches, and honest costing that includes maintenance. Option D is tempting because it mentions business benefits, but it ignores stakeholder segmentation and severely underestimates the required investment, which destroys credibility with leadership.
Read the full bite: How would you build a design system business case for leadership?
Question 15 of 30
Which conventional commit best documents a fix for a date sorter that incorrectly assumed US locale formats?
Show the answer
Answer: c · fix(date-parser): handle locale-aware date sorting with body noting the previous hardcoded US locale assumption
Option C correctly uses the fix type and date-parser scope, an imperative subject, and a body that explains the root cause to prevent future regressions. Option D is a tempting distractor because the change does add locale logic, but feat signals a minor SemVer bump and misrepresents a bug patch.
Read the full bite: Write a conventional commit for a non-US date sorting bug
Question 16 of 30
Which implementation best applies progressive disclosure and hierarchy in a complex data table with thousands of rows?
Show the answer
Answer: c · Default to essential columns with horizontal dividers at 48px, reveal sorting and filtering on hover or behind triggers, and reserve color cues for large datasets or status indicators.
Option C reflects the recommended layered strategy: a calm default view with essential columns and horizontal dividers at 48px, controls disclosed on interaction, and color used sparingly. Option A is tempting because it includes progressive disclosure patterns like a column picker and hover-revealed filters, but it incorrectly applies 56px to every dataset regardless of density and wrongly left-aligns numeric counts that should be right-aligned for scannability.
Read the full bite: How do you apply progressive disclosure and hierarchy in complex data tables?
Question 17 of 30
What single element most reduces churn when documenting a breaking API change for developers?
Show the answer
Answer: d · Concrete before-and-after migration steps for each breaking change
Developers churn when they cannot see how to fix their code; explicit before-and-after migration steps give a direct, actionable path. A celebratory tone or hiding the old behavior leaves users stranded and increases frustration.
Read the full bite: Structuring release notes for breaking API changes
Question 18 of 30
In a multi-platform design system using the W3C DTCG format, what is the primary purpose of aliasing semantic tokens to core tokens?
Show the answer
Answer: c · To reduce maintenance overhead by updating a single core value that propagates across themes and platforms
Aliasing establishes relationships where semantic and theme tokens reference a single core value, so a brand update automatically propagates across all platforms and themes without duplicated source files. Distractor D is tempting because teams often assume each platform needs its own token file, but that approach creates drift and maintenance overhead that aliasing is specifically meant to prevent.
Read the full bite: What are design tokens and why standardize them?
Question 19 of 30
Which factor does the concept of affordance prioritize when selecting a native button over a styled div?
Show the answer
Answer: b · Built-in keyboard support, focus handling, and screen reader semantics
Affordance centers on the built-in behavioral contracts of native elements, such as keyboard activation and screen reader announcements, rather than just appearance. Option D is tempting because developers often assume role='button' is sufficient, but that ignores the manual keyboard and focus management a div still requires.
Read the full bite: How does affordance guide choosing a native button over a styled div?
Question 20 of 30
You must validate a new feature concept without a researcher and before writing production code. Which approach best balances speed and rigor?
Show the answer
Answer: b · Run an unmoderated concept test with a low-fidelity prototype, recruiting target users in-app and measuring task success and perceived value against a preset threshold.
B is correct because unmoderated concept tests with prototypes gather both behavioral and attitudinal signals quickly without production code or dedicated research staff. A is the most tempting distractor because A/B testing feels rigorous, but it requires committing production code before validation, which defeats the purpose of lightweight de-risking.
Read the full bite: Describe a lightweight research method to validate a feature with no researcher
Question 21 of 30
Which metric pairing best demonstrates that a design system is accelerating product delivery and justifying continued investment?
Show the answer
Answer: c · High product-team adoption and low design-to-code drift
The card explicitly states that high adoption paired with low design-to-code drift correlates with faster delivery and fewer regressions, making it the strongest ROI signal. Option B is tempting because governance sounds rigorous, but the card flags manual audits as unsustainable and warns against measuring only designer adoption while ignoring engineering consumption.
Read the full bite: What metrics measure design system success and adoption?
Question 22 of 30
Which plan best demonstrates rigorous instrumentation to validate a qualitative behavioral insight?
Show the answer
Answer: c · Map qualitative themes to specific product events, define success and guardrail metrics, and compare the target cohort against a holdback with a preset minimum detectable effect
The correct approach requires traceability from themes to events, paired success and guardrail metrics, and a predefined analysis plan with a holdback cohort. Option D is tempting because A/B testing sounds rigorous, but testing the general population without linking metrics to specific qualitative themes or defining statistical power fails to validate the original insight.
Question 23 of 30
When A/B testing sign-up button copy, which practice ensures you can accurately attribute differences in sign-ups to the copy change?
Show the answer
Answer: a · Randomly assign users to variants using a hashed user ID, track impressions and conversions, and compare conversion rates
Randomizing with hashed user IDs and tracking both impressions and completed sign-ups lets you calculate a true conversion rate and establish causality. Sequential testing introduces temporal bias because traffic composition and external factors differ between weeks, invalidating the comparison.
Read the full bite: How would you A/B test sign-up button copy and measure results?
Question 24 of 30
Which implementation pattern best preserves a wizard's low cognitive load while keeping branching logic and back-button behavior maintainable?
Show the answer
Answer: b · Isolated step components that each own their validation, orchestrated by a state machine that syncs the current step to the URL and commits valid drafts to a central store.
C is correct because it pairs progressive disclosure with isolated validation, URL-synced navigation, and explicit state management exactly as the card recommends. A is the most tempting distractor because consolidating state feels simpler, but it collapses under branching logic and creates messy validation boundaries.
Read the full bite: How do you design a low-cognitive-load wizard and implement it technically?
Question 25 of 30
A team's current approach to keeping PII out of logs is to log full request and response bodies as usual, then run a nightly job that scans old logs and deletes lines matching an email regex. What is the main weakness of this approach?
Show the answer
Answer: d · It leaves PII sitting in logs until the nightly job runs, and regex scrubbing after the fact commonly misses fields it was not written to catch
Logging everything first leaves PII exposed in plaintext for up to a full day, and after the fact regex scrubbing routinely misses fields that do not match the pattern, so this is not equivalent to never logging it at all. The stronger control is preventing sensitive fields from being logged in the first place, not cleaning up after exposure.
Read the full bite: What is PII and how to keep it out of logs
Question 26 of 30
Which approach best implements click tracking for dozens of headlines and CTAs while remaining performant and maintainable?
Show the answer
Answer: b · Use a single delegated listener on a parent container, read data attributes to identify elements, and send via navigator.sendBeacon
Event delegation on a common ancestor avoids the performance cost of dozens of individual listeners and naturally handles dynamic content, while data attributes provide stable identifiers unlike brittle innerText or class names. The most tempting distractor, attaching unique listeners to every element, scales poorly and misses the efficiency and dynamic-content benefits that delegation provides.
Read the full bite: How would you track clicks on headlines and calls-to-action?
Question 27 of 30
When proposing governance for a centralized design system across legacy silos, which approach best balances standardization, team autonomy, and migration cost?
Show the answer
Answer: c · A hybrid model where a core team owns primitives and standards, distributed teams own framework-specific implementations, and legacy stacks adopt incrementally via design tokens.
The hybrid model correctly balances centralized standards with distributed implementation, using tokens to bridge legacy stacks without forcing immediate rewrites. The fully centralized mandate in Option B is tempting because the system is described as centralized, but it ignores migration costs and kills buy-in by removing team autonomy.
Read the full bite: What governance model would you propose for a centralized design system?
Question 28 of 30
A product manager insists on a custom component that violates the design system. Which response best articulates the long-term debt cost?
Show the answer
Answer: d · Model the 3-5x post-launch refactor multiplier, attach a risk matrix, and propose a time-boxed experiment with hard deprecation
Modeling the 3-5x refactor multiplier, attaching a risk matrix, and proposing a time-boxed experiment reflects the card's four-layer framework for stakeholder translation. Distractor A is tempting because it enforces the design system, but the card flags demanding an immediate full refactor without acknowledging delivery pressure as a red flag.
Read the full bite: How do you model and articulate long-term design debt cost to stakeholders?
Question 29 of 30
A product team requests a custom Button for a high-visibility landing page. Which response best demonstrates mature design system governance?
Show the answer
Answer: c · Ask context questions about user flow, apply a decision tree, and document the outcome as a pattern alignment or new variant.
The correct approach first investigates context and maps the request to existing patterns via a decision tree before documenting any new variant, balancing velocity with integrity. The most tempting distractor is adding the Button to the system immediately without guidelines, which appears helpful but merely delays the chaos by failing to establish reusable standards.
Read the full bite: How do you handle a product team requesting a custom Button?
Question 30 of 30
When merging anonymous analytics events with CRM data to auto-segment users by persona, what identity handling step best distinguishes a robust architecture from a fragile one?
Show the answer
Answer: d · Ingest both sources into common storage, then stitch anonymous IDs to CRM identifiers using deterministic or probabilistic matching while maintaining confidence scores
The correct answer treats identity resolution as a first-class problem by linking anonymous and known IDs with confidence scoring, preserving pre-authentication behavior. Option B is the most tempting distractor because joining on email seems straightforward but ignores anonymous users, data quality issues like typos, and merge conflicts.
Read the full bite: How to merge analytics and CRM data to auto-segment users by persona
Could you explain these out loud?
That is what an interview actually tests. Tezvyn gives you questions like these with what the interviewer is really checking, the answer that lands, and the mistake that ends the conversation, in the four minutes before your next meeting.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.