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.” The rest of the author's notes on Backend Engineer interview at Uber, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.
View Post