Data Engineering at Uber
Roles, Comp & Culture
An L6 staff data engineer at Uber sits around $523K total comp from 99 verified salary datapoints. The ladder runs from about $143K at entry up to $523K. Uber pays data engineers above the other companies we track. Reviews put them at 3.7 on Glassdoor, a little below the middle of the pack. Employee sentiment at Uber reads neutral and employee happiness has held flat over the past year. Layoff risk scores low for the next 30 days.
Uber
Transportation · San Francisco, US · UBER
live data · August 2, 2026
DE total comp
$394K median
L5 · senior level · $322K–$472K · 36 verified datapoints
Hiring now
No open DE roles
tracked daily
Team happiness
Neutral
employee happiness
Layoff risk (30d)
Low
Employee sentiment
3.7 / 5
MixedEmployees
5,001–50,000
Uber data engineer compensation
Each level's figure is the median of individual Uber 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.
What the Uber signals mean
Uber is regarded as a fast-moving, real-time environment with genuine 24/7 operational pressure: when a pipeline breaks, drivers earn less, riders wait longer, and revenue is lost every minute. The trade-off candidates weigh is that urgency and on-call intensity against the scale and technical depth of the marketplace and geospatial problems.
Uber 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.
Recent Uber events
Layoffs, leadership changes, and other major moves at the company, with dates.
- Exec departureFeb 2026Leadership change
- Exec departureJun 2025Leadership change
- Exec departureFeb 2025Leadership change
Notable company events we track, with dates.
Practice for the Uber loop
Round by round, the problems our model predicts for this company's interview. Rehearse the shapes their panels keep returning to.
Data engineering teams at Uber
Which team you interview for shapes the questions. The main DE surfaces:
Marketplace
Pricing, surge, driver matching. DEs build pipelines for real-time supply/demand signals, surge multiplier computation, and matching algorithm feature stores. This team generates the most system design interview questions.
Maps and Geospatial
Routing, ETA prediction, map data quality. DEs process billions of GPS pings daily, maintain geospatial indexes (H3), and feed ML models for arrival time estimation. Expect heavy geospatial SQL if interviewing here.
Safety and Insurance
Incident detection, fraud signals, insurance risk scoring. DEs build event pipelines that flag anomalous trip patterns and feed real-time safety interventions. Data quality is critical because false negatives have real consequences.
Eats and Delivery
Restaurant analytics, delivery time prediction, courier optimization. DEs manage order event streams and build pipelines that balance delivery speed against courier utilization.
Freight
Logistics, load matching, carrier analytics. DEs build pipelines for shipment tracking, carrier performance scoring, and pricing models across long-haul routes.
Data Platform
Internal tooling, governance, infrastructure. DEs build and maintain the shared data lake, schema registry, data catalog, and self-serve query tools used by every other team.
What makes Uber different
The things about this company that should shape every answer you give.
Hybrid infrastructure
Unlike companies that run entirely on AWS or GCP, Uber operates a hybrid of on-prem data centers and cloud resources. This means DEs must understand bare-metal performance tuning alongside cloud-native patterns. Interview questions often probe whether you can reason about infrastructure you manage directly, not just managed services.
Open-source DNA
Uber has built and open-sourced multiple foundational data tools: Apache Hudi for incremental data lake management, Cadence for workflow orchestration, H3 for geospatial indexing, and AresDB for real-time analytics. Interviewers expect candidates to know these exist and understand the problems they solve.
Multi-sided marketplace complexity
Every Uber transaction involves at least 2 parties (rider and driver, eater and courier) plus the platform. This creates data modeling challenges that single-sided businesses do not have. Supply/demand balancing, dynamic pricing, and matching algorithms all generate complex event streams that DEs must process and serve.
Real-time financial impact
When a data pipeline breaks at Uber, drivers earn less, riders wait longer, and the company loses revenue every minute. This urgency shapes interview expectations. Uber wants DEs who think about monitoring, alerting, SLAs, and graceful degradation as first-class requirements, not afterthoughts.
Preparing for the Uber loop
The round-by-round process, example questions, and prep plan are on the interview guide.
Uber data engineer roles by level
Level-specific pages: the comp, the bar, and what the loop tests at each seniority.
Compare Uber with other data engineering employers
How the role, pay, and loop stack up against peer companies.
Prepare at Uber 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