Skip to the content.

One week

345 minutes across 23 steps. Seven focused sessions across UI, State and Server — enough to hold your own in a frontend interview loop, assuming you already write JavaScript for a living.

One week 0 of 0 done (0%)
  1. ui/atom reading

    Start where every component starts.

  2. Where does an atom stop? quiz · easy · 8 min

    Four minutes that decide where half your components belong.

  3. ui/props reading
  4. Validating Prop Usage quiz · easy · 7 min
  5. Setting Default Values for Props quiz · easy · 7 min
  6. Presentational vs container components quiz · easy · 5 min

    The oldest split in the vocabulary, still the most useful.

  7. ui/events reading
  8. Handling DOM Events quiz · easy · 8 min
  9. Build a loading Button atom ui-coding · easy · 30 min

    Your first component from scratch, in two frameworks.

  10. ui/skeleton reading
  11. Replace a spinner with a skeleton ui-coding · easy · 25 min

    The layout-shift bug every list has until someone fixes it.

  12. state/store reading
  13. state/actions reading
  14. Implement Redux-style action creators coding · easy · 15 min
  15. state/reducer reading
  16. Implement a Redux-style reducer with immutability coding · medium · 20 min

    Immutability, with the tests that prove it.

  17. state/selectors reading
  18. Selector Memoization Basics quiz · medium · 10 min
  19. Memoize a derived selector coding · medium · 25 min

    Build the memoizer, then watch the recomputation count.

  20. server/ssr reading
  21. Pick a rendering strategy quiz · medium · 10 min

    Four briefs, four rendering decisions.

  22. server/protocol reading
  23. Design the caching layer for a static app system-design · easy · 20 min

    The design round in twenty minutes.

This plan assumes you already write JavaScript for a living and have shipped a component or two. What it adds is vocabulary and placement: where a value belongs, where a boundary goes, and which decision the other decisions hang on.

Seven sessions of roughly an hour. Read the concept page first, then do the question that follows it — the order is deliberate, because each question is only worth doing once you have the words for what it is asking.

The one thing not to skip is the workspace. Reading about memoisation and watching a recomputation counter go from six to one are different experiences, and only the second one survives an interview.