Multi-tenant warehouse isolation
You run an embedded-analytics product where thousands of your customers query their own data in a shared cloud warehouse. One customer's heavy ad-hoc query or a runaway dashboard can saturate compute and slow everyone (noisy neighbor); customers also demand strict data isolation and per-tenant cost attribution for billing. Design the warehouse architecture covering tenant isolation, query resource governance, and accurate per-tenant cost accounting, and discuss the isolation-vs-efficiency trade-off.
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.
Clarify4:30 left
Estimate4:30 planned
Design13:30 planned
Deep dive10:30 planned
Failure7: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.