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.

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!

The Uber Software Engineer interview typically takes 4–6 weeks and begins with a recruiter screen focused on your experience, motivation, and role fit, followed by an online coding assessment or live coding screen with one or two algorithm problems that test correctness, efficiency, and communication. If you pass, you’ll have a technical phone interview solving a medium-to-hard coding problem with complexity discussion, and then a virtual onsite loop of about four to five one-hour rounds: a data-structures/algorithms coding interview, a machine-coding or low-level design round where you build a small system with clean, runnable code, a system design interview focused on large-scale distributed systems (often Uber-style problems like ride dispatch or surge pricing), and a behavioral interview assessing ownership, teamwork, and decision-making. Senior roles may include a project deep dive, and after all rounds a hiring committee reviews feedback before team matching and a final offer, with Uber evaluating problem solving, engineering fundamentals, system thinking, communication, and real-world impact throughout the process.