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.
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.
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: 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
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.
Hiring Manager Round (45 min)
Ownership stories, cross-team collaboration, and why Uber. Prepare examples from your last two roles with measurable impact.
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 questionsThe 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.; 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.
To answer this question well, HireStepX recommends the Real-time geo-scale design approach: Start with geospatial data model, then consistency requirements, then pub-sub vs polling, then horizontal scaling strategy, then failure modes. Ground your answer in a specific real example from your own experience.
To answer this question well, HireStepX recommends the Real-time geo-scale design approach: Start with geospatial data model, then consistency requirements, then pub-sub vs polling, then horizontal scaling strategy, then failure modes. Ground your answer in a specific real example from your own experience.
To answer this question well, HireStepX recommends the Real-time geo-scale design approach: Start with geospatial data model, then consistency requirements, then pub-sub vs polling, then horizontal scaling strategy, then failure modes. Ground your answer in a specific real example from your own experience.
To answer this question well, HireStepX recommends the Real-time geo-scale design approach: Start with geospatial data model, then consistency requirements, then pub-sub vs polling, then horizontal scaling strategy, then failure modes. Ground your answer in a specific real example from your own experience.
To answer this question well, HireStepX recommends the Real-time geo-scale design approach: Start with geospatial data model, then consistency requirements, then pub-sub vs polling, then horizontal scaling strategy, then failure modes. Ground your answer in a specific real example from your own experience.