← Back to Directory

Bloomberg interview notes, page 9 of 14

Large Enterprises

Most of these Bloomberg write-ups come from Software Engineers (130), then Product Managers (2) and Data Analysts (1). The most reported rounds are the technical phone screen (100), the behavioral / leadership round (8), the onsite coding round (8) and the system design round (8).

133 interview notes · updated Oct 2026

Bloomberg·Software Engineer·Technical Phone Screen

Jun 2026
Bloomberg SWE interview where they had me implement a stripped-down version of grep from scratch. The focus wasn't on clever algorithms but on how cleanly you structure the code and whether adding a new flag later would be painful or trivial.
  • Implement a simplified grep utility that takes a pattern, a list of lines, and optional flags (case-insensitive, line numbers, invert match) and returns the matching lines in order.

“The problem itself isn't hard but I spent too long on the actual matching logic and not enough on the flag abstraction layer, which is clearly what they cared about.”

View Post

Bloomberg·Software Engineer·Technical Phone Screen

Jun 2026
Bloomberg technical screen focused on graph algorithms, specifically DAG traversal and path computation. The question had layers to it and pushed toward optimization in a way I wasn't fully ready for.
  • Given a directed acyclic graph with weighted edges and a source node, compute either the number of distinct paths from the source to each node, or the minimum total edge cost to reach each node (returning infinity if unreachable). How do you optimize beyond naive DFS?

“I started with brute-force DFS and they let me finish before asking about performance on large graphs.”

View Post

Bloomberg·Software Engineer·Technical Phone Screen

Jun 2026
Bloomberg data engineering interview with a pretty focused line of questioning around data validation practices. Nothing flashy, but the follow-ups pushed harder than I expected.
  • What pass rate on validation checks would you consider good enough to call a dataset valid?
  • When records fail validation, what do you do with them?
  • If you're working with a very large dataset, would you still run a full validation pass across every record, and would you still investigate each failure individually?

“I fumbled this a bit because I gave a number without context, like just said '99%' and moved on.”

View Post

Bloomberg·Software Engineer·Technical Phone Screen

Jun 2026
Bloomberg SWE coding round, one problem, stack-based string/array manipulation. The problem looked like a LeetCode variant I'd seen before and that familiarity almost worked against me.
  • Given a 1D array (or string) of elements, repeatedly remove every maximal consecutive run of three or more identical items. After each removal, the remaining elements close the gap and new runs may form, which should also be removed. Continue until no such run exists. Return the final array. Solve this efficiently using a stack of (value, count) pairs.

“I recognized the Candy Crush problem immediately and that was almost my downfall.”

View Post

Bloomberg·Software Engineer·Technical Phone Screen

Jun 2026
Bloomberg follow-up coding round, one problem but they kept pushing on complexity until you got to a proper O(n) solution. Felt like a reasonable problem until the interviewer started asking for a single-pass approach and I had to think harder than expected.
  • Given a string, you must remove exactly one character (no skipping even if already balanced). After removal, check whether all remaining characters appear with equal frequency. Return true or false.

“My first instinct was to just count frequencies, try removing each character, and recheck.”

View Post

Bloomberg·Software Engineer·Technical Phone Screen

Jun 2026
Bloomberg SWE interview with a scheduling/intervals problem. Pretty standard coding round but the question has some nuance if you haven't seen it before.
  • Given an array of meeting time intervals, find the minimum number of conference rooms needed so that no two meetings overlap.

“The trick I kept second-guessing myself on was whether to use a min-heap or just sort and scan.”

View Post

Bloomberg·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Bloomberg system design round for a software engineering role. One meaty question about real-time ticker ingestion that looked deceptively close to a leetcode problem but wasn't, and the distinction mattered more than I expected.
  • Design and implement a service that consumes stock ticker symbols from a high-frequency upstream API and exposes the current top-K most frequently seen tickers. How do you handle the ingestion rate, choose your data structures, and manage concurrency?

“I started with the obvious hashmap plus min-heap combo and the interviewer was fine with it but then pushed on what happens when the upstream is firing thousands of events per second.”

View Post

Bloomberg·Software Engineer·Recruiter / HR Screen

Jun 2026
Pretty standard opening round for Bloomberg SWE. Two behavioral questions, nothing technical, just the usual get-to-know-you stuff before they decide if you move forward.
  • Walk me through your background, what you're working on now, and what you're interested in next.
  • Why Bloomberg specifically, and why do you think you're a good fit for this role?

“Pretty much every interview starts this way so I had a version ready.”

View Post

Bloomberg·Software Engineer·Technical Phone Screen

Jun 2026
Bloomberg SWE interview with a data structures problem that looked simple on the surface but had some tricky edge cases once you got into it. The focus was on designing a class cleanly and thinking through time and space complexity out loud.
  • Design and implement a class that tracks records as (timestamp, score) pairs and supports inserting new records and querying the average score over a sliding time window.

“My first instinct was a queue and I went with it, which was fine, but I spent too long second-guessing whether to use a deque vs a plain list before just committing.”

View Post

Bloomberg·Software Engineer·Onsite - Behavioral / Leadership

Jun 2026
Bloomberg SWE interview, one behavioral question about a challenging project. Pretty standard stuff but the depth they expected caught me off guard.
  • Walk me through your most challenging project. What made it hard, what was your specific role, what trade-offs did you navigate, and how did it turn out?

“I had a project ready but fumbled the trade-offs part.”

View Post