How would you implement debounce in an interview?
PICTURE THIS: REACT RENDER CYCLE
Simple meaning
I keep a timeout id, clear it on every call, and set a new timeout that fires the original function after wait ms.
WHY — JavaScript instead of guessing?
Why interviewers care about JavaScript:
question about JavaScript.
trade-offs, and what you would actually do on a Frontend project - not buzzwords.
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:
- 1I keep a timeout
id, clear it on every call, and set a new timeout that fires the original function after wait ms.
- 2I also mention cancel
on unmount in React so setState does not run on a dead component.
- 3Leading-edge debounce is an
extra flag if they ask.
- 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
I keep a timeout id, clear it on every call, and set a new timeout that fires the original function after wait ms. I also mention cancel on unmount in React so setState does not run on a dead component.