Interview questions in Design & UX
What is the primary purpose of UX research before starting development?
Tests if you see pre-dev research as risk reduction. Strong answer: it validates real user needs before code, exposes unknown requirements while changes are cheap, and avoids building for imaginary users.
What is a design system's purpose and how does it enforce consistency?
This tests if you see a design system as a single source of truth for design, not just a UI kit. A strong answer cites components and style guides that standardize output. Calling it only a Figma file without developer adoption is a red flag.
What is a design system and its primary engineering components?
Tests if you treat design systems as engineering infrastructure, not just UI kits. Strong answers cite reusable coded components, design tokens, documentation, and governance as the core. Red flag: calling it just a component library or style guide.
Outline README sections for a migration CLI and explain persuasion
Tests information architecture and developer persuasion. Strong answers sequence: hook, one-line install, runnable quickstart, comparison table, then config. Front-loads time-to-value and tackles migration pain.
Explain qualitative vs quantitative user data with engineering examples
Contrast the two modes and give one example per type.
Explain UI feedback and implement immediate feedback for API calls
Define feedback as real-time state communication; describe optimistic UI or spinners resolving to success or error after the API call.
Component library vs style guide vs design system
A design system is holistic parent for scale; a style guide is a narrow visual/content child; a component library is a coded child of reusable UI elements.
How would you apply progressive disclosure to UI copy and tooltips?
Tests tiering copy by expertise. Good answers: show plain labels and short tooltips for common tasks; hide advanced settings, risks, and edge-case definitions behind expanders or secondary sheets. Red flag: dumping all help text inline to eliminate clicks.
How does UX research integrate into a two-week agile sprint?
This tests if you see research as ongoing discovery, not a predev phase. A good answer covers backlog work across sprints, outcome-based prioritization, and engineer touchpoints in refinement. Red flag: saying research happens only before coding starts.
How would you show system status during a multi-megabyte file upload?
Tests turning Nielsen's heuristic into concrete frontend patterns for uncertain waits. Cover granular progress like percent and bytes, distinct states for upload versus processing, time estimates, and error recovery.
What are the main benefits of consuming a design system?
Cite tokens for theming, isolated components, live docs, and designer collaboration.
How would you document a destructive API endpoint safely?
This tests balancing legal safety and usability for irreversible API operations. Strong answers use signal words like WARNING, direct imperatives, and distinct formatting. Red flag: vague phrases like 'be careful' or burying warnings in prose.
Generative versus evaluative research: when to use each
Generative precedes design to find needs; evaluative follows a build to test it.
How do you apply progressive disclosure and hierarchy in complex data tables?
This tests layered UI decomposition. Strong answer: default to essential columns with horizontal dividers; disclose sort and filter on interaction; paginate at 48-56px row height; apply contrast and color cues sparingly.
How would you build a design system business case for leadership?
Audit inefficiencies with metrics, map the pitch to stakeholder priorities like ROI and velocity, and contrast build cost with projected savings.
Write a conventional commit for a non-US date sorting bug
Pick fix(locale): imperative subject; body explains root cause, impact, and SemVer mapping.
Structuring release notes for breaking API changes
Lead with a summary and why, group breaking changes with before/after migration steps, give deprecation timelines and an upgrade path.
Describe a lightweight research method to validate a feature with no researcher
What it tests: bootstrapping validation without research headcount. Answer outline: unmoderated concept tests or concierge MVPs; behavioral vs attitudinal data; lightweight recruiting. Red flag: shipping A/B tests or using only internal opinions.
How does affordance guide choosing a native button over a styled div?
This tests if you see affordance as built-in behavior, not only looks. A strong answer picks the native button for free keyboard, focus, and reader support, noting a div needs tabindex, role, and keydown logic. A red flag is treating it as purely visual.
What are design tokens and why standardize them?
Tests whether you treat tokens as API contracts between design and engineering. Strong answers define platform-agnostic decisions, cite W3C DTCG spec for cross-platform codegen, and note aliasing prevents drift.
We are hiring for this. Every open role lists the topics its interview covers, so you can prepare for the real thing rather than guessing.
See open roles