Frontend
State Management
Also written as Zustand, Context API
The pattern/library used to track and update data that changes over time in an app (e.g. what's in a shopping cart), and keep the UI in sync with it.
Think of it like
Like a shared whiteboard in the office that everyone reads from and writes to, so the whole team stays in sync on what's currently true.
Junior or senior?
Junior sounds like
Reaches for a heavy state library by default.
Senior sounds like
Knows when local state is enough, and can discuss the tradeoffs between the options they considered.
Ask them
“How did you decide what belonged in global state versus local component state?”