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

Uber Software Engineer Interview Questions India 2026

Uber's SDE interview loop in India runs 4 to 5 rounds and is known for system design questions rooted in real Uber infrastructure: ride matching, surge pricing, geospatial queries, and real-time driver location tracking at millions of concurrent users.

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

Questions12
Rounds4
Intense9 of 12
FrameworkReal-time geo-scale design
Try it · Uber question 1 of 10
Intense

Design a system to predict same-day delivery feasibility for a new pincode in tier-3 India.

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

The design bar is set by what Uber actually runs in production, so interviewers will push back on naive solutions and ask you to reason about consistency vs availability trade-offs explicitly. DSA rounds cover medium to hard problems with an emphasis on graphs and greedy algorithms, reflecting the routing and matching problems that are central to Uber's business.

Practice questions

  1. 01

    Design a system to predict same-day delivery feasibility for a new pincode in tier-3 India.

    IntenseFlipkart engineering loves India-specific constraints: pincode coverage, monsoon patterns, kirana partnerships.
    Practise
  2. 02

    We're seeing UPI failure rates spike at 9pm on weekends. How would you debug, and what's your hypothesis?

    IntenseRazorpay loves real production scenarios: payments failures, NPCI rate limits, settlement reconciliation. Be specific.
    Practise
  3. 03

    Walk me through how you'd build idempotency into a payment retry system. What happens if the network drops mid-callback?

    Intense
    Practise
  4. 04

    Design Swiggy Genie's matching algorithm. How does it differ from food-order matching?

    Intense
    Practise
  5. 05

    Walk me through how you'd architect transaction-level fraud detection for 100M daily UPI transactions.

    IntensePhonePe engineering rounds are scale-obsessed: every answer should explicitly address throughput, latency, and cost at India scale.
    Practise
  6. 06

    How would you build a recommendation engine that suggests bills the user is about to forget?

    Standard
    Practise
  7. 07

    Design a cashback-allocation system that prevents abuse without alienating genuine users.

    Standard
    Practise
  8. 08

    Design a system to detect duplicate documents at web scale. What's your approximation strategy?

    IntenseGoogle SWE rounds prize first-principles thinking and explicit trade-off articulation. Always discuss what you're approximating.
    Practise
  9. 09

    Design Amazon Prime's recommendation engine. How would you handle the cold-start for a new Prime member?

    Intense
    Practise
  10. 10

    Design a URL shortener like bit.ly. Walk me through database choice and scaling.

    Standard
    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 5 stages: Recruiter screen: role and compensation alignment, 30 min → Coding screen: 1 to 2 DSA problems, typically graphs or arrays → On-site or virtual loop: 2 DSA rounds + 1 system design round → Hiring Manager round: behavioral, ownership, and culture fit → Offer, background check, and ESOP discussion.

Uber typically conducts 4 interview rounds: Coding Screen (45 min): 1 to 2 medium-hard DSA problems, often graph-based. Uber favours problems that reflect real product scenarios like shortest path or scheduling; DSA Rounds x2 (45 min each): Graphs, heaps, greedy, and dynamic programming. Interviewers ask you to articulate why your approach works before you start coding; System Design (60 to 75 min): Design a real-time system at Uber scale. Common prompts: design the driver location service, design surge pricing, design the ride-matching system. Start with the data model and consistency requirements before jumping to components. For the location service specifically, separate the write-heavy location-ping ingestion path from ETA reads; Hiring Manager Round (45 min): Ownership stories, cross-team collaboration, and why Uber. Prepare examples from your last two roles with measurable impact.

HireStepX recommends the Real-time geo-scale design framework for this type of interview: Start with geospatial data model, then consistency requirements, then pub-sub vs polling, then horizontal scaling strategy, then failure modes.

Flipkart engineering loves India-specific constraints: pincode coverage, monsoon patterns, kirana partnerships.

Razorpay loves real production scenarios: payments failures, NPCI rate limits, settlement reconciliation. Be specific.

PhonePe engineering rounds are scale-obsessed: every answer should explicitly address throughput, latency, and cost at India scale.

Google SWE rounds prize first-principles thinking and explicit trade-off articulation. Always discuss what you're approximating.

Ride matching at scale, real-time driver location tracking, surge pricing calculation, geospatial indexing (H3/quadtrees), and distributed rate limiting. Expect questions on consistency vs availability trade-offs explicitly.

Practice

Rehearse the room before you enter it.

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