One of our students recently completed the entire Bloomberg Software Engineer New Grad interview process and received an offer. From the initial phone screen to the final offer call, the entire process took about one month. Bloomberg's interviews focus less on solving extremely difficult algorithm problems and more on communication, practical engineering skills, project discussions, and system design.
Below is a complete walkthrough of the interview process, including coding questions, behavioral interviews, system design topics, and preparation advice.
Interview Timeline
- October 9 — Phone Screen
- October 29 — Virtual Onsite (VO1 + VO2 + HR)
- November 4 — Engineering Manager Interview
- November 6 — Offer Call
Preparation Tips Before Interviewing
Communication is one of the biggest evaluation criteria at Bloomberg. Interviewers expect candidates to explain their thinking continuously while solving problems. Thinking out loud, discussing trade-offs, and communicating clearly are significantly more valuable than silently writing code. Long periods of silence often leave a poor impression.
Referral strategy also matters. Bloomberg verifies referral information shortly after applications are submitted. Candidates without referrals or target-school backgrounds may find the process considerably more difficult, so planning your application strategy beforehand can be worthwhile.
Instead of memorizing Bloomberg-specific LeetCode tags, focus on recognizing problem patterns. Bloomberg frequently presents familiar algorithmic ideas wrapped inside different business scenarios, making pattern recognition much more valuable than memorization.
Phone Screen
The interview started with several behavioral questions, including "Why Bloomberg?" and a discussion about the candidate's most challenging project.
Two coding problems followed.
The first was an easy graph problem involving a social network where candidates needed to find the first connection satisfying specific conditions.
The second problem was based on LeetCode 2062. The coding difficulty itself was relatively manageable. What mattered most was explaining the solution clearly, discussing complexity, and walking through edge cases while implementing the code.
Virtual Onsite Round 1
The interview began with project discussions and behavioral questions. The interviewer focused heavily on the most technically challenging portion of the project, how obstacles were overcome, and what improvements would be made if the project were redesigned today. A structured STAR response worked well for this portion.
The coding question centered around a probability scenario.
Imagine a television series with ten episodes. Users may leave after each episode. Given that 70% of users who finish a certain episode eventually complete all ten episodes, answer several probability-related questions involving the nth episode.
Although the mathematical difficulty was moderate, Bloomberg cared more about reasoning and edge-case analysis.
Several follow-up questions explored special cases:
- What if every user leaves after the first episode?
- What if every user watches all ten episodes?
- How could an if-statement be rewritten to eliminate extra branching logic?
The final ten minutes were reserved for candidate questions, including discussions about work-life balance and commuting in New York. Before ending the call, the interviewer immediately scheduled the second virtual onsite round.
Virtual Onsite Round 2
After another project discussion, the interview shifted into an object-oriented design problem.
The task was to design a Tesla Equity system. Traders should be able to update daily prices or delete the latest price, while analysts should support the following operations:
- Retrieve the latest price
- Retrieve the maximum price
- Calculate the average price
All operations were expected to run in O(1) time.
An object-oriented solution was recommended, separating the system into classes such as Equity, Trader, and Analyst while carefully organizing internal data structures.
A follow-up discussion referenced LeetCode 295 (Find Median from Data Stream). The interviewer mainly wanted to understand the design approach and data structure choices rather than requiring complete implementation.
Another ten-minute Q&A session followed, during which the candidate asked about the interviewer's daily responsibilities. The Engineering Manager interview was scheduled immediately afterward.
HR Interview
The HR interview consisted entirely of behavioral questions.
- Tell me about a time you had disagreement with teammates.
- Tell me about a time you learned something completely new.
- Why Computer Science?
- Why Bloomberg?
- Tell me something not listed on your resume.
After the interview, HR confirmed that the feedback would be forwarded to the Engineering Manager for the final round.
Engineering Manager Interview
The Engineering Manager interview was the most technically demanding part of the process.
The primary question involved designing a distributed messaging system similar to Kafka.
The discussion covered multiple system design dimensions:
- Producer
- Consumer
- Topics
- Partitions
- Brokers
- Message SDK design
- Retry mechanisms
- Durability
- Consistency
- Availability
One particularly challenging scenario involved message ordering.
Suppose Producer A successfully sends data to Broker 1 while Producer B experiences network delays before also reaching Broker 1. How can the system guarantee message ordering?
The candidate did not fully answer this scenario. The Engineering Manager explained that a leader elected through the Raft consensus algorithm should determine message ordering while follower brokers replicate the committed log, ensuring consistent ordering across replicas.
Although the candidate initially felt this answer was incomplete, the interview extended beyond the scheduled time by nearly ten minutes. Before ending the conversation, the Engineering Manager even asked whether the candidate had any additional questions about relocating to New York, which turned out to be a very positive signal. Only two days later, Bloomberg reached out with the offer.
Overall Interview Experience
Bloomberg interviews emphasize practical engineering rather than purely difficult algorithms. Strong communication, deep project knowledge, structured problem-solving, and the ability to generalize familiar algorithmic patterns all play important roles throughout the process.
Candidates preparing for the Engineering Manager round should also review distributed systems fundamentals, especially Kafka architecture, Raft consensus, replication, consistency models, and messaging systems.
How Interview Show Helped
Before the onsite interviews, this candidate completed several targeted mock interviews focusing on Bloomberg's coding style and Engineering Manager system design expectations. During practice sessions, we emphasized structured communication, explaining implementation choices clearly, and decomposing distributed systems into manageable components.
The Kafka system design question closely resembled topics covered during mock interviews. Although every follow-up question could not be answered perfectly, the candidate maintained a logical discussion framework throughout the conversation instead of becoming stuck, which significantly improved overall interview performance.
Interview Show specializes in technical interview preparation for North American software engineering positions. Our team includes engineers with experience at leading technology companies and provides personalized interview coaching, coding interview preparation, virtual onsite mock interviews, and system design guidance. For companies like Bloomberg, Citadel, Jane Street, and other finance-focused engineering teams, we also offer company-specific preparation tailored to each interview style.
Top comments (0)