Bloomberg Lp Data Engineer interview typically runs 4 rounds: HR screening, two technical rounds, and a final behavioral round. The process takes about two months and is notably role-specific and hands-on.
$163K
Avg. Base Comp
$195K
Avg. Total Comp
4
Typical Rounds
2 months
Process Length
We’ve seen Bloomberg’s Data Engineer interviews reward candidates who can move comfortably between applied data work and crisp implementation details. Multiple candidates reported that the strongest signal was not flashy architecture, but whether they could reason through real datasets, explain tradeoffs, and cleanly manipulate data under pressure. In one successful experience, the technical work leaned into Python, Pandas, graph interpretation, and basic data cleaning on realistic inputs; the candidate who got the offer specifically noted that Bloomberg-style datasets felt more useful than generic problem sets. That lines up with what we hear often: Bloomberg wants people who can work with messy, business-shaped data, not just code in the abstract.
At the same time, our candidates also report a less obvious pattern: Bloomberg can pivot from “practical” to surprisingly algorithmic without much cushioning. One candidate was told to expect a real-world assessment, only to face a design-plus-coding problem that demanded binary search variants and time-range querying in the same sitting. That mismatch matters because it reveals what can make or break the interview here: not just knowing the tools, but being ready for the company’s version of practicality, which often includes efficient data structures, careful complexity reasoning, and implementation discipline. In other words, Bloomberg seems to care less about polished storytelling and more about whether you can build something correct, efficient, and directly useful when the problem gets specific.
Synthetized from 2 candidates 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.
The process started on a positive note — the recruiter George was professional, communicative, and set clear expectations going into the technical rounds. Unfortunately, the interview itself did not match what I was told to expect. Before the coding round, I was explicitly told there would be no LeetCode and that it would be a practical assessment of data structures in a real-world context. What I got was a 50-minute session that blended OOP design, clean code, type hints, and straight algorithmic coding into one problem about storing and searching incoming stories with timestamps.
On paper, the question sounded reasonable. I was asked to design a Story and StoryManager class, use a hashmap for efficient storage, and then support searching stories within a time interval. The part that made it difficult was that the interviewer expected a full implementation of binary search, including lower and upper bound variants, all within the same round. I initially suggested an O(n) linear scan, but that was dismissed as brute force and I was pushed toward the binary search approach. That’s fair in isolation, but in the time available it felt like too much to combine system thinking, object design, and a complete algorithmic implementation.
What stood out most was how quickly the conversation moved from “practical” to “LeetCode-style” without much warning. I have plenty of experience, so I’m not against algorithmic interviews, but this one felt misleading because it was framed as something more applied than it really was. The rejection came quickly and there wasn’t any meaningful feedback, which made the whole thing feel more dismissive than constructive. If anything, the main takeaway is to ignore the recruiter’s reassurance and be ready for a coding-heavy interview anyway, especially around binary search and time-range queries.
Prep tip from this candidate
Be ready to implement binary search lower/upper bounds for time-range lookups, not just describe the approach. Also practice combining a small class design with a hashmap-backed storage layer and a working search method under time pressure.
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 | |
| Hurdles In Data Projects | |
| Most Repetition | |
| Target Value Search | |
| Longest Increasing Subsequence | |
| Binary Tree Validation | |
| Median O(1) | |
| 5th Largest Number | |
| Filling Supermarket Bag | |
| Blob Indexing | |
| Minimum Days for Scheduling All Meetings | |
| Summing Numeric Strings | |
| Shortest Path Algorithms | |
| Check Matching Parentheses | |
| Moving Window | |
| Pathfinder in Maze | |
| Client Solution Pushback | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| LRU Cache 1 | |
| Minimum Parking Spots | |
| Analyzing Multiple Data Sources | |
| Prime to N | |
| Top 3 Users | |
| Find the Missing Number | |
| Rectangle Overlap | |
| Groups of Anagrams | |
| Radix Addition |
Synthesized from candidate reports. Individual experiences may vary.
A recruiter or HR representative reaches out to review your background, skills, and interest in the Data Engineer role. They also outline the rest of the process so you know to expect technical interviews and a final behavioral round.
This round mixes practical data-engineering discussion with coding. Candidates have been asked about databases, taxonomies, graphs, and then given Python problems such as counting distinct values from a semicolon-separated string, along with questions about optimizing code and explaining time and space complexity.
A deeper coding session focused on Python and Pandas. Candidates work through dataframe-based tasks such as cleaning a column typo and counting records, with an emphasis on practical data manipulation and working with real datasets.
The last interview is typically with a senior manager and is mostly behavioral. It focuses on your past experience, relevant classes or projects, and why you want Bloomberg, the specific role, and the finance/data industry.