Real, anonymous reports from people who interviewed for Software Engineer at Bloomberg, newest first and distilled into what to expect across the loop.
Get your personalized Bloomberg Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
I didn’t have much detail beyond the first round I was preparing for. I was expecting a one-hour LeetCode-style coding round for a Senior Software Engineer role, and that was the only concrete step I had lined up in my mind at the time.
5 months ago
Difficult Neutral New York, NY
I only made it through two technical rounds, but it didn’t feel wildly chaotic. Each one had two LeetCode mediums, so the bar felt like steady execution rather than a single dramatic challenge. The first part of the conversation included resume questions for the first chunk of time.
Even though I didn’t progress further, the overall vibe was manageable up to that point. I didn’t get to see how the later stages would have looked beyond that—there was a sense the next step would have involved more senior-level HR or engineering leadership judging.
5 months ago
Average Positive Pune
My process felt pretty smooth overall. In the first round, I had one DSA problem—an actual LeetCode hard-style question—plus a quick intro and discuss…
5 months ago
Difficult Negative United States
My experience was rough in a way that had nothing to do with the actual interview questions. I got passed between three different recruiters, and each…
6 months ago
I got through the first round at Bloomberg, but I was ultimately rejected. The whole thing that stood out was a single DSA coding problem: merging two…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Interview Structure & Timeline
The interview process typically involves multiple rounds, starting with a coding session focused on data structures and algorithms (DSA), followed by additional technical rounds and concluding with HR and manager interviews. Candidates should expect the entire process to last around four hours, potentially split across two days.
multi-roundDSAHR
Technical Coding Rounds
Candidates will face LeetCode-style coding problems, often including two medium-level questions per round, with a focus on clear problem-solving and optimal approaches. Interviewers may provide hints and guidance if candidates get stuck, emphasizing the thought process over just arriving at the correct answer.
LeetCodeproblem-solvingDSA
Behavioral & Experience Discussion
Initial rounds often include discussions about the candidate's background and previous projects, allowing interviewers to gauge experience and fit. This conversational aspect is typically friendly and supportive, which can help ease nerves before diving into technical questions.
behavioralexperiencesupportive
System Design Component
For more advanced candidates, there may be a system design interview that focuses on architectural thinking and problem-solving in a broader context, such as designing a specific service. Candidates should prepare to discuss their reasoning and modifications to their designs in detail.
system designarchitectural thinkingproblem-solving
Candidate Experience & Pressure
Candidates have reported varying experiences with pressure during interviews, especially in later rounds where expectations may increase significantly. Some felt overwhelmed by the depth of questioning and the need to adapt solutions on the fly, highlighting the importance of preparation for high-stakes scenarios.
pressureadaptabilitypreparation
Recruitment Communication
Some candidates experienced issues with recruiter communication, including mismatched expectations regarding interview content and timelines. Clear and consistent communication from recruiters is essential for setting accurate expectations and reducing candidate anxiety.