Easy everything in Design & UX
First technical questions to scope a journey-map pain point
Ask how widespread and severe it is, where in the system it originates, and what constraints bound a fix.
What is PII and how to keep it out of logs
Define PII, redact or mask at the logging boundary, and avoid logging sensitive fields at the source.
Aesthetics-Usability Effect
The aesthetics-usability effect is the tendency for users to perceive attractive designs as easier to use and to be more tolerant of minor usability problems in them, which can mask real issues during testing.
Pixel-identical modals across platforms
Raise back-button and gesture behavior, safe areas and keyboard insets, native dismiss patterns, and accessibility differences.
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.
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.
First steps to deprecate a legacy component
Add a JSDoc @deprecated tag and IDE/console warning, document the migration, and keep the component working.
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.
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.
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.
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.
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.
Deciding whether a one-off variant belongs in core
Weigh reuse and consistency against maintenance cost, then decide with a shared-need bar and escape hatches for local cases.
Contributor workflow from proposal to merge
Proposal or RFC, design and core alignment, branch and build with tests and docs, review, then merge and release.
Process for adding a new component
Triage need, design and spec, build with a11y and tests, document, version, and release.
Core roles on a design system team
Name design, engineering, product/PM, and accessibility/docs roles with clear ownership.
Enforcing WCAG color contrast programmatically
Pre-validate token pairs, expose only safe semantic combos, lint and test contrast in CI.
Managing keyboard focus in an accessible Modal
Move focus in on open, trap Tab inside, close on Escape, restore focus to the trigger on close.
CSS-in-JS vs pre-compiled CSS for distribution
Runtime cost and dynamic theming of CSS-in-JS versus cacheability and SSR simplicity of static CSS.
Storybook's role in design system infrastructure
Isolated development, living documentation, visual and interaction testing, shared review surface.
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