Interview questions in Design & UX, page 8
Storybook's role in design system infrastructure
Isolated development, living documentation, visual and interaction testing, shared review surface.
Advocate for generative research over a complex feature request?
Tests mapping research methods to product risk. Strong answers reframe the feature as an unvalidated problem, cite qualitative behavioral methods like field studies, and translate unknowns into scope and opportunity cost.
Explain Figma Smart Animate's core principle and layer matching requirements
Tests Figma's layer-matching logic for prototyping. Great answers cover: name-based matching between frames, compatible layer types, and interpolated properties like position and size.
How would you engineer pSEO templating and data integration to prevent duplication?
Architecting data-templating pipelines that enforce genuine uniqueness at scale. A strong answer hits modular variable-rich blocks, canonical and noindex guardrails, and similarity monitoring.
CSS-in-JS vs pre-compiled CSS for distribution
Runtime cost and dynamic theming of CSS-in-JS versus cacheability and SSR simplicity of static CSS.
What lightweight generative research reveals why users drop off a funnel?
Tests bridging analytics to qualitative insight fast. Outline: run 5-8 micro-interviews at the exact drop-off step; probe confidence and expectations; map findings to technical fixes.
Build a reusable checkbox with unchecked, checked, and hover states
Tests Figma interactive components. Answer: create a component set with unchecked, checked, and hover variants; wire them with Change to actions using On click and While hovering triggers.
Describe how you'd implement an A/B test for a landing page headline
Mention deterministic bucketing, anti-flicker rendering, tracking with variant IDs, and sample-size planning.
Monorepo vs polyrepo for a design system
Atomic cross-package changes and shared tooling versus build orchestration, caching, and versioning complexity.
How do you adapt contextual inquiry for internal API and tool design?
This tests applying ethnographic methods to API design by observing engineers at work, surfacing invisible habits, and mapping findings to endpoint granularity and docs. A red flag is treating internal users as unlike external customers or using only surveys.
How would you prototype fixed header, footer, and scrollable content?
Make content taller than frame, enable Clip content and vertical overflow, then fix header and footer.
How would you instrument a CTA button and describe its event payload?
This tests basic event instrumentation and payload design. Mention a click listener, a gtag call with an event name, and parameters like button_text and page_path. A red flag is a bare event name with no parameters or mixing pageviews and clicks.
Releasing a breaking change without forcing upgrades
Ship a major bump, keep the old major published, document migration, automate with Changesets.
Usability vs A/B testing: when should engineers advocate for each?
Tests qualitative versus quantitative UX methods. Outline: usability observes why users struggle and finds bugs; A/B compares live variants to optimize conversions. Choose usability for unknown friction, A/B for known tweaks.
Steps to publish color and text styles to a Figma shared library
Open Publish in the right panel, select color and text styles, add a version note, publish; teammates enable the library.
How would you architect personalized email and coupon delivery at scale?
This tests decoupled rendering and atomic coupon reservation. A strong answer uses template rendering, atomic coupon reservation, an idempotent queue, and batched ESP delivery. Red flag: generating coupons during SMTP without reservation risks overspend.
Bundling a library for tree-shaking and multiple formats
Externalize peers, emit ESM and CJS, preserve modules for tree-shaking, set sideEffects false, ship types.
Describe heuristic evaluation and two heuristics that guide UI components
Tests if you bridge UX research and frontend decisions. Define heuristic evaluation as expert review against rules of thumb, cite two NN/G heuristics, and map each to a concrete component behavior. Red flag: listing heuristics without code impact.
How do you handle versioning and breaking changes in a shared library?
This tests bridging design and engineering workflows. A strong answer covers semantic versioning, a protected main file with branching, a visible changelog, and release alignment with code.
A/B test copy in a native app without app store releases
Tests native release friction versus web. Strong answers cite app store review, binary caching, and stale config; then remote fetch, local defaults, and user targeting. A red flag is assuming updates are instant like the web.
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