The Uber system design interview often starts with a prompt that looks simple, then tests how far you can push the design. Follow-ups target databases, scaling, and the hot paths in your architecture.
Many Uber prompts come from its own products, such as rider-driver matching or the Uber Eats homepage. Some interviewers also add ranking or ML follow-ups once the core design is in place.
Uber's loop varies by team, level, and role, and system design can appear in a technical round, the onsite, or both. Senior candidates may also get a past-project round that works like a design interview.
Uber's system design rounds
Uber's engineering loop can include system design in up to 3 places. Which ones you get depends on your level and the team you're interviewing with.
| Stage | Format | What to expect |
|---|---|---|
| Technical round | A 60-minute session that can mix coding and design | A design prompt after a coding question, such as a car rental or stock ticker system |
| Onsite system design | About 60 minutes, with roughly 40 minutes on the whiteboard | A product-based prompt with follow-ups on scale, caching, and data |
| Past-project round | A technical retrospective for senior candidates | Pushback on the design decisions in a project you led |
Mid-level candidates have gotten system design prompts in a combined technical round before the onsite. Prepare to switch from coding to design in the same session.
Engineering manager loops include system design too. A staff EM candidate got a design prompt in a technical round, separate from the leadership interviews.
What to expect
Remote Uber system design rounds often use CodeSignal's whiteboard. Practice sketching and talking through a design on a digital canvas before your interview.
Three traits set the Uber round apart from other companies:
- Prompts often come from Uber's own products, such as ride matching, food delivery, and fleet tracking.
- Interviewers expect you to cover the high-level design fast, then spend most of the round on scale and design decisions.
- Follow-ups can move into new territory mid-round, such as top K rankings by region or how ML fits into the design.
One staff candidate described the Uber Eats homepage prompt as "deceptively simple." The point of the round was to see how far they could go once the obvious design was done.
Depth expectations vary by level. Mid-level and entry-level candidates tend to get simpler, high-level prompts that aren't Uber-specific, while senior and staff candidates describe deeper, product-specific follow-ups.
What Uber evaluates
Uber scores how well you understand the decisions behind your design. Interviewers look at these dimensions:
- Requirements gathering: Uber values careful scoping before you draw anything. Ask about users, regions, and peak traffic first.
- Database and scaling knowledge: Candidates say interviewers expect understanding well beyond the high-level architecture. Justify your storage choices and explain how they hold up under load.
- Tradeoffs: Strong answers compare more than one option. Explain what you give up with each choice.
- Hot-path optimization: Interviewers want to see where you'd cache and optimize the busiest requests. Name the read and write paths that matter most.
- Adaptability: Follow-ups can change the scope mid-round. Show that your design can absorb a new requirement without starting over.
Uber system design questions
Uber system design interview questions center on real-time marketplaces, delivery, and tracking. Practice these, and find more in the Uber question bank.
Uber product prompts:
- Design Uber.
- Design Uber's driver-rider matching system.
- Design Uber Eats.
- Design the Uber Eats homepage, then build a top K list of restaurants per region.
- Design a truck tracking system with filtering by truck number and driver status updates.
- Design a gift card redemption flow.
General prompts:
- Design a car rental system.
- Design a stock ticker system.
- Design Robinhood.
- Design a malware scanner reporting dashboard.
- Design a new food startup.
How to prepare
Focus your prep on marketplace designs and the data decisions behind them. Work through these steps:
- Practice delivery and marketplace designs: Work through Design Uber Eats end to end. Cover matching, order status, live location, and lunch and dinner traffic spikes.
- Review databases and scaling: Practice choosing between SQL and NoSQL for a given workload. Explain partitioning, replication, and what fails first under load.
- Prepare for ranking follow-ups: Be ready to explain a basic ranking flow: generate candidates, build features, rank, and return the top K. You don't need to know the model math.
- Practice booking and inventory designs: Work through a hotel booking service. The reservation logic carries over to car rental and gift card prompts.
- Review general prompts: Practice a feed design like Design Instagram and a real-time game like Design Chess.com. Both appear in the Uber software engineer guide's practice list.
- Prepare a past project: If you're senior or above, pick one project you led and map its architecture. Expect pushback on why you made each decision.
- Run timed mock interviews: Practice a full design out loud with a partner who changes the scope mid-round. Book mock interviews to test your timing.
Common mistakes
Avoid these mistakes in your Uber system design round:
- Stopping at the high-level design: Uber interviewers expect you to go further. Plan for most of the round to cover scale, caching, and data.
- Skipping peak traffic: Ride and delivery demand spikes at predictable times. Size your design for peak load.
- Freezing on a new follow-up: Scope changes such as regional rankings or ML are part of the round. Restate the new requirement and extend your design from there.
- Ignoring real-time updates: Location and order status change by the second in Uber prompts. Explain how updates reach riders, drivers, and restaurants.
- Treating the EM loop as nontechnical: Engineering manager candidates still get design prompts. Prepare a full design alongside your leadership stories.
FAQs
How long is the Uber system design interview?
The Uber onsite system design round lasts about 60 minutes. Plan to spend roughly 40 minutes designing and save the last 15 minutes for follow-ups and your own questions.
What system design questions does Uber ask?
Uber system design questions include designing Uber, Uber Eats, driver-rider matching, and a truck tracking system. General prompts such as a car rental system or stock ticker also appear.
Do Uber engineering managers get a system design round?
Uber engineering manager loops can include a system design round. A staff EM candidate got a design prompt in a technical round, alongside separate leadership interviews.
Does Uber ask ML questions in system design?
Some Uber interviewers add ML follow-ups to product design prompts, such as ranking restaurants on the Uber Eats homepage. A staff software engineer candidate got this follow-up in the final loop.
Is the Uber system design round different by level?
The round changes with your level. Mid-level candidates tend to get simpler, high-level prompts, while senior candidates may also get a past-project round with design pushback.
Resources
Use these to keep preparing for your Uber design round:
Want to ace your System Design interviews?
Try our System Design interview course for mock interviews, frameworks, and more.
Start course for freeΒ βGet 1-1 coaching