Uber Backend Engineer interview questions

5 Backend Engineers have shared notes from their Uber interviews, with the questions they were asked in each round. That is 2% of the 263 Uber interview notes on Screna AI.

5 Backend Engineer interview notes

Uber·Backend Engineer·Technical Phone Screen

Jun 2026
Did a technical phone screen for a backend role at Uber. One coding question, BFS-based, with a follow-up twist that actually made it more interesting. Passed and got moved forward to HR scheduling.
  • You're given a matrix with only dashes and letters. Replace each dash with the nearest letter (distance 1). If multiple letters are equidistant, pick alphabetically the smallest one.

“Recognized it pretty fast as a multi-source BFS thing, similar to the walls and gates problem.”

View Post

Uber·Backend Engineer·Technical Phone Screen

Jun 2026
Uber backend interview that went deep into dynamic graph connectivity, specifically a variant of the rider-connection problem where you have to handle both union and deletion operations on a graph over time. Harder than I expected and I'm not sure I fully nailed the complexity analysis.
  • You have a time-sorted event log with two types of events: two riders sharing a ride (connecting them in a graph), and one rider blocking another (removing that edge and potentially splitting a connected component). Find the earliest timestamp at which all riders belong to a single connected component. Standard union-find won't work because it doesn't support deletions. What's your approach, and what's the time complexity?

“This wrecked me a little.”

View Post

Uber·Backend Engineer·Onsite - System Design / Architecture

May 2026
Uber backend interview centered on a classic OO design problem, parking lot, but with enough depth in the discussion that it didn't feel like a checkbox exercise. The concurrency angle caught me a bit off guard and I think that's where I lost some points.
  • Design and implement an object-oriented model for a parking lot system, including vehicles, spots, levels, tickets, and pricing.
  • How would you implement the search strategy for finding the next available spot efficiently?
  • Two vehicles arrive at the same level at the same time. How do you ensure they don't get assigned the same spot?
  • How would you extend this system to support EV charging spots, reservations, and license-plate-based entry and exit?
  • Walk through the park and leave API design, including what a ticket looks like and how fees are calculated.

“Started with the class hierarchy and felt pretty good about it.”

View Post

Uber·Backend Engineer·Onsite - System Design / Architecture

May 2026
System design round at Uber for a backend role. The whole session was basically one big question about shopping cart architecture for a food delivery app, and it went pretty deep into tradeoffs I hadn't fully thought through before.
  • Design the shopping cart service for a food delivery platform like Uber Eats, covering item management, cross-device persistence, menu reconciliation, and checkout integration.
  • How would you handle two devices editing the same cart at the same time? Walk through your concurrency strategy.
  • The cart is persisted server-side. What storage technology would you choose and why, and how do you handle abandoned carts?
  • How do you keep the cart consistent with live menu data, especially around price changes or items going out of stock?
  • How would you design the API for cart operations to handle client retries safely?
  • How would you apply promotions, coupons, taxes, and delivery fees at checkout, and where does that logic live in the system?

“This was the core question and it sprawled.”

View Post

Uber·Backend Engineer·Technical Phone Screen

May 2026
Uber backend interview with a combinatorics-heavy coding question. The problem was deceptively math-y for what I expected to be a straightforward algorithms round.
  • Given a 1D array of houses where some are initially infected, and each day an infected house can spread to one of its immediate neighbors, count the total number of distinct orderings in which all healthy houses become infected.

“I stared at this for a bit before realizing it's a counting problem, not a simulation.”

View Post