🚀 40 React Interview Questions Top Tech Companies Are Asking in 2026 🔥
React in 2026 looks different than React in 2022. The compiler, server components, the use hook, transitions — the surface area is bigger and the bar moved up. Here are 40 questions I've collected from real loops, organized by theme.
A 2026 React interview tests four layers: hooks fundamentals, the React 19 compiler, concurrent rendering / transitions, and Server Components / streaming. Most candidates over-prep hooks and under-prep concurrency.
Section 1 — Hooks fundamentals (10)
-
useStatevsuseReducer— when each? -
useEffectcleanup — common bugs. - Why is the dependency array so painful?
-
useMemovsuseCallback— when do you actually need them in 2026 (compiler era)? -
useRef— three legitimate uses. -
useImperativeHandle— example use. -
useLayoutEffectvsuseEffect. - Custom hook design — when to extract?
- The
usehook (React 19) — semantics. - Why do hooks need a stable call order?
Section 2 — React 19 compiler (6)
- What does the compiler do, conceptually?
- Does the compiler eliminate the need for
useMemo? - Cases where the compiler bails out.
- How do you debug a component the compiler skipped?
- Compiler vs forget hooks — interaction model.
- When would you opt out of the compiler for a component?
Section 3 — Concurrency and transitions (8)
-
startTransition— when do you reach for it? -
useDeferredValue— example use. - Suspense boundaries — granularity tradeoffs.
- How does React decide what's urgent vs non-urgent?
- Streaming SSR with
renderToPipeableStream. - Selective hydration — what is it?
- Concurrent rendering — what changed in error boundaries?
- Tearing — what is it and how does React 18+ avoid it?
Section 4 — Server Components and frameworks (8)
- Server Components vs Client Components — boundary.
- Server Actions — when over a fetch handler?
- How do server components shrink client bundles?
- Cache layers in Next.js 15 / 16 with React Server Components.
- Why can't server components use hooks?
- Streaming a server-rendered list with Suspense.
- Forms with Server Actions — error handling patterns.
- SEO with Server Components — what to know.
Section 5 — Performance and tricky gotchas (8)
- Re-renders — three common causes in 2026.
- React DevTools Profiler — what to look for.
- Why is the key prop so important in lists?
- Memoizing entire trees — when does it backfire?
- Context overuse — symptoms and fixes.
- Hydration mismatch — common causes.
- INP optimization — how React's scheduler helps.
- State management in 2026 — why most apps don't need Redux anymore.
How to drill
Don't memorize. Build a small app touching every primitive. Use the coding copilot to verify hook patterns against current best practice.
Mock rhythm
- Monday: hooks fundamentals
- Tuesday: compiler
- Wednesday: concurrency
- Thursday: server components
- Friday: perf gotchas
- Saturday: full mock with practice mode
Common interview mistakes
- Saying "
useMemoeverywhere" in 2026 - Confusing server components with SSR
- Not knowing what
usedoes - Underestimating Suspense boundary granularity
- Mixing class components into the conversation when nothing requires them
Get started
Free forever plan: aissence.ai/auth/signup.
Top comments (0)