React Interview Preparation Learning Path

Review modern React concepts with emphasis on state, rendering, effects and architecture decisions.

Free learning path by InterviewGround — a frontend interview readiness platform.

What frontend interviews test

React interviews test whether you can trace what renders and why. Expect to explain how keys preserve state, why an effect ran twice, or why a callback reads an old value.

For senior roles the discussion turns to ownership: where state lives, how server data is cached, and how a component library stays accessible and testable as teams grow.

What you should know

  • Rendering

    What triggers a render, reconciliation, and the difference between rendering and committing.

  • State and data flow

    Local, lifted, context, URL and server state — and choosing between them.

  • Effects

    Synchronising with external systems, cleanup, and when an effect is unnecessary.

  • Stale closures

    Why handlers and effects can read old props or state, and how to fix it.

  • Memoisation

    memo, useMemo and useCallback as targeted tools rather than defaults.

  • Architecture

    Composition, error boundaries, suspense and feature boundaries.

Recommended learning order

  1. 01

    Render model

    Practise predicting renders and state preservation with keys.

  2. 02

    State placement

    Refactor duplicated or derived state; separate server state from UI state.

  3. 03

    Effects and async

    Fix stale closures and request races, with correct cleanup.

  4. 04

    Architecture practice

    Design a dashboard feature and justify boundaries, loading and error handling.

Questions you should be able to answer

  • Why can using an array index as a key show the wrong row state after a deletion?
  • A setInterval inside useEffect keeps logging the initial count. Explain and fix it.
  • When would you move state into context, and what does every consumer pay for that?
  • How would you decide whether useMemo is worth adding to a component?

Common interview mistakes

  • Syncing derived values into state with an effect instead of computing them during render.
  • Wrapping everything in useCallback without measuring, adding complexity for no benefit.
  • Fetching in effects without handling the response arriving after the input changed.
  • Describing context as a performance-free state manager.

Free learning resources

Free resources from their original publishers. InterviewGround does not own or host them.

FreeFoundation

React Learn

React

The official React learning path. The sections on state structure, escape hatches and effects map closely to what interviewers probe.

Sign in to save progress. Completion is self-reported.

Practice what you learned

Related learning paths

Ready to find your actual interview gaps?

Take a free frontend readiness assessment based on your skills or target job, and see which topics need attention before you interview.

Check My Readiness

Preparing for a specific company?

Practise company-style frontend questions by level and round.

Explore Company Prep