User settings store
Design a per-user settings/preferences store for a small app (theme, notification preferences, default view, and a handful of other toggles that may grow over time). Settings are read when a user loads the app and written occasionally when they change a preference. Describe how you model settings that can evolve without a schema migration every time you add one.
What a strong answer looks like
Clarify scale and constraints first. Propose a clean component breakdown, then go deep on the hard parts (data model, bottlenecks, consistency, failure modes) and name the trade-offs you are making.
Clarify3:00 left
Estimate3:00 planned
Design8:30 planned
Deep dive6:30 planned
Failure4:00 planned
Which questions mattered is sealed until you submit. Telling you now would just be handing over the edge cases.
Run or narrate your approach, then ask the coach.