I applied online. The process took 4 weeks. I interviewed at Uber in Aug 2015
Interview
Applied online and was contacted by a recruiter the next day. I went through two technical phone interviews, each with a pair of engineers. The questions were fairly straight-forward. Some implementation questions, software architecture, and algorithm design.
After going through the first two interviews, I was informed by the recruiter that they wanted me to speak with a manager (it was not explicitly a technical). I then had a third phone interview scheduled with the recruiter. Over the course of the next week, the recruiter changed the time and manager on me five times before settling down on a date and person. By the time the third interview rolled around, I got called by a manager who wasn't the one I was scheduled to talk to. This manager seemed unprepared and was unaware of the position I wanted to take at the company (mobile development, more geared towards UI). This manager completely dismissed my design work and delved straight into a machine learning question (i never stated i had experience in this field). I was asked a few questions about how to improve an aspect of the Uber service. I responded with some naive answers about device-device communications, to which he shot down immediately and went deep into a machine learning topic.
The next day I was informed they would pick a different candidate.
The interview process started with a recruiter screen where they covered my background and the role's expectations. Next, I had a phone screen focused on technical skills where I faced a DSA question on frequent elements in an array. I had practiced similar problems on prachub.com beforehand, which helped me tackle it effectively. The technical rounds consisted of coding and system design questions, including rate limiting. Finally, I had a behavioral interview where they assessed cultural fit. Overall, the experience was average, but I received and accepted an offer.
I interviewed at Uber (San Francisco, CA) in Apr 2026
Interview
Recruiter screen then there was a hiring manager round which felt more like a mix of product sense + execution - mostly a mix of OOP algorithms in Python or Java and some high-level system design. The onsite was 5 back to back rounds covering data structures, database management (heavy on SQL and data lifecycles), deep sys design, and behavioral. The sys design round was the real test where I had to walk through building a scalable real-time gaming leaderboard, discussing tradeoffs ofcourse in architecture, APIs, and data flow. The coding rounds was around things like linked lists and tree traversals, while the behavioral part focused heavily on ownership of my code and handling feedback. When you prep, make sure you can go a level deeper on database management and object oriented patterns instead of just grinding LC I’d say. I did grind LC though but ensure you understand the depth behind everything you solve. I also did a few mocks with uber swe on prepfully specifically for the sys design and database rounds and that honestly helped me catch some blind spots in my architecture knowledge and practice explaining my tradeoffs clearly. I’d say get a mock or two from anywhere if you can - helped me a lot!
3
Top companies for "Compensation and Benefits" near you