The concepts React interviewers probe most, with the short answer you would give out loud.
How does React's reconciliation work?
Each render produces a tree of elements. React compares it with the previous tree: if an element's type changed it unmounts and remounts that subtree, and if the type is the same it updates the props and keeps the state. Keys tell React which list item is which. Fiber lets this work be split up so urgent updates can go first.
React course →Controlled vs uncontrolled components?
A controlled input gets its value from React state and updates it in onChange, so React is the single source of truth and you can validate or format on every keystroke. An uncontrolled input keeps its own value in the DOM and you read it through a ref or on submit. Controlled is the default; uncontrolled is fine for simple forms and for file inputs.
React course →What are the Rules of Hooks and why do they exist?
Call hooks only at the top level of a component or a custom hook, never inside conditions, loops or nested functions. React tracks hooks by the order they are called, so the order must be the same on every render. Break the rule and state ends up attached to the wrong hook.
React course →useMemo vs useCallback vs React.memo?
React.memo skips re-rendering a component when its props are shallowly equal. useMemo caches a computed value, and useCallback caches a function, so that a memoized child sees the same reference next time. None of them is free, so measure first and use them where a stable reference or an expensive calculation actually matters.
React course →When does Context cause performance problems?
Every component that reads a context re-renders when its value changes, even if it only uses one field. Split contexts by how often they change, memoize the value object, and keep fast-changing state (for example mouse position or a timer) out of context. For heavy cross-cutting state a store with selectors, such as Zustand or Redux, avoids the wide re-render.
React course →Server Components vs Client Components?
Server Components render on the server and send no JavaScript of their own, and they can read data directly. They cannot use state, effects or browser APIs. Client Components, marked with 'use client', hydrate in the browser and handle interactivity. Keep the interactive leaves small and let the server render the rest.
React course →