I applied through a recruiter. The process took 4 weeks. I interviewed at Uber (Seattle, WA)
Interview
I interviewed for an iOS engineer position. The whole process took about a month and a half. It could've gone faster, but I had some personal reason that caused the delay. I was contacted by a recruiter on LinkedIn. The whole process went pretty smoothly.
The phone screen was mainly solving a Leetcode question on HackerRank. I got an email the next day about passing the phone screen and scheduling the on-site.
The on-site interview is quite different from what I've experience. You need to bring your own laptop that has the dev tools you like. The first interview for me is an 1.5 hour time slot for me to build an iOS app with some requirements from the ground up. You can use any tools, libraries, package management system you like. I was in the room by myself for the most part unless I ran into any questions. After that, I met with a manager for behavioral interview during lunch. Then I met with the same interviewer from round 1 to do a deep dive on the app I wrote. After that I had a system design question. Then lastly I had a coding round, where I code on HackerRank and the code should be running and can run test cases.
Up until this point, everything went pretty smoothly and the people I met on-site are all super nice and friendly.
But after the on-site, the recruiter became quite unresponsive. She promised to get back to me by the end of the week, and didn't really gave me any information in a week and a half, not even a status update on why it's taking longer than expected. Once she told me I got the offer, she became super pushy. I told her I have other interviews that I want to get to, but she insisted that I gave her an answer in a week. I ended up having a counter offer and that bought me more time. I declined the Uber offer because the other offer is better. The recruiter was quite understanding about it in the end 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
