Multi-tenant observability platform
Design a multi-tenant SaaS observability platform shared by 5,000 customer organizations, ranging from tiny startups to a few whales sending 100x the median traffic. All tenants share the same ingest, storage, and query clusters. One noisy tenant must never degrade ingest or query latency for others, data must be strictly isolated, and per-tenant usage must be metered for billing. Design tenant isolation across the write path, storage, and query path, plus quota enforcement.
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.
Clarify5:00 left
Estimate5:00 planned
Design15:00 planned
Deep dive12:00 planned
Failure8: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.