Why can missing useEffect dependencies cause bugs?
PICTURE THIS: ARRAY IN MEMORY
Index starts at 0. Scan once for max — O(n).
Simple meaning
The effect closes over stale props or state from the render that created it.
WHY — React instead of guessing?
Why interviewers care about React:
on React.
the situation, the default choice, and one exception - that reads as experience.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 1The effect closes over
stale props or state from the render that created it.
- 2Exhaustive-deps exists because that
stale closure is a real production bug.
- 3If the effect should
not re-run, I restructure with refs or split the effect rather than lying in the array.
- 4Give an example
One tiny concrete case you can say aloud.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
The effect closes over stale props or state from the render that created it. Exhaustive-deps exists because that stale closure is a real production bug.