Skip to main content
HireStepX is now in Beta! Be among the first to practise smarter and get hired on proof.
Technical · Uber

Uber Data Engineer Interview Questions India 2026

Uber's data-engineering rounds are streaming-heavy and metrics-obsessed, reflecting a business built on real-time supply and demand.

By the HireStepX editorial team · How we source and label this

Questions12
Rounds4
Intense3 of 12
FrameworkStream and standardise
Try it · Uber question 1 of 10
Standard

Reverse a linked list in O(1) extra space. Then explain when you'd use this in production.

Think of your answer first, then reveal how to structure it.
Practise this out loud

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.

Practice questions

  1. 01

    Reverse a linked list in O(1) extra space. Then explain when you'd use this in production.

    Standard
    Practise
  2. 02

    What is the difference between a class and an object? Give an example.

    Warm-upTCS Ninja/Digital tracks lean heavily on CS fundamentals: OOP, OS, DBMS, SQL basics. Expect rapid-fire Q's, not deep dives.
    Practise
  3. 03

    Write a SQL query to find the second-highest salary in a department.

    Warm-up
    Practise
  4. 04

    What is normalisation in databases? When would you de-normalise?

    Warm-up
    Practise
  5. 05

    What's the difference between a stack and a queue? Give a real-world use case for each.

    Warm-up
    Practise
  6. 06

    Given a stream of integers, design a data structure that returns the median in O(log n).

    Intense
    Practise
  7. 07

    You have a service that's slow only on Tuesdays. Walk me through how you'd debug.

    StandardGoogleyness: structured debugging, hypothesis-driven, instrumentation-first.
    Practise
  8. 08

    Here's 200 lines of payment-processing code with several intentional bugs. Find them and explain the production impact of each.

    IntenseStripe's signature 'bug bash' round. Off-by-one, race conditions, wrong error handling, edge cases in money math. Communicating impact > finding all bugs.
    Practise
  9. 09

    Explain webhooks vs. polling for a developer who has never built a payment integration. You have 4 sentences.

    StandardStripe values writing clarity above almost everything. Length-constrained explanation tests prioritisation of ideas.
    Practise
  10. 10

    Walk me through Razorpay's fraud-detection model. How would you reduce false positives without increasing chargeback losses?

    IntenseRazorpay ML rounds tie model decisions to ₹ impact, chargeback cost vs. blocked-good-txn cost. Pure ML answers without business framing fail.
    Practise
2 more questionsCreate a free account to see the full set and practise any of them with scoring.Unlock all questions
Prep notes

How to walk in ready.

The typical Uber recruitment process has 4 stages: Recruiter screen and technical pre-screen → SQL and data-manipulation round → Streaming pipeline and platform design round → Hiring-manager and behavioural round, then offer.

Uber typically conducts 4 interview rounds: 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.

HireStepX recommends the Stream and standardise framework for this type of interview: Design low-latency streaming with watermarks and geospatial bucketing, compute percentiles at scale with approximate algorithms, and standardise metrics via a semantic layer.

TCS Ninja/Digital tracks lean heavily on CS fundamentals: OOP, OS, DBMS, SQL basics. Expect rapid-fire Q's, not deep dives.

Googleyness: structured debugging, hypothesis-driven, instrumentation-first.

Stripe's signature 'bug bash' round. Off-by-one, race conditions, wrong error handling, edge cases in money math. Communicating impact > finding all bugs.

Designing pipelines that compute real-time supply/demand metrics per geohash from trip events, with windowing, watermarks, and explicit handling of out-of-order events.

Percentile computation such as median trip duration per city-hour, plus reasoning about approximate algorithms like t-digest to scale to billions of rows.

Practice

Rehearse the room before you enter it.

Run a mock Uber interview and get scored feedback on every answer.