Uber's data-engineering rounds are streaming-heavy and metrics-obsessed, reflecting a business built on real-time supply and demand.
In 2026 expect a streaming round on computing surge-relevant supply/demand metrics per geohash from trip events with bounded latency and out-of-order handling, a SQL round on percentile metrics (median trip duration per city-hour) and scaling to billions of rows with approximate algorithms, and a platform round on designing a self-serve semantic/metrics layer for consistent metric definitions. Interviewers reward precise reasoning about windowing, watermarks, geospatial bucketing, and metric governance rather than generic ETL. Uber pioneered internal metrics platforms, so governance thinking stands out.
About Uber
Uber India (Bengaluru) builds core platform engineering: the real-time matching engine, driver and rider experience, payments, and maps. Engineering culture is heavily influenced by ex-FAANG hires and prioritizes correctness, latency, and reliability.
Recruiter screen and technical pre-screen
SQL and data-manipulation round
Streaming pipeline and platform design round
Hiring-manager and behavioural round, then offer
Round 1 (45-60 min)
SQL round on percentiles and large-scale analytical queries.
Round 2 (60 min)
streaming pipeline design round with windowing and out-of-order handling.
Round 3 (45-60 min)
metrics-platform and semantic-layer design round.
Round 4 (45 min)
behavioural and hiring-manager round.
Sourced from 2+ candidate post-mortems. Hit Practice to answer any one with AI voice feedback.
2 more questions. Sign up to unlock all
Sign up free: unlock all questions