Intermediate everything in Design & UX, page 6
Documentation for a new Card component
Usage guidance and do/don't, variants, accessibility, code examples, composition.
Design tokens for multi-brand button theming
Tokens as named design decisions, primitive-versus-semantic layers, per-brand themes mapping semantic to primitive.
End-to-end process for a Modal props API break
Justify and design the change, additive rollout with deprecation, major release plus codemod, comms and adoption tracking.
Measuring designer efficiency from Figma data
Library component usage and detach rates from Figma, time-to-mockup, override frequency via the API.
Linking form-component adoption to fewer a11y bugs
Define both variables, segment by adoption level, control confounders, watch correlation-versus-causation.
Gradual design system adoption in legacy code
Coexistence strategy, codemods for mechanical swaps, lint rules to block regressions, prioritize high-traffic surfaces.
Measuring design system adoption and health
Component coverage and version spread from code scans, usage analytics, issue and satisfaction signals.
Technical and comms plan for a Button break
Additive-first then deprecate, major semver, codemod and guide, multi-channel early comms with adoption tracking.
Critical a11y fix requiring a breaking API change
Ship a safe interim fix, plan the breaking API as a major with deprecation and codemod, communicate urgency.
Design systems across micro-frontends
Shared singletons and version alignment, token-based theming, distribution via shared scopes, stronger governance.
Governance for accessibility regressions
Detection via audits and monitoring, triage with severity and ownership, remediation SLAs, prevention feedback.
Automated a11y testing in CI and its limits
Axe-core in unit and story tests, fail the build on violations, plus manual screen-reader and keyboard testing.
Architecting a federated documentation site
Docs-as-code with a manifest, CI publishing artifacts, a build that pulls and merges, unified deploy.
Documenting accessibility per component
Per-component a11y sections, keyboard tables, ARIA roles and states, live examples.
Composite components versus layout primitives
Primitives give flexibility and composition, composites enforce consistency, choose by reuse and variation.
Rolling out a breaking change to a shared Button
Major semver bump, deprecation period, codemod and migration guide, staged comms.
Versioning and shipping design tokens via NPM
Semver, deprecate-before-delete with aliases, codemods and migration guides.
How would you track clicks on a new 'Export Data' button?
Tests prod analytics design beyond console.log. Outline: typed event schema, client validation, beacon or queue with batching, and queryable storage. Red flag: fire-and-forget tracking without retry, sampling, or privacy checks.
Outline a research plan to diagnose low adoption despite positive usability tests
Tests distinguishing usability from adoption drivers. Strong answers hypothesize discoverability, motivation, and timing gaps; use behavioral triangulation, contextual inquiry, and surveys. Red flag: blaming users or redesigning before diagnosing the funnel.
How would you secure a moderated screen-sharing session end to end?
Cover encrypted WebRTC transport, KMS-backed storage, access controls, PII redaction, and retention policies.
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