Easy interview questions in Design Systems, page 2
Purpose and key sections of CONTRIBUTING.md
It documents how to contribute; key sections are setup and dev workflow, contribution process and standards, and review and release expectations.
Bug report to deployed fix workflow
Triage and reproduce, write a failing test, fix it, pass CI gates and review, then patch-release and notify.
Essential docs for onboarding a new team
Getting-started guide, per-component API and usage docs, design guidelines and tokens, plus changelog and migration notes.
Tracking design system adoption technically
Scan codebases for component imports via AST, compute adoption versus off-system usage, and aggregate into a dashboard over time.
SemVer bump for a non-breaking bug fix
A backward-compatible bug fix is a PATCH, the third number; major is breaking, minor is new compatible features.
First steps to deprecate a legacy component
Add a JSDoc @deprecated tag and IDE/console warning, document the migration, and keep the component working.
Implementing light and dark mode on the web
CSS custom properties for color tokens, a data-theme attribute toggle, and prefers-color-scheme as default.
Delivering one color token to three platforms
One JSON source, generated CSS variable for web, color resource XML for Android, and Swift/asset for iOS.
Pixel-identical modals across platforms
Raise back-button and gesture behavior, safe areas and keyboard insets, native dismiss patterns, and accessibility differences.
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