I applied through university. I interviewed at Uber in Oct 2016
Interview
Uber was far too slow throughout the entire process. They told me in mid-September that they wanted to interview me, and from the very beginning, I told them that I had a deadline of November 1st with other companies. It took them almost an entire month to finally schedule the interview, during which, I contacted my recruiter multiple reminding him of the deadline and he assured me that I could complete the process with Uber in time. When they did finally get back to me, the phone interview was scheduled for Mid-October, which I passed. Afterwards, I get an email asking me to give them my availabilities for an onsite. I list them, but the only time they had listed was the end of October. I responded within minutes of receiving the email and asked for the earliest of the days, he listed, but also asked if it was at all possible to do it earlier. Instead, he took a full day to respond telling me the day I chose was full, and the earliest I could do was days later, and as such, I wasn't able to do the onsite.
Interview questions [1]
Question 1
Standard Algorithms questions. Reading Crack the Coding Interview really helps.
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!