roadmap
- 01
- 02
- 03
- 04
- 05
- 06
- 07
- 08
Build and run a design system that product teams adopt, from tokens and theming to components, documentation and governance. Covers design language, accessibility and UX practice.
423 of 423 questions in your plan: 0 known, 0 in progress, 0 due, 0 skipped, 423 new. 0 cut, outside your plan.
Frontend loops meet this subject as working code. A candidate is handed a modal or a custom select and asked what it needs before it ships: where focus goes when it opens and where it returns when it closes, what a screen reader announces for it, how its colors follow a theme without a hardcoded hex value. From middle level up the questions widen to the library behind the component: what a props API should refuse to accept, and how to change one without breaking the teams still pinned to the old version. The [Frontend Developer](/roadmaps/frontend) roadmap sets this subject beside the JavaScript, framework and browser questions of the same loop; the [Full Stack Developer](/roadmaps/full-stack) and [JS Full Stack Developer](/roadmaps/javascript-full-stack) plans carry it into jobs where the interface is one half of the work. A [UX Designer](/roadmaps/ux-design) interview comes at it from the other side, through a portfolio walkthrough: why this type scale and this spacing, what research the flow rested on, what a usability test changed, and how a decision held when a stakeholder disagreed. On the [iOS Developer](/roadmaps/ios) roadmap the subject arrives through the platform, as Dynamic Type, VoiceOver and colors that adapt to dark mode. Testers preparing with the [QA Engineer](/roadmaps/qa-engineer) or [Java SDET](/roadmaps/java-sdet) roadmap get the audit half: what an automated accessibility scan can catch, what still needs a keyboard and a screen reader, and how a shared component is tested once instead of on every page that uses it.
The [hub's primer](/topics/found-design-ux) lays out how these sections lean on one another, with the design language and the token model early because everything after them consumes both. Read it once; then take the plan one section per sitting and keep drilling its questions until your answers survive the interviewer's second why. Juniors are tested hardest on whether a control works without a mouse and announces itself correctly, so get [keyboard operability](/topics/found-accessibility-keyboard-nav) solid first: focus order, a visible focus indicator, and which keys a menu or a tab list is expected to answer. At middle level the deciding subject is [design tokens](/topics/found-design-systems-tokens): the layer between a raw value and the semantic name a component uses, and why a dark theme or a second brand then becomes a change of values rather than a rewrite. Senior and principal answers are judged on [governance](/topics/found-design-systems-governance): who may add a component, how a breaking change is announced and migrated, and what to do when a product team forks the button instead of asking for a variant. If the posting is for the team that owns the system, leave senior and principal inside your level range even when the title says middle: adoption and contribution questions are pitched high, and that team is hired to answer them.
Frontend loops meet this subject as working code. A candidate is handed a modal or a custom select and asked what it needs before it ships: where focus goes when it opens and where it returns when it closes, what a screen reader announces for it, how its colors follow a theme without a hardcoded hex value. From middle level up the questions widen to the library behind the component: what a props API should refuse to accept, and how to change one without breaking the teams still pinned to the old version. The Frontend Developer roadmap sets this subject beside the JavaScript, framework and browser questions of the same loop; the Full Stack Developer and JS Full Stack Developer plans carry it into jobs where the interface is one half of the work.
A UX Designer interview comes at it from the other side, through a portfolio walkthrough: why this type scale and this spacing, what research the flow rested on, what a usability test changed, and how a decision held when a stakeholder disagreed. On the iOS Developer roadmap the subject arrives through the platform, as Dynamic Type, VoiceOver and colors that adapt to dark mode. Testers preparing with the QA Engineer or Java SDET roadmap get the audit half: what an automated accessibility scan can catch, what still needs a keyboard and a screen reader, and how a shared component is tested once instead of on every page that uses it.
The hub's primer lays out how these sections lean on one another, with the design language and the token model early because everything after them consumes both. Read it once; then take the plan one section per sitting and keep drilling its questions until your answers survive the interviewer's second why.
Juniors are tested hardest on whether a control works without a mouse and announces itself correctly, so get keyboard operability solid first: focus order, a visible focus indicator, and which keys a menu or a tab list is expected to answer. At middle level the deciding subject is design tokens: the layer between a raw value and the semantic name a component uses, and why a dark theme or a second brand then becomes a change of values rather than a rewrite. Senior and principal answers are judged on governance: who may add a component, how a breaking change is announced and migrated, and what to do when a product team forks the button instead of asking for a variant.
If the posting is for the team that owns the system, leave senior and principal inside your level range even when the title says middle: adoption and contribution questions are pitched high, and that team is hired to answer them.