Uber SDE-1 2025 || Interview Experience || Pending Status
Summary
I interviewed for the SDE-1 role at Uber, completing four rounds covering technical coding, a graph-based problem with a real-world scenario, low-level design, and a hiring manager round focusing on behavioral aspects. I am currently awaiting the final decision.
Full Experience
π£οΈ My Uber SDE-1 Interview Experience π
I recently interviewed for the SDE-1 role at Uber and wanted to share my experience to help others who might be preparing. Hereβs a breakdown of the process:
π Total Rounds: 4
π Round 1: Technical Coding (DSA Elimination Round)
- Got two problems:
- A medium-hard graph problem, requiring a DFS/BFS-based approach.
- A conceptual discussion around the classic Edit Distance problem.
- I was able to solve both efficiently and optimally.
- The interviewer seemed satisfied with my approach and clarity of explanation.
- I think , I will get hire/strong hire from this round.
π Round 2: Problem Solving with a Twist (Uber Story Style)
- The question was framed in an Uber real-world scenario.There is a city connected to each other , where we want to put maximum number of Uber cabs to reach each and every location fast.
- Simplified the problem , I had to find all nodes from which the maximum distance to other nodes is minimized.
- It was a blend of graph algorithms and topological sorting.
- Take all the leaf Nodes and run toposort from all leaf Nodes and you will get the centre of the graph.
- Took a bit of time but was able to arrive at a correct and optimized solution.
- I think , I will get hire/lean hire as I was not that quick in this round , took a lot of time to understand the problem but solved correctly in the most optimized way.
π Round 3: Low-Level Design (LLD)
- This round didnβt go as well.
- The task was to implement a design problem with appropriate classes, methods, and logic.
- There is a company , who has employees and a referal bonus system , where one employee will get some bonus for referring another one.
- I had to implement it from the scratch and interviewer wanted to query on the employee or the company.
- I misunderstood some part of the requirement and implemented the logic incorrectly.
- Tried to correct it mid-way, but ran out of time to fully recover.
- As I communicated properly and wrote clean code with proper structure , hoping for atleast lean Hire :)
π Round 4: Hiring Manager (HM) Round
- Focused more on behavioral questions, past projects, and team fit.
- Discussed decision-making, ownership, challenges Iβve faced, and how I handled them.
- Overall, it was a calm and friendly discussion.
- Expecting a hire from here.
π― Takeaways:
- Be strong with graph algorithms (especially BFS/DFS and shortest-path problems).
- Expect real-world story-based questions that map to classic CS problems.
- For LLD, practice clarifying requirements before coding, and rehearse end-to-end implementations :).
Still waiting on the final decision, but I hope this helps someone preparing for similar roles. Feel free to connect or ask if you have questions β happy to help!
Interview Questions (3)
The question was framed in an Uber real-world scenario: There is a city connected to each other, where we want to put maximum number of Uber cabs to reach each and every location fast. Simplified, I had to find all nodes from which the maximum distance to other nodes is minimized.
Implement a low-level design problem for a company that has employees and a referral bonus system, where one employee gets a bonus for referring another. The task was to implement this system from scratch, allowing the interviewer to query on the employee or the company.
Focused on behavioral questions, past projects, and team fit. Discussed my decision-making process, sense of ownership, challenges Iβve faced, and how I handled them.