roadmap
- 01
- 02
- 03
- 04
- 05
- 06
- 07
- 08
Prepare for UX designer interviews, from user research and usability testing to defending design decisions. Covers interaction patterns, visual foundations, accessibility and design systems.
742 of 742 questions in your plan: 0 known, 0 in progress, 0 due, 0 skipped, 742 new. 0 cut, outside your plan.
A UX designer loop is built around your own work. After a recruiter screen and a hiring-manager call, the onsite usually centers on a portfolio presentation: one or two case studies walked through for a panel of designers, product managers and engineers. Around it sit a design exercise, live at a whiteboard or as a take-home, often an app critique, and a behavioral conversation; research-heavy roles add a session on planning a study.
The panel interrupts the case study to test the process behind it. Why a card sort, when the hierarchy already existed and a tree test would have measured whether people could find things in it? What can a handful of usability sessions tell you, and why not how many users will hit the problem? In the critique and the exercise the questions move onto the screen: why a switch takes effect at once while a checkbox in a form waits for submit, why an error the user must act on does not belong in a toast that disappears, where focus goes when a dialog closes.
Seniority shows in what the story is about. Early on it is one flow and what testing changed in it. Later it is a decision argued across teams: the metric it was meant to move, whether it still moved once the novelty wore off, and what you gave up to ship it.
Process comes first because it is what the portfolio and the design exercise are scored on. The UX design module runs from research through journeys and information architecture to prototyping and usability testing, the sequence a case study is expected to follow and the one interviewers hold it against. Figma follows as the place that work gets made; its components, variants and auto layout already rehearse the reuse the plan returns to later.
The plan then turns from how you decide to what you decide with. Standard components come before the visual layer because choosing a dialog over an inline message is a behavior decision made before anything is styled. Design language adds type, spacing, color and motion, and accessibility follows at once, re-reading both stretches with a different question: can the component be reached by keyboard and announced correctly, and does the palette still carry meaning for someone who cannot tell its hues apart?
Scale is the next turn. Atomic design supplies the vocabulary for where one component ends and the next begins, and design systems turn it into tokens, theming, the handoff to engineering and the governance that keeps a shared library from splitting into local copies. Measurement then answers the question research opened, whether the shipped design worked, through funnels and retention and the novelty and primacy effects that flatter or punish a redesign in its first weeks. Agile delivery places design work inside the sprint. The last module steps back from the screen to the conversation around it: behavioral questions about conflict, influence and failure, and the stages of the loop from screening to the panel day and after.
A visual designer moving into UX usually has the middle of the plan and lacks its ends: start with research and usability testing, and do not skip measurement, because a case study without evidence reads as a mood board. A UX researcher has the opposite gap, in components, the visual layer and accessibility. Senior candidates get most from design systems, governance and measurement, where the questions are about influence over teams you do not run. When the presentation is days away, most of the time belongs to rehearsing it aloud; give the page what is left, with importance narrowed to must know and level pulled in to your own band. A longer runway suits the plan's own sequence, so choose by topics as the study order. For the last weeks, switch it to random: a critique jumps from a research method to a dropdown to a contrast failure with no transition, and a shuffled drill is the closer rehearsal. The plan meets code only at the handoff. It does not teach HTML or CSS, or how engineers build and version a component library. A designer joining a design-system team should continue with the [Design Systems roadmap](/roadmaps/design-system); one who wants to prototype in the browser, with the [CSS roadmap](/roadmaps/css).
A visual designer moving into UX usually has the middle of the plan and lacks its ends: start with research and usability testing, and do not skip measurement, because a case study without evidence reads as a mood board. A UX researcher has the opposite gap, in components, the visual layer and accessibility. Senior candidates get most from design systems, governance and measurement, where the questions are about influence over teams you do not run.
When the presentation is days away, most of the time belongs to rehearsing it aloud; give the page what is left, with importance narrowed to must know and level pulled in to your own band. A longer runway suits the plan's own sequence, so choose by topics as the study order. For the last weeks, switch it to random: a critique jumps from a research method to a dropdown to a contrast failure with no transition, and a shuffled drill is the closer rehearsal.
The plan meets code only at the handoff. It does not teach HTML or CSS, or how engineers build and version a component library. A designer joining a design-system team should continue with the Design Systems roadmap; one who wants to prototype in the browser, with the CSS roadmap.