← Back to Directory

Bloomberg interview notes, page 12 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 software engineer interview with what sounds like a single coding question, probably a stack-based string decoding problem. Not much detail shared but enough to recognize the question.
  • Given an encoded string where the format is k[encoded_string] meaning the encoded_string is repeated k times, write a function to decode it.

“Classic stack problem.”

View Post

Bloomberg·Software Engineer·Technical Phone Screen

Jun 2026
Bloomberg software engineer interview that came down to a single coding problem, the magic dictionary one from LeetCode. Pretty focused session, no fluff.
  • Implement a magic dictionary that supports building a dictionary from a list of words and searching whether a given word can match any word in the dictionary by changing exactly one character.

“This is LeetCode 676.”

View Post

Bloomberg·Software Engineer·Technical Phone Screen

Jun 2026
Bloomberg coding round, one question the whole time. The problem looked like a fun little string thing until the duplicate letter handling showed up and made me rethink everything I'd written.
  • Implement the feedback logic from a Wordle-style game: given a guess and a target of equal length, return per-character results indicating exact match, present but wrong position, or not present. Duplicate letters must be handled correctly so a letter isn't marked 'present' more times than it actually appears in the target once exact matches are removed.

“I got the basic cases pretty fast, exact match is trivial, absent letters are trivial.”

View Post

Bloomberg·Data Analyst·Technical Phone Screen

Jun 2026
Bloomberg data analyst interview, one question but it had real teeth. The core problem sounds straightforward until you realize they want you to defend your metric choice under pressure.
  • Two companies in the same industry have nearly identical revenue, expenses, and net profit. How would you use data analysis to differentiate them, and why would you choose the specific metric you proposed over alternatives?

“The follow-up is where they actually get you.”

View Post

Bloomberg·Software Engineer·Recruiter / HR Screen

Jun 2026
Bloomberg SWE interview, just one question from what I can tell. Not much to go on but I'll share what I remember.
  • Why do you want to work at Bloomberg?

“Pretty standard motivation question but I fumbled it a bit.”

View Post

Bloomberg·Software Engineer·Technical Phone Screen

Jun 2026
Bloomberg coding screen, one question, pretty straightforward on the surface but easy to fumble if you're not careful about how you track depth.
  • Given a valid string containing parentheses and other characters, find the maximum nesting depth of the parentheses.

“Simpler than it looks but I almost overthought it.”

View Post

Bloomberg·Software Engineer·Online Assessment (OA)

Jun 2026
Bloomberg SWE online assessment with three coding problems and 20 MCQs. The problems ranged from array manipulation to graph traversal to combinatorics, and the MCQs were on top of all that. Pretty dense for a single sitting.
  • You have n servers each with a state of 0 or 1. You can pick any consecutive subarray and flip all values in it. After the flip, the redundancy is the number of distinct counts of operational servers across all possible configurations. Find the maximum redundancy achievable.
  • Given a network of devices where each device has a frequency of 1, 2, or 3, two devices can communicate if there's a simple path between them where consecutive devices differ in frequency by at most 1. Find the maximum distance between any two communicating devices.
  • Given an array of response times for n components, every non-empty subset forms a pipeline whose response time is (max element in subset) times (size of subset). Return the sum of all pipeline response times across all non-empty subsets, modulo 10^9 + 7.

“This one took me a while to even understand what was being asked.”

View Post

Bloomberg·Software Engineer·Technical Phone Screen

Jul 2026
Bloomberg data engineering interview that was basically one big coding problem: implement a production-grade rotating file sink in Python with thread safety, context manager support, and a custom exception. Pretty intense for a single question but it covers a lot of ground at once.
  • Implement a RotatingFileSink class in Python that writes records as JSON lines to disk, rotates files based on line count or byte size, supports context manager usage, is thread-safe, raises a custom error when written to after closing, and works as a drop-in replacement for an existing abstract base class without modifying the Pipeline class.

“This one took me a minute to even parse fully.”

View Post

Bloomberg·Software Engineer·Onsite - Behavioral / Leadership

Jul 2026
Behavioral round at Bloomberg for a software engineering role. The whole thing was structured around one project and they just kept drilling deeper into it, which I wasn't fully prepared for.
  • Walk me through a full-stack project you led end-to-end for a real client. How did it start, and how did you figure out what the MVP should actually be?
  • When client requirements are vague or keep expanding, what do you do? Give a specific example where you narrowed things down to a more focused first version.
  • How do you confirm that non-technical stakeholders actually understood what you were building, and vice versa? What specific techniques do you use?
  • If you suddenly left the team tomorrow, what would happen to this project? What did you put in place so someone else could pick it up?

“The MVP scoping part is where I stumbled a bit.”

View Post

Bloomberg·Software Engineer·Technical Phone Screen

Jul 2026
Bloomberg software engineer screen, first ten minutes were intro and one behavioral question. Pretty standard format, nothing too surprising.
  • Tell me about yourself: your background, recent projects, and why you're interested in this team.
  • Walk me through a significant challenge you faced, a conflict you resolved, or a project you're most proud of.

“They gave me the full first chunk of the screen just for this.”

View Post