Intermediate interview questions in Design & UX, page 4
Design a content gap tool: data sources and core logic
Tests system design for SEO pipelines. Strong answers cite APIs (Ahrefs, Semrush, GSC), explain normalization, and frame logic as a left-anti-join on keyword plus geo and device filtered by rank. Red flag: dismissing API cost, rate limits, and freshness.
How do you mitigate confirmation bias when a user validates your solution?
In the moment, probe for exceptions; in synthesis, triangulate and invite reviewers.
How would you use a journey map to find technical root causes?
Map journey stages to logs and traces, find bottlenecks, propose API or data model changes.
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.
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.
Monorepo vs polyrepo for a design system
Atomic cross-package changes and shared tooling versus build orchestration, caching, and versioning complexity.
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.
Releasing a breaking change without forcing upgrades
Ship a major bump, keep the old major published, document migration, automate with Changesets.
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.
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.
Syncing design tokens from Figma to code
Export Figma variables to a token spec, transform with Style Dictionary into platform outputs, automate via CI.
Explain a conversion pixel, click-to-signup flow, and failure points
Tests cross-session attribution state. Strong answers trace the GCLID from URL parameter to cookie or local storage, then to the conversion tag, plus list failure modes like ITP, ad blockers, and race conditions.
Diagnose and validate a failing usability task
Pinpoint the failure step from session and telemetry data, form a root-cause hypothesis, ship a targeted fix, and re-test to validate.
How would you track multiple CTAs to the same conversion goal?
Tests granular event attribution beyond aggregate counts. A strong answer uses unique data attributes per CTA, routes clicks through GTM into GA4 events, and ties them to the conversion. Red flag: relying only on destination URLs, which fails if paths match.
How could you adapt usability testing principles to evaluate two API designs?
Tests holistic API UX beyond static syntax. Strong answers propose observing developers in realistic IDE and doc contexts, noting errors and confusion across both designs.
What usability metrics would you instrument, and how do regressions drive priorities?
Tests operationalizing UX into engineering signals. Strong answers list success rate, time on task, and error rate; triage regressions by criticality; and pair quant drops with qual diagnosis. Red flag: calling every regression P0 or using vanity metrics.
Design the keyboard interaction flow for a modal dialog
Your grasp of accessible focus management per WAI-ARIA dialog patterns. Cover initial focus rules, Tab trapping inside the modal, Escape to close, and restoring focus to the trigger on exit.
Designing and documenting focus order in Figma
Focus order is the sequence keyboard and screen-reader users traverse interactive elements; it should follow meaning and reading order, documented in Figma via layer order, numbered annotations…
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