I applied through an employee referral. The process took 3 weeks. I interviewed at Uber in Oct 2015
Interview
I was referred by a friend. After that I had a basic phone screen to see who I was. After that, I had two technical phone screens. It took about one week for them to schedule the first one and then I waited two more weeks until the second. The first was pretty easy, a basic array algorithm questions that you would find in Cracking the Coding Interview. The second phone screen was much harder. There was only one question, but was much more involved to answer.
Interview questions [2]
Question 1
(Easier) You have a sorted array of integers. Find the element where the array index is equal to the value of the corresponding element. Or return that no such element exists.
(Harder) You have a dictionary of words. Create a matrix of letters such that each row of the matrix is a word and each column of the matrix is a word. Kind of like a very dense crossword puzzle.
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
