Design a Logging and Monitoring System
Two 2026 reports from Uber loops land on this family. In January 2026 an L4 (SWE II) candidate in Sunnyvale was asked something like "design a logging system" and talked through a write-heavy store for ingest next to an inverted index for search. In April 2026 an SDE II candidate in India got something like "design a real-time monitoring system". That discussion covered push against pull collection, a service mesh such as Istio, the time-series database, caching, 5 and 10 minute aggregation windows and dashboard design. The two prompts are halves of one system, so prepare both. Logs answer "what happened on this request?" Metrics answer "is anything wrong right now?" They share the collection path and split at storage.
The January candidate's write-up is the one to learn from. Their high-level design was rated good. Then the interviewer kept asking about failure scenarios, and the feedback said those weren't handled well. The loop ended in a rejection. So failure sits inside the design here from the first box, and the deep dives open with it.
UberPremium lesson · System design round
The Uber design, worked end to end.
- Requirements and scopeSystem design · Frequently asked
- The API and data model
- The design, drawn out1 diagram
- 7 deep divesWith the tradeoffs
$49 a year · all 107 companies · instant access
548 Uber interview reports · guide updated
Uber interview guideKnow what Uber asks before you walk in.
30 coding · 8 system design · 21 behavioral questions
Get their questions first.
InterviewLegend is independent and not affiliated with or endorsed by any company it covers.