I applied through a recruiter. The process took 2 weeks. I interviewed at Uber (Palo Alto, CA) in Jul 2018
Interview
Standard tech hiring process.
1. Initial call with recruiter.
2. Phone screen for an hour.
3. 5 onsite interviews. (2 coding, 1 design, 1 current project review, 1 bar raiser behavioral)
External Uber recruiter reached out to me for the initial rounds. For onsite interviews, internal Uber HR was assigned. The recruiter was supposed to setup a 15 min call with me before onsite to give me some familiarity about the rounds and the teams I would be interviewing with. I tried to follow-up with the recruiter to setup this call several times but the recruiter never responded to any of my questions and my onsite was setup by the coordinator. I agreed to onsite with no clue about the teams I am being considered for which was my mistake but hoped my onsite experience would be better.
On the day of my onsite, I reached Uber office and the recruiter never showed up after waiting for 25 mins. I then asked the receptionist to reach out to that recruiter again as it was time for my initial interview and someone else showed up saying the recruiter was busy. I still hoped the recruiter would show up after all the rounds but still nowhere to be seen. I didn't even bother to thank the recruiter or follow-up after onsite.
Interview questions [1]
Question 1
Technical rounds were fun & engaging and I hadn't solved those previously. Could have done little better in design & behavorial round though.
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
