React Interview Practice: The Questions That Separate Juniors from Mid-Level

React interviews are unusually predictable. The same eight or nine topics come up everywhere, and the difference between a junior and a mid-level offer is almost never knowing more APIs — it is explaining why React behaves the way it does. Here is what gets asked, and what a strong answer sounds like.

The mental model: why did this re-render?

The single most revealing React question is “what causes a component to re-render?” State change, parent re-render, or context value change — and crucially, a parent re-rendering re-renders children even when their props are identical, unless the child is memoized. Follow it with the trap most candidates miss: passing an inline object or arrow function as a prop creates a new reference every render, which defeats React.memo silently.

If you can also explain reconciliation and why keys matter — that an index key breaks when the list reorders, because React matches elements by key, not by position — you are already answering above junior level.

Hooks, in the order they get asked

• useState — batching, and why the functional updater exists when the next value depends on the previous one.
• useEffect — the dependency array, the cleanup function, and race conditions when a fetch resolves after the component moved on. Say “abort the request or ignore the stale response in cleanup” and you have answered it fully.
• useMemo and useCallback — what they cost as well as what they save. “I do not wrap everything; I memoize when profiling shows a real cost or when a reference feeds a memoized child” is the mature answer.
• useRef — mutable values that survive renders without triggering them.
• Custom hooks — expect to write one live, usually a data-fetching or debounce hook.

State management without dogma

The question is rarely “Redux or Zustand?” and usually “where should this state live?” The good answer starts local, lifts only when two components genuinely need it, uses context for low-frequency global values like theme or user, and reaches for a server-cache library such as TanStack Query for anything that comes from an API — because server data is a cache, not application state. Say that sentence and you have covered most of what the interviewer wanted.

Modern React: Server Components and Suspense

In 2026, teams on Next.js expect you to explain the server/client boundary: Server Components render on the server and ship no JavaScript to the browser, Client Components handle interactivity and state, and "use client" marks the boundary rather than a single file. Know why you cannot pass a function as a prop across that boundary, what Suspense is doing while it waits, and roughly what useTransitionis for. Even if the team is not on the App Router yet, knowing this reads as current.

The live coding task

Common tasks: a search input with debounce, a paginated list with loading and error states, a controlled form with validation, or a small component refactor. Narrate while you type, handle the empty and error states without being asked — that alone lifts many candidates a level — and clean up your effects. If you finish early, say what you would test.

How to practise it properly

Explaining re-renders out loud is harder than recognising the right explanation in an article. Set a timer, answer “what causes a re-render?” in sixty seconds without notes, then do the same for effects and memoization. A full mock frontend interview in the language of your real one turns those explanations into something you can produce under pressure rather than something you know you know.