Hooks, rendering, and state management under real questioning.
This is a spoken, conceptual discussion, not a live-coding exercise. You explain your reasoning out loud — concepts, tradeoffs, and "what would happen and why" — while the interviewer follows up and pushes on anything vague or surface-level.
Can you explain the rules of hooks in React, and why they exist?
Can you explain how React's reconciliation algorithm decides whether to update, replace, or remove a DOM node?
When would you lift state up versus reaching for something like Context or a state management library?
Can you explain what React.memo does, and when it actually helps versus when it's dead weight?
How do you decide when to break a component into smaller pieces versus keeping it as one larger component?
Can you explain how React Context works under the hood, and why overusing it can hurt performance?
Can you explain the dependency array in useEffect, and what actually happens if you get it wrong?
How do you approach testing a React component — what do you test, and what do you deliberately not test?
These are a few examples — each real session pulls 5 questions at random from a larger pool across every category above, so repeat sessions won't repeat the same set.
5 free interviews every month, any track, no card required.