Skip to content

Senior React interview path

Use this page as the one-stop path. Read the lessons in order, attempt the starter code before the hints, check your reasoning with the quiz bank, then move to the next lesson only when you can explain the current one without notes.

The one-pass loop

  1. Read the lesson's Objective, Mental Model, and Example.
  2. Predict what the starter code will do before you run it.
  3. Implement the starter lab in interview-labs/ without reading the Hints.
  4. Check your answers with the Quiz bank.
  5. Defend the Challenge out loud as if in an interview.
  6. Advance only after a correct quiz and a working implementation.

Senior-level expectations

At senior and staff levels, interviewers care more about tradeoffs than syntax. For every concept you must be able to:

  • Name the problem it solves.
  • State the working model and the deeper reality.
  • Give a failure you have seen or can imagine.
  • Compare it to two alternatives and explain when you would change your choice.
  • Describe how to debug it in production.

21-day follow-once schedule

Week Lessons Daily focus Output
1 1–4 Build, predict, derive Typed shell, reducer, composition
2 5–9 Context, routes, async, effects Provider, router, fetch, cleanup
3 10–13 Tests, performance, architecture, capstone Passing tests, profile, design record

Before the interview

What senior interviewers actually ask

  • "Why not just put everything in a global store?"
  • "How would this fail on a slow 3G device with stale data?"
  • "What is the cheapest change that proves your performance theory?"
  • "Where is the trust boundary and why?"
  • "What would you not mock in a test for this component?"

If your answer only describes API usage, go deeper. If it only describes internals, connect it to the user or the business.