Intermediate interview questions in Design Systems, page 3
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.
Governance for accessibility regressions
Detection via audits and monitoring, triage with severity and ownership, remediation SLAs, prevention feedback.
Design systems across micro-frontends
Shared singletons and version alignment, token-based theming, distribution via shared scopes, stronger governance.
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.
Technical and comms plan for a Button break
Additive-first then deprecate, major semver, codemod and guide, multi-channel early comms with adoption tracking.
Measuring design system adoption and health
Component coverage and version spread from code scans, usage analytics, issue and satisfaction signals.
Gradual design system adoption in legacy code
Coexistence strategy, codemods for mechanical swaps, lint rules to block regressions, prioritize high-traffic surfaces.
Linking form-component adoption to fewer a11y bugs
Define both variables, segment by adoption level, control confounders, watch correlation-versus-causation.
Measuring designer efficiency from Figma data
Library component usage and detach rates from Figma, time-to-mockup, override frequency via the API.
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.
Design tokens for multi-brand button theming
Tokens as named design decisions, primitive-versus-semantic layers, per-brand themes mapping semantic to primitive.
Documentation for a new Card component
Usage guidance and do/don't, variants, accessibility, code examples, composition.
Framework-agnostic components across React, Vue, Angular
Web components for one core, framework wrappers for ergonomics, codegen as an alternative, with their costs.
A simple automatable metric for dev-time savings
Component coverage or cycle time, gathered automatically, compared across adoption levels.
Structuring color tokens for a new app
Primitive palette, semantic role tokens, optional component tokens, theming benefit.
Explain token aliasing in design systems
Primitives hold raw values, semantic tokens reference them by intent, components consume only semantic ones.
Designing a flexible yet usable DataTable API
Sensible defaults, compound or slot-based composition for flexibility, props for common cases.
Architecting decoupled but linked Tabs components
A Tabs context provider holds active state, TabList and TabPanel consume it anywhere inside the provider.
Versioned documentation site for a design system
Snapshot docs per release, version-prefixed routes, a version switcher, canonical latest.
Deprecating a widely used component gracefully
Announce and document replacement, soft-deprecate with runtime and type warnings, ship codemods, remove only in a later major.
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