Easy interview questions in Design & UX, page 4
How do you restore one component from Figma version history?
Tests whether you know version history is file-level. Answer: open the file name menu, show version history, find the ~1h autosave, duplicate it to a new file, copy the component, paste back. Red flag: restoring the entire old version and losing later work.
Deciding whether a one-off variant belongs in core
Weigh reuse and consistency against maintenance cost, then decide with a shared-need bar and escape hatches for local cases.
Purpose and key sections of CONTRIBUTING.md
It documents how to contribute; key sections are setup and dev workflow, contribution process and standards, and review and release expectations.
Create a counter where clicking '+' increases the number by one
Tests Figma number variables and Set variable action. Use a number variable on the text, then add an On click trigger on the plus button with Set variable and an expression to add one. Red flag: using duplicate frames instead of a single dynamic variable.
Mean, median, and mode: which measure for task completion times?
This tests whether you know task times are skewed and sample size drives the mean-versus-median choice. A strong answer cites the under-25 rule, contrasts mean outlier sensitivity with median robustness, and dismisses mode. Red flag: defaulting to the mean.
Explain what a p-value represents in an A/B test and interpret 0.03
This tests frequentist hypothesis testing literacy. It is the chance of seeing a result this extreme if the null of no effect were true; 0.03 means 3% chance of such data under the null, not 97% chance the variant wins. Red flag: saying 97% likely.
Bug report to deployed fix workflow
Triage and reproduce, write a failing test, fix it, pass CI gates and review, then patch-release and notify.
Are 1-5 satisfaction ratings continuous or discrete?
Tests knowledge of measurement scales. A strong answer calls 1-5 ratings discrete and ordinal, notes intervals may be unequal, and prefers medians or non-parametric tests over means unless equal spacing is defensible.
Why use button variants instead of separate components per state?
Tests Figma component set organization and scalability. Strong answers cite flexible property mixing, reduced combinatorial bloat, and cleaner dev handoff. Red flag: saying only "it's cleaner" without naming navigability or system integrity.
Essential docs for onboarding a new team
Getting-started guide, per-component API and usage docs, design guidelines and tokens, plus changelog and migration notes.
How would you use Auto Layout to build a responsive card?
Tests Figma Auto Layout direction, padding, and resizing rules. Answer: stack header, image, and text vertically with a fixed gap; set text to fill width and hug height; wrap in a scaling frame. Red flag: absolute positioning instead of structured Auto Layout.
Design a database schema for an ad A/B test
Tests separating high-volume events from slow-changing experiment metadata. Strong answer: distinct tables for variants, impressions, and clicks; clicks link to impressions; a user-assignment table avoids duplicating variant data per event.
Programmatically create an ad via a marketing API
Authenticate, create a campaign with an objective, an ad set with budget and targeting, a creative with the copy, then the ad linking them.
Tracking design system adoption technically
Scan codebases for component imports via AST, compute adoption versus off-system usage, and aggregate into a dashboard over time.
Design a simple templating system for ad copy generation
Tests separation of concerns and API design. A good answer: data model separate from template, placeholder syntax, graceful missing-value handling, and HTML escaping. Red flag: naive string concatenation without validation or extensibility.
First technical questions to scope a journey-map pain point
Ask how widespread and severe it is, where in the system it originates, and what constraints bound a fix.
What's the functional difference between wireframes, mockups, and prototypes? Describe a scenario.
This tests whether you distinguish structure, visuals, and interactivity. A strong answer defines each by fidelity and function, then names a lifecycle stage like using wireframes in discovery to align scope before visual design.
SemVer bump for a non-breaking bug fix
A backward-compatible bug fix is a PATCH, the third number; major is breaking, minor is new compatible features.
Design a database schema for a research participant panel
Your ability to normalize relational data without over-engineering. Propose a participants table for contact and demographics; a participation_history table with foreign keys; and a consent_log table.
First steps to deprecate a legacy component
Add a JSDoc @deprecated tag and IDE/console warning, document the migration, and keep the component working.
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