Framework Pack · Mid to Senior
React Developer Interview Pack
Hooks, reconciliation, state management and performance, the questions asked in every React loop.
Hooks, the virtual DOM, state management patterns and render performance, with the tradeoffs interviewers probe.
- Questions
- 360
- Topics
- 20
- Pages
- 253pages
- 360 questions, every one with a model answer
- Hooks + rendering cheat sheet
- Redux vs Zustand vs Context
- Performance checklist
Get the React Developer Interview Pack — $9
One-off. Delivered as a PDF by email the moment payment clears.
Prices shown are a USD base. Your local-market price is calculated at checkout in your own currency, plus any local sales tax.
What is inside
20 chapters, in the order the interviews tend to ask them:
- The rendering model and reconciliation
- State that should not be state
- Hooks internals and the rules of hooks
- Effects and synchronising with the outside world
- Lists, keys and memoisation
- Context, composition and avoiding prop drilling
- Forms, controlled inputs and validation
- Suspense, transitions and concurrent rendering
- Server components and the data model
- Performance, profiling and Core Web Vitals
- Error boundaries and resilience
- Testing React at scale
- Accessibility in component design
- Frontend architecture at scale
- Data fetching, caching and revalidation
- Styling, CSS architecture and design tokens
- Designing component APIs that age well
- Portals, refs and imperative interop
- Hydration, mismatches and streaming SSR
- React 19 and the modern API surface
How the answers are built
Each chapter opens with the checklist the question is really testing. A few from this pack:
- A re-render is React re-running your component function. It does not mean the DOM changed.
- If a value can be computed from existing state and props, compute it during render instead of storing it.
- Hooks are dispatcher calls resolved from a per component ordered list, not special objects handed back to you.
- An effect synchronises a component with something outside React: a network, a browser API, a subscription or a timer.
- Keys communicate identity across renders, so a wrong key makes component state follow the wrong row.
- Context is for values that change rarely and are needed by distant components that have no reason to know about each other.
Questions this pack covers
- Walk me through what actually happens when I call setState.
- What is reconciliation, and does React diff the DOM?
- When should a value not be state at all?
- What is the duplicated state bug, and how do you spot it in code review?
- What is a hook at runtime?
- Why can I not call a hook conditionally or inside a loop?
- What is an effect actually for?
- What is the difference between useEffect and useLayoutEffect?
Each one is answered in full in the pack, with the reasoning written out rather than a bullet list.
About this pack
- How many questions?
- 360, spread across 20 topics, written out in full across 253 pages.
- Do the answers just list keywords?
- No. Each answer is written as prose, because that is what you have to reproduce when someone asks you the question.
- How do I get it?
- Pay once and the PDF arrives by email immediately, with a signed download link.
- Can I get it refunded?
- Yes, if it is not what you expected. See the refund policy.
