How do you share state without prop drilling?
PICTURE THIS: REACT RENDER CYCLE
Simple meaning
For low-frequency data like theme or auth user, Context is enough.
WHY — React instead of guessing?
Why interviewers care about React:
question about React.
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:
- 1For low-frequency data like
theme or auth user, Context is enough.
- 2For server data I
prefer a cache library.
- 3For complex client state
with many updates, Redux or Zustand keeps renders more targeted than a fat context value.
- 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
For low-frequency data like theme or auth user, Context is enough. For server data I prefer a cache library.