Uber Data Engineer Interview Questions (2026)
The 15 Data Engineer interview questions most worth practising for Uber, selected from a bank of 239. Design and operate scalable data pipelines and platforms powering analytics and ML. Below: the interview process, the questions with answer outlines, the topics tested, and how to prepare.
Uber runs a fast, bar-heavy loop: a CodeSignal or live coding screen, then a virtual onsite with two coding rounds, a system design round steeped in real-time/marketplace problems, and a behavioral round mapped to its rewritten cultural norms. Uber India (Bangalore/Hyderabad) engineering interviews at the same global bar.
Questions
15
from a 239-question bank
Difficulty
Medium
from our question mix
Rounds
6
typical loop
Uber rating
4.02/5
Top 99% in Internet
Uber's interview process
- 1Recruiter Screen30 minEasy
Role targeting, level calibration and process expectations.
- 2Technical Phone Screen60 minMedium
One or two medium DSA problems (CodeSignal or live) with emphasis on correct, runnable code and edge cases.
- 3Onsite Coding I60 minHard
Practical problem such as building a rate limiter or an in-memory index, judged on working code and API cleanliness.
- 4Onsite Coding II60 minHard
Algorithmic problem often with a geospatial or streaming flavor, pushed to optimal complexity.
- 5System Design60 minHard
Design a real-time marketplace system (dispatch, ETA, surge) with hard follow-ups on scale, geo-sharding and failure modes.
- 6Behavioral / Hiring Manager Round45 minMedium
STAR stories mapped to Uber's cultural norms: ownership, bold bets, customer obsession and conflict handling.
Data Engineer interview questions for the Uber loop
- Q1
Design an event contract and schema registry process for Uber's mobile trip event stream producers and data consumers
MediumRound 6: System DesignData ContractsHow to answer:Define versioned schemas, compatibility rules, ownership, validation at ingestion, documentation, and a migration process for breaking changes.
- Q2
How would you model app open, ride request, driver dispatch, and pickup events for Uber?
MediumRound 2: Trip Lifecycle Data ModelingData ModelingHow to answer:Keep a raw immutable event table, create typed staging models per event family, and build a lifecycle or funnel fact for analysis. The raw layer supports audit and replay, while analytics models standardize timestamps, identities, and event names. Good answers address schema evolution and duplicate events.
- Q3
vehicle product attributes change over time at Uber. Design the dimension table
HardRound 2: Trip Lifecycle Data ModelingData ModelingHow to answer:Use an SCD Type 2 dimension with surrogate key, natural key, effective_start, effective_end, is_current, and tracked attributes. Facts should join to the dimension version valid at the fact timestamp. This allows historical analysis without overwriting old attributes when current-state source values change.
- Q4
Uber has anonymous events and logged-in events for riders. How would you model identity resolution?
SeniorRound 2: Trip Lifecycle Data ModelingData ModelingHow to answer:Maintain an identity graph that maps anonymous IDs, device IDs, and user IDs with validity windows and confidence levels. Analytics models should choose the identity appropriate to the metric, such as session-level or account-level. The explanation should address privacy, merge/split corrections, and reproducibility of historical metrics.
- Q5
How would you model semi-structured attributes from app open payloads at Uber?
MediumRound 2: Trip Lifecycle Data ModelingData ModelingHow to answer:Store raw payloads for replay, then extract stable high-value attributes into typed columns. For sparse or rapidly changing attributes, use a key-value satellite table only when analysts need flexibility and understand its costs. The explanation should cover schema drift, data types, and query performance.
- Q6
What aggregate tables would you create for high-traffic Uber dashboards on completed trips?
MediumRound 2: Trip Lifecycle Data ModelingData ModelingHow to answer:Create daily aggregates by common dimensions such as city, vehicle product, and time of day, while preserving a detailed fact for drilldown. Aggregates should be derived from canonical facts and tested against them. The answer should mention freshness, backfill, and avoiding a separate business definition in the aggregate.
- Q7
How would you partition large Uber tables driven by location pings and dispatch events?
MediumRound 7: Real-Time Warehouse & Quality DesignData WarehousingHow to answer:Partition primarily by event or business date, and consider clustering or sorting by common filters such as city and entity keys. Partitioning should match access patterns and retention policies. The answer should mention avoiding too many tiny partitions and validating improvements with actual query plans.
- Q8
Uber needs to backfill one year of trip financials fact. How would you run it without disrupting production?
HardRound 7: Real-Time Warehouse & Quality DesignData WarehousingHow to answer:Use a separate compute pool, process partitions in batches, validate row counts and metrics incrementally, and avoid overwriting production until checks pass. Communicate expected downstream changes and freeze schema during the backfill. The explanation should mention rollback, checkpointing, and cost monitoring.
- Q9
How should the warehouse handle schema changes in app open payloads at Uber?
MediumRound 7: Real-Time Warehouse & Quality DesignData WarehousingHow to answer:Ingest raw payloads flexibly, validate expected columns in staging, and use additive changes whenever possible. Breaking changes should trigger alerts and coordinated downstream migrations. The explanation should include versioned event contracts and a compatibility window for producers and consumers.
- Q10
What warehouse access controls are needed for user-level trip data at Uber?
MediumRound 7: Real-Time Warehouse & Quality DesignData WarehousingHow to answer:Use role-based access, column masking, row-level filters, and audited grants based on least privilege. Sensitive identifiers should be hashed or hidden unless needed. The explanation should mention separate access for raw PII, aggregated marts, and certified dashboards.
- Q11
Design a star schema for Uber's ride-sharing marketplace that supports reporting on completed trips, gross bookings, and request -> match -> pickup -> completion
MediumRound 4: Data ModelingDimensional ModelingHow to answer:Define a clear fact grain for trips, add conformed dimensions such as city, rider, and driver dimensions, and store additive measures separately from derived metrics.
- Q12
Design reconciliation logic for Uber's ETL so gross bookings in mobility data lakehouse matches the operational source
MediumRound 5: ETL DesignETL ReconciliationHow to answer:Compare control totals by date and city, track accepted tolerances, investigate deltas, and block publishing on material mismatches.
- Q13
For Uber, decide between ETL and ELT for transforming trip, driver-location, and pricing events. What factors drive your choice?
MediumRound 5: ETL DesignETL vs ELTHow to answer:Choose ELT when the warehouse/lakehouse can scale transformations cheaply; choose ETL when privacy, bandwidth, or source constraints require pre-load shaping.
- Q14
What interference risks exist in Uber's mobility marketplace experiments, and how would you mitigate them?
SeniorRound 6: Dispatch & Pricing Experimentation CaseExperimentationHow to answer:Interference occurs when one user's treatment affects another user's outcome, which is common in marketplaces, recommendations, capacity-constrained systems, or shared infrastructure. Mitigate with cluster randomization, switchback tests, geo experiments, or careful metric interpretation. The answer should connect design to the actual spillover mechanism.
- Q15
What should be logged for exposure in Uber's dispatch matching change experiment?
HardRound 6: Dispatch & Pricing Experimentation CaseExperimentationHow to answer:Log assignment id, variant, user or cluster id, exposure timestamp, experiment version, eligibility context, and relevant request metadata. Exposure should represent the moment the user could be affected by treatment. The explanation should distinguish assignment from exposure and mention idempotent logging.
Practice these with instant AI feedback in a live mock interview → Start a Uber Data Engineer mock
Topics tested most
How to prepare for the Uber Data Engineer interview
Strong DSA and scalable system design; prepare analytical/behavioral stories
Indicative Data Engineer pay in India: ~₹10–45 LPA (role-level range, not a Uber-specific figure).
Frequently asked questions
How hard is the Uber Data Engineer interview?
Based on our 239-question Data Engineer bank for the Uber loop, the overall difficulty is medium (Uber's process is generally rated elevated). Expect around 6 rounds spanning Data Modeling, Data Warehousing, Experimentation.
How many interview rounds does Uber have for a Data Engineer?
Uber typically runs about 6 rounds for Data Engineer candidates: Recruiter Screen → Technical Phone Screen → Onsite Coding I → Onsite Coding II → System Design.
What is the interview process at Uber?
The Uber interview process typically runs: Recruiter screen -> technical screen -> onsite (coding x2, system design, behavioral). Prepare for each round in order rather than only the first — the later stages usually carry the most weight.
How hard is the Uber interview?
Uber interviews are rated high difficulty. The bar is highest on coding — go deep there and practise explaining your reasoning out loud.
What does Uber look for in candidates?
Uber focuses on Coding, large-scale system design, analytical thinking. Culturally, it values We build globally, customer obsession, bold bets, ownership. Line up your examples to hit both the technical bar and these values.
Explore more
Other roles at Uber
Data Engineer interviews at other companies
Compiled by PrepNPlaced from 239+ interview reports and question banks for the Uber Data Engineer loop, cross-referenced with 1,075 employee reviews. Data refreshed 2026-08-13. Updated 2026.