Advanced interview questions in Design & UX, page 3
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.
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.
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.
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 do you migrate a breaking change in a mature design system?
This tests organizational change management at scale, not just code changes. A strong answer covers SemVer major versioning, beta testing with key consumers, phased deprecation timelines, and automated file audits.
Building a visual regression testing pipeline
Snapshot Storybook stories per PR, freeze nondeterminism, set diff thresholds, manage baselines via approvals.
Minimizing library bundle-size impact on consumers
Track size in CI with size-limit, support granular imports, externalize peers, lazy-load heavy parts, audit with bundle analyzers.
Architect a real-time multi-armed bandit and compare trade-offs to A/B testing
Sketch a fast arm router, streaming feedback, and model updates; contrast MAB regret minimization with A/B's unbiased estimates.
Caching and performance challenges in SSR with personalized copy
Segment-level cache keys, short TTLs with stale-while-revalidate, and edge personalization to protect origin.
How would you triage 50+ UX issues against new features in agile?
Matrix the 50 issues by severity and effort; reserve 15-20% sprint capacity for debt; socialize compound cost.
Design a centralized Copy Service with versioning, segmentation, and experiments
This tests separation of editorial workflow from runtime delivery. A strong answer covers immutable versioned records, a resolution API evaluating segmentation rules, and delegating experiment bucketing externally.
How do you architect an automated performance and accessibility testing pipeline?
This tests operationalizing quality gates via automation, not manual checks. A strong answer covers Lighthouse CI in CI/CD, fail thresholds for CWV and WCAG, and a triage workflow assigning regressions to owners.
Adapting CSS for Forced Colors Mode
Use semantic HTML and system color keywords, the forced-colors media query, forced-color-adjust sparingly.
Detect a three-action user sequence in real-time at scale
Tests stream processing and stateful pattern matching on unbounded data. A strong design uses a CEP engine with keyed event-time windows, pushes alerts via WebSocket, and trades state-memory for latency.
Shadow DOM accessibility: focus and cross-boundary ARIA
IDREF ARIA can't cross the shadow boundary, so aria-labelledby and aria-activedescendant break; delegatesFocus and ElementInternals/ARIAMixin help.
Architect a secure draft preview system for a headless CMS
It tests safe headless CMS draft previews on production frontends. A strong design uses authenticated preview APIs, SSR middleware with JWT sessions, CMS preview tokens, and cache-busting. Relying on obfuscated URLs or disabling preview auth is a red flag.
Design a programmatic SEO landing-page system
Structured data plus templates, genuinely unique per-page data, static build-time generation, quality gates and indexation control.
Limitations of Figma Dev Mode generated code
Dev Mode output is static, absolute-positioned, non-semantic, and ignores responsiveness, state, and your component system; use it for values and structure, then refactor to semantic, tokenized…
Reversing stagnating design system adoption
Find friction via interviews, reduce it with DX, codemods, and docs, then prove value with adoption and velocity metrics.
How would you extract Figma Variables via REST API for Style Dictionary?
Tests Figma Variables to Style Dictionary architecture. Outline: paginate REST endpoint, map modes/aliases to W3C draft JSON, then run Style Dictionary in CI from tokens folder. Red flag: raw API payloads without type normalization or alias resolution.
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