Uber

Uber's process is a standard product-company loop, run mostly over video. For engineering it typically takes four to six weeks from first contact to offer.

1. Application and resume review

Apply on the Uber careers site, through a referral or via a portal such as Jobaaj. Recruiters look for depth in a relevant stack, impact on real products and, for business roles, evidence of owning metrics.

2. Recruiter call

A short conversation on your background, the team you are being considered for, level expectations and logistics. The recruiter explains the loop and shares preparation guidance.

3. Online coding assessment or technical phone screen

Engineering candidates either complete a timed online assessment with two or three coding problems or do a live 60 minute coding interview with an engineer. Data roles get SQL and statistics questions; business roles get a case or analytics exercise instead.

4. Virtual onsite loop

Three to five interviews on one or two days: coding, system design (for mid-level and above), a deep dive into a past project, and a behavioural interview. Product and business candidates get product sense, analytics, execution and leadership rounds.

5. Bar-raiser or hiring manager round

An interviewer from outside the team checks that the candidate meets Uber's overall bar, focusing on values, judgement and collaboration. The hiring manager may also meet you to discuss the team and role.

6. Debrief, offer and background check

Interviewers submit feedback, a hiring committee or the hiring manager decides, and the recruiter shares the offer. Background verification is completed before the start date.

The rounds below describe the software engineering loop in Uber's Indian tech centres. Data, product and operations roles follow the same structure with function-specific content.

Round 1: Online assessment or phone screen

Roughly 60 to 90 minutes. Two or three problems of medium difficulty on a coding platform, or a live session with an engineer. Correctness, edge cases and complexity all count.

• Arrays, strings, hashing and two-pointer techniques
• Graph traversal, shortest paths and union-find
• Heap and interval problems such as merging rides or scheduling

Round 2: Coding interviews

Two 45 to 60 minute sessions with engineers. Problems are medium to hard and interviewers look at how you clarify requirements, structure code and test it, not only whether you reach the optimal answer.

• Dynamic programming and recursion
• Designing a data structure such as an LRU cache or rate limiter
• Concurrency basics for backend roles

Round 3: System design

For mid-level and senior engineers. A 60 minute open-ended design discussion covering requirements, scale, data model, APIs and trade-offs, often around problems close to Uber's domain.

• Design a ride-matching or dispatch service
• Design real-time location tracking for millions of drivers
• Payments reconciliation and idempotency

Round 4: Project deep dive

You walk the interviewer through a significant project you owned. They probe architecture decisions, what went wrong, how you measured impact and what you would do differently.

• Why you chose a particular technology or design
• How you handled production incidents or scaling issues
• Trade-offs between speed and quality

Round 5: Behavioural and bar-raiser interview

A 45 minute conversation with a manager or bar raiser on ownership, collaboration, dealing with ambiguity and ethics, using examples from your past work.

• A time you disagreed with a decision and what you did
• Handling a conflict with a teammate or stakeholder
• Why Uber and what you want to build here