5 React Interview Questions Recruiters Can Use (Cheat Sheet)

Hiring React engineers is difficult when you don't write code yourself.

Most recruiters and founders run into the same problem: a candidate sounds technical, but it's hard to tell whether they actually understand React or are just repeating buzzwords.

If you need a safe, reliable cheat sheet for phone screens, the best approach is to ask questions that have very clear right and wrong signals.

The five questions below help you quickly identify whether someone understands core React fundamentals — without needing to read their code.

You can read these questions verbatim during a phone screen.

If the candidate mentions the “Listen for” signals, that's a strong indicator they know React.
If you hear the red flags, it's usually a sign of shallow experience.

1. The "Rules of Hooks" Question

Why this matters

Hooks are the foundation of modern React. Developers who don't understand the rules will constantly introduce bugs into applications.

Ask exactly this

"React relies heavily on Hooks. Can you explain the 'Rules of Hooks'?"

Listen for (Green Flags)

• "Hooks must be called at the top level"
• "You can't call them inside loops, conditions, or nested functions"
• "They must run in the same order every render"

These phrases show they understand why React's state system works.

Red Flags

• They say there are no rules
• They immediately start talking about class components
• They can't explain why order matters

2. The "List Key" Question

Why this matters

This is one of the most common React mistakes. Strong developers know this instantly.

Ask exactly this

"When rendering a list of items in React, why do you need to use a `key` prop, and what is considered a bad key?"

Listen for (Green Flags)

• "Keys help React identify which items changed"
• "They help React update the DOM efficiently"
• "You should use a unique ID from your database"
• "Using the array index can be bad if the list changes"

These signals show they understand React's reconciliation process.

Red Flags

• "Keys are just to remove the warning"
• "Using array indexes is always fine"
• They don't understand why keys matter

3. The "API Fetching" Question

Why this matters

This question reveals whether the developer thinks about real user experience, not just happy paths.

Ask exactly this

"When you fetch data from an API, what states should your UI handle?"

Listen for (Green Flags)

• Loading state (spinner, skeleton UI)
• Success state (displaying the data)
• Error state (handling failed requests)

Better candidates may also mention:

• retry logic
• empty states

Red Flags

• They only talk about successfully fetching data
• They ignore loading or error scenarios

This often indicates inexperienced frontend thinking.

4. The "State Management" Question

Why this matters

Good engineers prefer simple solutions first. Poor engineers often over-engineer everything.

Ask exactly this

"How do you decide whether state should stay inside a component versus using a global state tool like Redux or Context?"

Listen for (Green Flags)

• "Keep state local when possible"
• "Use global state when multiple distant components need the same data"
• "Lift state up when needed"

This shows they understand React architecture tradeoffs.

Red Flags

• "I put everything in Redux"
• "I never use global state"
• They cannot explain when global state is appropriate

5. The "Re-Rendering" Question

Why this matters

React performance issues often come from unnecessary re-renders.

Ask exactly this

"What causes a React component to re-render, and how do you prevent unnecessary re-renders?"

Listen for (Green Flags)

• "Changes in state or props trigger re-renders"
• "Parent re-renders can also cause children to re-render"
• "Use tools like `React.memo`, `useMemo`, or `useCallback` when necessary"
• "Measure performance first using the React Profiler"

This shows they understand performance optimization responsibly.

Red Flags

• They put `useMemo` everywhere
• They don't know that state changes trigger re-renders
• They try to optimize everything prematurely

Quick Recap

A strong React candidate should confidently explain:

• The Rules of Hooks
• Why list keys matter
• API loading and error states
• Local vs global state decisions
• What triggers component re-renders

If a candidate struggles with these fundamentals, they will likely need significant mentorship before owning production React code.