How does Redux data flow work?
PICTURE THIS: ASYNC / PROMISE
Simple meaning
The UI dispatches an action object.
WHY — Redux instead of guessing?
Why interviewers care about Redux:
question about Redux.
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:
- 1The UI dispatches an
action object.
- 2A pure reducer returns
the next state without mutating the previous one.
- 3Subscribed components then read
the store, often through useSelector.
- 4Middleware sits between dispatch
and the reducer for async.
- 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 UI dispatches an action object. A pure reducer returns the next state without mutating the previous one.