← Back to Directory

Bloomberg interview notes, page 2 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·Onsite - Coding / Algorithms

Apr 2026
Bloomberg coding round where they handed you a ~200-line Python skeleton full of abstract base classes and told you to fill in the concrete subclasses without touching anything public. Pretty demanding for a timed setting, lots of moving pieces to track.
  • You're given a large Python codebase with abstract base classes using abc.ABC and @abstractmethod. Implement the missing logic in the concrete subclasses so the system works end-to-end, without touching public interfaces or the base classes themselves.
  • How did you navigate a roughly 200-line skeleton with abstract methods to identify where to implement logic and avoid making changes in the wrong places?
  • Separate parsing, validation, and execution responsibilities using composition within the concrete classes. How did you structure that?
  • Write unit tests that demonstrate the behavior of each implemented class and cover key interactions between them.

“The hardest part wasn't the implementation, it was just reading the skeleton fast enough to understand what each TODO actually needed.”

View Post

Bloomberg·Software Engineer·Technical Phone Screen

Apr 2026
Bloomberg SWE interview with a follow-up question on the bigram next-word predictor that pushed into data structure tradeoffs. Felt more like a design conversation than a coding screen.
  • You've built a bigram next-word predictor. Now what other data structures could you use to implement it? Walk through tries, hash maps with tuple keys, suffix arrays, and compressed neural representations. How do they compare on lookup time, memory usage, and ease of updating?

“The base bigram question felt manageable but then they pushed into this comparison and I fumbled a bit on suffix arrays.”

View Post

Bloomberg·Software Engineer·Technical Phone Screen

Apr 2026
Bloomberg SWE interview that started with a resume walkthrough and quickly went into the weeds on a real project. The system design follow-ups were sharper than I expected for what felt like a warm-up round.
  • Walk me through a recent project. How is the data stored and why did you design it that way?
  • How would you scale this system if QPS increased significantly?
  • Have you run into any production issues or bugs with this project? What happened?
  • How do you handle cache invalidation in your system?

“This was basically the first real question after the resume small talk.”

View Post

Bloomberg·Software Engineer·Technical Phone Screen

Apr 2026
Bloomberg SWE coding round, one problem the whole session. The question looked like a straightforward filtering task but the O(n) constraint is what made it actually interesting, and I didn't nail that part until pretty late.
  • Given a time-sorted list of transaction strings in the format name/time/amount/city, return all invalid transactions. A transaction is invalid if the amount exceeds 1000, or if the same person made another transaction in a different city within 60 minutes of it.

“I got the basic logic pretty fast: parse each record, flag anything over 1000, then check for same-name transactions within 60 minutes in a different city.”

View Post

Bloomberg·Software Engineer·Recruiter / HR Screen

Apr 2026
Bloomberg HR screen for a software engineer role, pretty standard stuff. About 30 minutes, recruiter covered background basics and then asked about a project and a behavioral question. Nothing technical, just the usual getting-to-know-you round.
  • Walk me through your background: how many years of experience do you have, what's your current role, and are you authorized to work in this location?
  • Tell me about a project you're most proud of. What was the problem, what was your role, and what was the impact?
  • Describe a time you dealt with a conflict, a significant challenge, or a failure at work.

“Pure logistics.”

View Post

Bloomberg·Software Engineer·Onsite - Coding / Algorithms

Apr 2026
Bloomberg onsite coding round for a software engineer role. One algorithmic problem the whole time, but it had enough layers to keep things interesting for a while.
  • You have n candidates, each with a cost to fly to New York and a cost to fly to San Francisco. Exactly ceil(n/2) candidates must go to New York and the rest to San Francisco. Find the minimum total travel cost. Also write unit tests covering edge cases like n=1 and odd n.

“My first instinct was brute force and I actually said that out loud which, fine, but I should've pivoted faster.”

View Post

Bloomberg·Software Engineer·Hiring Manager Screen

Apr 2026
Interviewed for a data management role at Bloomberg. The main thing they seemed to care about was whether you actually wanted this kind of work or were just defaulting to it because you couldn't get a pure finance gig.
  • You're coming from an interesting background. Why Bloomberg specifically, and why a tech-oriented data role rather than a more traditional business analyst path?

“This sounds like a softball but it really isn't.”

View Post

Bloomberg·Software Engineer·Technical Phone Screen

Apr 2026
Bloomberg coding round, one question, stack-based string decoding. Pretty standard for this kind of interview but the nesting aspect can trip you up if you haven't seen it before.
  • Given an encoded string in the format k[encoded_string] where the substring inside brackets is repeated k times, write a function to decode it. Assume the input is always valid and digits only appear as repeat counts.

“The base case is straightforward but I kept second-guessing myself on nested brackets.”

View Post

Bloomberg·Software Engineer·Technical Phone Screen

Apr 2026
Bloomberg coding round, one problem the whole session. The question looked clean on the surface but the follow-up constraints are where it got interesting.
  • Given an array of strings, group them into anagram clusters and return all the groups in any order. Aim for near-linear time in total characters, avoid sorting each string if possible, and explain how you'd handle case sensitivity, non-ASCII input, and very long strings.

“My first instinct was to sort each string and use that as a map key, which is the obvious O(n * k log k) approach.”

View Post

Bloomberg·Software Engineer·Technical Phone Screen

Apr 2026
Bloomberg software engineer interview that was basically a deep dive into your internship. One long question, lots of follow-ups. Felt more like a conversation than a grilling, but don't let that fool you.
  • Walk me through your most recent internship: the team, the business problem you were working on, your specific contributions, the biggest technical challenge you faced and how you resolved it, the most impactful thing you shipped and how you measured that impact, and what you learned about yourself as a collaborator.

“This is basically five questions wrapped in one and they will pull on every thread.”

View Post