roadmap
- 01
- 02
- 03
- 04
- 05
- 06
- 07
- 08
Walk into React interviews able to explain how the library works, not just how to use it. Covers components, hooks, rendering, server features, styling, testing, and the router, data, state and form libraries.
561 of 561 questions in your plan: 0 known, 0 in progress, 0 due, 0 skipped, 561 new. 0 cut, outside your plan.
React usually surfaces in two rounds of a frontend or full-stack loop. A live coding round asks for a small working component, an autocomplete over a remote search or a paginated list, and reads the code for its state and effects as much as for whether it runs. A technical conversation then asks why that code behaves as it does, and loops for middle and senior candidates usually add a design round on where data and state should live across a whole screen. The probes are small and specific. An interval started inside `useEffect` with `[]` for its dependencies logs the same count forever. Three calls to `setCount(count + 1)` in one handler move the count by one. A list keyed by array index leaves a typed value in the wrong row after a sort. A child wrapped in `memo` still re-renders because its parent hands it a fresh arrow function each time. A server-rendered page reports a hydration mismatch because it printed the current time. What changes with seniority is where the explanation stops. Fixing the interval with an updater function is enough early on; further up, the answer names the closure each render captures. Senior conversations leave the single component: whether a value belongs in the URL, a server cache or a client store, when `useMemo` costs more than it saves, and what can render on the server behind a Suspense boundary.
For its first four modules the plan is about React alone, and the order inside them follows how a question deepens. [Components and JSX](/topics/fe-react-components-jsx) set the vocabulary, controlled and uncontrolled inputs included. Hooks & State follows with the contract of each [built-in hook](/topics/fe-react-hooks), [state and context](/topics/fe-react-state-context) as a question of where state lives, and [effects](/topics/fe-react-effects-lifecycle), where a component reaches outside itself and most coding-round bugs begin. [Rendering and reconciliation](/topics/fe-react-reconciliation) comes after the hooks, so the puzzles they raised have an explanation waiting: why updates are batched, why effects run after the commit, why a key decides whether state survives. [Performance](/topics/fe-react-performance) stands on that engine, since memoizing only pays where React would re-render a subtree whose inputs did not change, and it ends on the [React Compiler](/topics/fe-react-performance-react-compiler) and on restructuring a tree instead. [Server Components and Suspense](/topics/fe-react-server-suspense) close the React half, last because streaming and Suspense boundaries assume the concurrent rendering described before them. From Routing & Data on, the plan turns to the libraries a React codebase is assembled from. Routing shares a module with data because [loaders and actions](/topics/fe-react-router-loaders-actions) fetch at the route instead of in an effect; [TanStack Query](/topics/fe-tanstack-query) and its alternatives then treat remote data as a cache with keys, staleness and invalidation, the server half of the [split drawn earlier](/topics/fe-react-state-context-server-vs-client). Client State takes what remains: [Redux](/topics/fe-redux) leads because its explicit loop is the yardstick newer stores are judged by, and the lighter stores follow. [React Hook Form](/topics/fe-react-hook-form) and Formik take the first module's forms to library scale, one registering uncontrolled inputs by ref, the other holding values in state. The last stretch is the toolchain: Tailwind's [source detection](/topics/fe-tailwind-jit-purge) and variants beside CSS Modules, then Vite from its [dev server](/topics/fe-vite-dev-server) to the production bundle. Testing comes at the very end because a component test exercises everything above it: [React Testing Library](/topics/fe-react-testing-library) renders through router, query and store providers, waits for async data and finds elements by role, the way a user would.
Someone who writes React daily and interviews in a week or two seldom needs the API again; the gaps are in the reasons. Spend the days on effects and rendering, and let importance at must know shrink each library module to what any team on that library would ask. Skip a library module outright if the posting never names its library. Developers coming from Angular or Vue bring a different idea of an update: React calls the component again and compares what it returns. Read the hooks and rendering modules whole and in printed sequence, which is what the by topics study order gives you, and over a longer runway build one small Vite app beside them, with a fetching search box, a sortable list and a validated form, each under a Testing Library test. At senior level the component model needs a quick pass at most; the hours belong to the state split, Server Components, and a query cache weighed against a store. The plan assumes JavaScript: the closures, event loop and promises behind stale-closure and race-condition answers are not taught here, nor is CSS beyond the two styling approaches. Those are what the [Frontend Developer roadmap](/roadmaps/frontend) adds around React. The framework most production Server Components run on, with its file-system routing and caching, belongs to the [Next.js roadmap](/roadmaps/nextjs).
React usually surfaces in two rounds of a frontend or full-stack loop. A live coding round asks for a small working component, an autocomplete over a remote search or a paginated list, and reads the code for its state and effects as much as for whether it runs. A technical conversation then asks why that code behaves as it does, and loops for middle and senior candidates usually add a design round on where data and state should live across a whole screen.
The probes are small and specific. An interval started inside useEffect with [] for its dependencies logs the same count forever. Three calls to setCount(count + 1) in one handler move the count by one. A list keyed by array index leaves a typed value in the wrong row after a sort. A child wrapped in memo still re-renders because its parent hands it a fresh arrow function each time. A server-rendered page reports a hydration mismatch because it printed the current time.
What changes with seniority is where the explanation stops. Fixing the interval with an updater function is enough early on; further up, the answer names the closure each render captures. Senior conversations leave the single component: whether a value belongs in the URL, a server cache or a client store, when useMemo costs more than it saves, and what can render on the server behind a Suspense boundary.
For its first four modules the plan is about React alone, and the order inside them follows how a question deepens. Components and JSX set the vocabulary, controlled and uncontrolled inputs included. Hooks & State follows with the contract of each built-in hook, state and context as a question of where state lives, and effects, where a component reaches outside itself and most coding-round bugs begin.
Rendering and reconciliation comes after the hooks, so the puzzles they raised have an explanation waiting: why updates are batched, why effects run after the commit, why a key decides whether state survives. Performance stands on that engine, since memoizing only pays where React would re-render a subtree whose inputs did not change, and it ends on the React Compiler and on restructuring a tree instead. Server Components and Suspense close the React half, last because streaming and Suspense boundaries assume the concurrent rendering described before them.
From Routing & Data on, the plan turns to the libraries a React codebase is assembled from. Routing shares a module with data because loaders and actions fetch at the route instead of in an effect; TanStack Query and its alternatives then treat remote data as a cache with keys, staleness and invalidation, the server half of the split drawn earlier. Client State takes what remains: Redux leads because its explicit loop is the yardstick newer stores are judged by, and the lighter stores follow. React Hook Form and Formik take the first module's forms to library scale, one registering uncontrolled inputs by ref, the other holding values in state.
The last stretch is the toolchain: Tailwind's source detection and variants beside CSS Modules, then Vite from its dev server to the production bundle. Testing comes at the very end because a component test exercises everything above it: React Testing Library renders through router, query and store providers, waits for async data and finds elements by role, the way a user would.
Someone who writes React daily and interviews in a week or two seldom needs the API again; the gaps are in the reasons. Spend the days on effects and rendering, and let importance at must know shrink each library module to what any team on that library would ask. Skip a library module outright if the posting never names its library.
Developers coming from Angular or Vue bring a different idea of an update: React calls the component again and compares what it returns. Read the hooks and rendering modules whole and in printed sequence, which is what the by topics study order gives you, and over a longer runway build one small Vite app beside them, with a fetching search box, a sortable list and a validated form, each under a Testing Library test. At senior level the component model needs a quick pass at most; the hours belong to the state split, Server Components, and a query cache weighed against a store.
The plan assumes JavaScript: the closures, event loop and promises behind stale-closure and race-condition answers are not taught here, nor is CSS beyond the two styling approaches. Those are what the Frontend Developer roadmap adds around React. The framework most production Server Components run on, with its file-system routing and caching, belongs to the Next.js roadmap.