Data Engineering at Bloomberg
Roles, Comp & Culture
An L6 staff data engineer at Bloomberg sits around $374K total comp from 63 verified salary datapoints. The primary Data Engineering tech consists of CI/CD, Databricks and GCP, according to current job listings. Bloomberg pays data engineers above other Finance companies. Reviews put them at 4.0 on Glassdoor, a little above the middle of the pack. Bloomberg employees are stressed and employee happiness is trending down over the past year. Layoff risk scores low for the next 30 days. 9 data engineering roles are open right now.
Bloomberg data engineer compensation
Each level's figure is the median of individual Bloomberg offers at that level, so it reflects a typical outcome rather than an average pulled up by a few large packages. Total comp counts base salary plus equity and bonus annualized over the vest, and the range shown is the middle half of offers, with the top and bottom quarters trimmed off.
Bloomberg employee sentiment, tracked weekly
Employee happiness for data engineers over the past year, so you can see which direction it is moving, not just where it sits today.
Bloomberg pays above other Finance companies, and the ladder confirms it: $275K at senior, $374K at L6. The trade is real, though. Happiness is stressed and trending down, Glassdoor sits at 4.0, which is a little above the middle of the pack, and Blind sentiment runs mixed. The pattern that surfaces in reviews is a company that has historically rewarded longevity and domain depth but has been slower to modernize team structures and career mobility than its compensation might imply. You're getting paid well to work on genuinely hard financial data problems, inside a culture that leans conservative and process-heavy. Engineers who need fast feedback loops or frequent role changes tend to find that friction accumulating over time. The Terminal is profitable enough that there's no existential pressure, but that stability can read as stagnation depending on your temperament.
Layoff risk over the next 30 days is low, and 9 open data engineering roles across 4 cities, concentrated in New York. That's a modest but real hiring footprint for a company this size in finance. The direction of travel here is modernization at Bloomberg's pace: the GCP and Databricks presence in current listings signals active migration work rather than net-new greenfield, which means near-term joiners will spend real time on platform transition alongside steady-state pipeline work. Happiness trending down is worth flagging as trajectory evidence; whatever friction exists in the organization, the signal hasn't reversed. Someone joining in the next 6 to 12 months is buying into a migration cycle with solid pay but a culture under some internal stress. The upside is that platform modernization work tends to create genuine technical breadth for engineers willing to own it.
Bloomberg data engineering tech stack
The languages, storage, and processing tools Bloomberg data engineers actually work with, grouped by what they do. Tailor your system-design answers to this stack.
Bloomberg's core data problem is financial information at scale: the Terminal feeds real-time prices, news, analytics, and reference data to hundreds of thousands of terminals simultaneously, with latency and accuracy expectations set by trading desks rather than product managers. Data engineers here work inside that constraint, building pipelines that serve both the live Terminal and downstream products like Bloomberg Intelligence and BNEF. The stack showing CI/CD, Databricks, and GCP alongside Python and Java reflects a shop running mature batch and streaming workloads in parallel, with serious investment in moving historical financial data into cloud-scale compute. The regulatory surface is wide given the financial data redistribution business, so data contracts, auditability, and schema governance aren't afterthoughts. If you want problems that are purely product-growth-driven, this isn't where you'll find them; the constraints here come from market structure and compliance.
SQLBloomberg data engineer job openings
A live read on what they are hiring: open roles, recent postings, where, and at what level.
Build and maintain highly scalable, resilient and observable data pipelines supporting critical Commodities datasets
You will design and develop shared components, workflow patterns, and developer-facing systems that enable teams to deliver data pipelines with greater consistency, efficiency, and reliability.
Design and build data pipelines to enable decision making through analytics
Lead and develop a central team responsible for defining and delivering shared data infrastructure and reusable workflow patterns that improve consistency and efficiency across teams
Build and enhance data pipelines and processes that powers Bloomberg’s Private Funds and Hedge Funds Databases, ensuring high data quality, consistency, and reliability.
You are a data engineer who thrives in a highly collaborative environment, partnering with product, analytics, and engineering teams to deliver high-quality, trusted data.
The salary reports skew senior: 27 senior reports and 15 at L6, with only 6 at entry. Bloomberg hires data engineers who can own pipeline architecture end to end, and the interview loop confirms that: the screen centers Python and the full loop goes deep on pipeline architecture. Engineers who thrive here are comfortable with Java alongside Python, have worked with warehouse or lakehouse platforms before, and don't need a fast-moving product culture to stay engaged. If you're early-career and hoping Bloomberg is a training ground, the numbers suggest they fill that band rarely; you'll have an easier path in with a few years of financial or large-scale batch pipeline experience behind you. If you're a senior or staff engineer who wants market-rate pay on hard data problems and can tolerate a slower organizational culture, the case is solid. Before pursuing, prep the pipeline architecture conversation carefully.
Preparing for the Bloomberg loop
The round-by-round process, example questions, and prep plan are on the interview guide.
Compare Bloomberg with other data engineering employers
How the role, pay, and loop stack up against peer companies.
Prepare at Bloomberg interview difficulty
- 01
Reading a solution is not the same as writing one
Every engineer who has frozen on a query they had read a dozen times knows the gap. The only preparation that closes it is producing the answer yourself, under time, before the interview does it for you
- 02
76% of hiring managers reject on the coding task, not the resume
From HackerRank's 2024 Developer Skills Report. Candidates who look strong on paper still fail the live screen if they haven't done timed, executable practice
- 03
5 problem shapes cover 80% of data engineer loops
Dedup, sessionization, top-N-per-group, slowly-changing dimensions, partition tricks. Writing the shapes by hand turns the unfamiliar into pattern recognition