My Successful Interview Journey at Uber: Landing the Sr. Software Engineer L5A Offer

5 min read
May 19, 2024

Hello everyone,

Since I rejoined Uber, I've had numerous individuals ask me about the interview process and how to get ready for it. To assist with that, I've put together a summary of my interview experience in this article. I hope you find it helpful.

To land a Software Engineer role at Uber, you'll need to focus your preparation on two key areas. Here are some of the resources I found helpful while preparing for the L5A (Senior Software Engineer) position.

Data Structures and Algorithms

  • Leetcode Blind 75 Questions: Begin by solidifying your fundamental understanding of commonly used and frequently asked Data Structures. Once you have a firm grasp on these concepts, start working through various problems. Identify the points where you struggle and the areas that challenge you within the given time limits.
  • Grind75, a creation of TechInterviewHandbook, offers a comprehensive guide for individuals preparing for technical interviews. This resource simplifies the study process, making it easier for users to tackle complex topics efficiently.

System Design and Architecture

  • Grokking the System Design Interview: Discover the art of designing large-scale systems by exploring key examples such as TinyURL, Facebook, Twitter, Uber, and more.
  • Check out some YouTube channels for additional preparation, such as codeKarle, ByteByteGo, and TechDummiesNarendraL.
  • Sure! Here is a rewritten version of the text while keeping the mood and tone similar: Welcome to the System Design Primer. This repository aims to enhance your system design abilities through a collection of comprehensive guides. By exploring these resources, you can broaden your understanding of designing robust and scalable systems. Whether you're preparing for interviews or striving to improve your knowledge, the System Design Primer offers valuable insights. Feel free to navigate through the repository, refer to the detailed explanations, and make the most of the illustrative examples provided. Dive in and elevate your system design skills to the next level!

My interview experience for an L5A position included five rounds in total. The process is quite similar if you're applying for an L4 role. It's also a good idea to confirm all the details of the process with your recruiting coordinator.

Round 1: Coding BPS (1 hour).

This was an Elimination Round in which I was presented with a coding question similar to those found on LeetCode at a medium difficulty level. The question primarily assessed my core understanding of Data Structures and Algorithms (DSA). It also tested my ability to write well-structured classes, maintain a modular code structure, and use good naming conventions for variables and classes, among other fundamentals.

If you pass this round, the next four rounds will be arranged for you, regardless of how you perform in those rounds.

Round 2: Algorithms and Data Structures (1 hr).

This key Software Engineering round centers around Algorithms and Data Structures. The initial 5 minutes will be dedicated to introductions of both the panelists and the candidate, and the final 5 minutes will allow time for any questions. You'll have 50 minutes to engage in discussions about coding problems.

I faced a total of three questions. The first one focused on Dynamic Programming and had a Leetcode Medium level of difficulty. I managed to come up with a working solution in about 15 minutes. Following this, I received a follow-up question, which I also solved in the next 15 minutes. With 15 minutes still remaining, the panelist posed another question where I didn't need to implement the solution. I explained my approach verbally and then proceeded to the segment where I got to ask questions about the team.

Round 3: In-Depth Specialization (1 hr)

This is the second coding round, but the emphasis shifts from Algorithms and Data Structures to assessing your ability to write production-ready code. Several key factors will be evaluated in your code, such as: adhering to the Single Responsibility Principle by creating distinct classes for specific tasks, utilizing object-oriented programming to instantiate classes and invoke relevant methods, employing good naming conventions for variables and methods, and maintaining proper indentations for readability, among others.

I managed to incorporate various classes and methods while simultaneously addressing the main issue using the appropriate data structures. The final 10 minutes were once again reserved for questions.

Round 4: Design and Architecture (New Problem) (1hr). Maintain the original mood and tone while ensuring it sounds fresh and engaging.

The System Design round is crucial for the L5 role because it tests your skills as a Senior Software Engineer. Typically, this round presents you with a Greenfield problem statement. Your first step is to clarify the requirements, then estimate the necessary resources. After that, you need to outline a high-level design for the system and dive into the detailed aspects, including API design and Database design. Once your design is set, it's essential to identify potential bottlenecks and failure points, and suggest solutions to scale your system to handle high load.

Round 5: Teamwork and Leadership, Design and Architecture (Problem Solved Previously) (1 hour 15 minutes). Keep the mood and tone of the text and don't rewrite phrases and HTML tags.

This phase is led by a Manager and involves a combination of Behavioural questions along with a conversation about the systems that were previously designed.

During my interview, we spent the initial 45 minutes talking about the projects I had previously undertaken. We delved into the design choices I made, the lessons learned, potential improvements, and how I would tackle the same problems differently today.

Over the next 30 minutes, we talked about strategies for tackling leadership challenges, improving conflict resolution, enhancing collaboration with colleagues, and establishing standard practices to foster a positive team culture.

After these rounds, the recruiting coordinator contacted me with the interview feedback and the offer details 🎊.

I started working at Uber on April 1, 2024, and at the time of writing about my interview experience (May 1, 2024), I've been with the company for one month.

Also, this isn’t my first stint with Uber; I was previously employed here from July 2021 to November 2022. This time around, I'm part of a different team, but both my new and old colleagues have been incredibly welcoming. Many, many thanks to everyone ❤️.

Read more in Tech