Bloomberg Software Engineer candidates most often describe coding-heavy loops, with project discussions, behavioral conversations, and design topics appearing in later stages.
$198K
Avg. Base Comp
$250K
Avg. Total Comp
4-5 rounds
Typical Rounds
4-6 weeks
Process Length
Bloomberg Software Engineer interviews described by candidates are coding-heavy, but not coding-only. Several candidates reported an initial recruiter or phone screen followed by live coding, often with medium-difficulty algorithm questions. Reported topics included trees, BFS, linked lists, hash maps, caching, and graphs. The repeated practical requirement is to explain the solution as you work: candidates were asked to justify complexity, discuss data-structure choices, and handle follow-up changes rather than simply produce working code.
Candidates who described later stages also encountered project or resume discussions, motivation questions, and design-oriented conversations. Reported prompts included a subway-ticketing calculation and a WhatsApp design discussion, while other candidates described design rounds as team-specific. Prepare to clarify requirements, identify tradeoffs, and connect an implementation choice to the problem rather than assuming one fixed architecture question.
Behavioral preparation should be specific. Reports mention why Bloomberg, past projects, testing decisions, technical challenges, and conflict or achievement discussions. Individual loops differed by team and candidate, so the exact sequence is not consistent. A focused practice plan is to time-box two coding questions, narrate complexity and edge cases, then rehearse a concise project deep dive and one open-ended design discussion.
Synthesized from 20 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Bloomberg Lp process.
There were three rounds: a one-hour coding round, a two-hour technical round covering coding and system design, and a three-hour behavioral round. The coding questions were medium difficulty, but on the easier side of medium. The format was usually two questions in one hour, or about 30 minutes per question. Depending on the interviewer, you might need to run and test the code.
Questions asked: One question I remember was the bus routes problem.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Bloomberg Lp
Write a query to return whether each user's subscription date range overlaps with any other completed subscription
| Question | |
|---|---|
| Merge Sorted Lists | |
| Google Maps Improvement | |
| Longest Increasing Subsequence | |
| Most Repetition | |
| Hurdles In Data Projects | |
| Median O(1) | |
| Messenger Service Design | |
| Filling Supermarket Bag | |
| Target Value Search | |
| Binary Tree Validation | |
| Check Matching Parentheses | |
| Moving Window | |
| Inherited Model Evaluation | |
| 5th Largest Number | |
| Pathfinder in Maze | |
| Impossibly Iterative Fibonacci | |
| Blob Indexing | |
| Minimum Days for Scheduling All Meetings | |
| Summing Numeric Strings | |
| Shortest Path Algorithms | |
| Client Solution Pushback | |
| Why Do You Want to Work With Us | |
| Minimum Parking Spots | |
| Your Strengths and Weaknesses | |
| LRU Cache 1 | |
| Prime to N | |
| Top 3 Users | |
| Find the Missing Number | |
| Rectangle Overlap |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report recruiter conversations about prior work, technology stack, motivation, and logistics. Other candidates describe an early technical screen with live coding, so prepare both a concise background walkthrough and a ready-to-code setup.
Several candidates describe medium LeetCode-style problems involving trees, graphs, linked lists, hash maps, caching, tries, intervals, and BFS. Candidates report being pressed on Big-O, chosen containers, edge cases, and follow-up changes to the initial solution.
Candidates who reached later technical stages report a mix of project deep dives and design prompts, including a subway ticketing calculation, URL shortening, a key-value store, and portfolio-oriented services. The exact prompt varies, but candidates describe explaining assumptions and technical decisions.
Some candidates report HR, engineering-manager, or senior-manager conversations after technical rounds. Topics may include why Bloomberg, project testing, a technical challenge, conflict with a coworker, and how the candidate communicates through decisions.
