Bloomberg · Primly Community

Bloomberg senior / L5 system design interview, what to expect (did mine last month)

corp_refugee · 4 replies

Went through the Bloomberg senior SWE loop in May 2026. Sharing system design specifics because I couldn't find anything current when I was prepping.

The system design round is 60 minutes with two engineers. Format is pretty classic: whiteboard-style (virtual, they use their own internal diagramming tool if you're remote), starting from an ambiguous prompt.

My prompt was something like: design a real-time news distribution system at scale. Not a surprise given what they build, but the constraints mattered. They pushed me toward: Latency requirements (they care a lot: sub-second delivery to terminals) Fan-out to millions of subscribers Data model for market data feeds vs. editorial news feeds (they treat these differently)

What they actually evaluated: I asked decent scoping questions and was upfront about tradeoffs. They seemed less interested in memorized patterns and more in whether I could reason aloud through something new. When I said "I'd use a message queue here, probably Kafka-style, but let me think about whether that changes if we need strict ordering per-feed" they leaned in.

What hurt candidates I heard about: going immediately to buzzword soup. Saying "microservices, Kubernetes, Kafka" in the first sentence without motivation killed at least one person who reported back.

Time allocation felt like: 10 min scoping, 25 min high-level design, 15 min deep-dive on one component, 10 min Q&A. They'll steer you if you're too shallow on depth.

Level calibration note: at senior / L5 equivalent, they expect you to own the tradeoffs, not just list them. "A database is better here because X, but I'd accept a cache if Y" is the register they want, not "you could do either."

One thing I didn't expect: they actually asked about observability and alerting as part of the design. Not deeply, but enough that I was glad I mentioned it proactively.

Overall the Bloomberg system design round felt less like a performance and more like a technical conversation. That was actually kind of nice after some of the more theatrical FAANG-style rounds.

4 replies

staff_steph

The "real-time distribution" prompt is consistent with what I saw two years ago, so they've stuck with it or something similar. The Kafka ordering thing is a real gotcha too. Strict global ordering at scale is not free, and if you just say "Kafka handles it" without acknowledging per-partition ordering vs. global, an experienced interviewer will notice.

corp_refugee

Exactly. One interviewer specifically asked "what if two publishers write to the same feed at the same millisecond?" That's not an accident. They want you to have thought about this.

newgrad_neil

Is the system design round at all levels or only senior? I'm interviewing for a new grad role and I'm terrified of getting a system design prompt.

corp_refugee

From what I was told, new grad / junior roles skip system design or do a lighter version. Your focus will be the coding rounds and behavioral. Don't stress that part.