Uber | SDE 2 | Interview Experience | Rejected
Summary
I interviewed for an SDE 2 role at Uber, which included an online assessment and five interview rounds covering Data Structures & Algorithms, Low-Level Design, High-Level Design, and behavioral questions. Despite receiving positive feedback, I was ultimately rejected for not exceeding the bar.
Full Experience
There was 1 online test followed by 5 rounds of interviews.
For online assessment I don't remember exact questions but 3 questions were easy and last question was bit trick which I guess can be solved with BST.
Round 1 - This was elimination round We are given an array, minRange, maxRange. Need to count number of subarrays which have both minRange and maxRange inside them and all other elements in the subarray should be between the range.
After that there were 3 interviews scheduled.
1 DSA - Was asked to build a system in which we are getting stream of userIds visiting a website. And we need a functionality to return the first user who visited website only once till now.
2 LLD - Design similar to org chart which we have on teams. There were multiple requirement. Like allocate budget. Add manager, add IC, remove manager, remove IC and few more requirements
3 HLD - Design chat application. There were no exact requirement but discussed about all these - Handling 1:1 chatting, grp chatting, offline message, handling sudden surge of messages. DB design, API contracts, websockets.
After 2-3 days got a call from recruiter to schedule HM round In this rounds there was indepth discussion about my past project and few behavioural questions. This felt like stress test back to back question, cross questions.
Received Feedback after 3 days that overall it was +ve. You are meeting the bar but not exceeding it so we can't proceed. So bascially it is not -ve but not extremely +ve 🤷🏻♂️
Interview Questions (5)
Given an array, minRange, maxRange. Need to count number of subarrays which have both minRange and maxRange inside them and all other elements in the subarray should be between the range.
Build a system in which we are getting stream of userIds visiting a website. And we need a functionality to return the first user who visited website only once till now.
Design a system similar to an org chart on teams. There were multiple requirements, including: allocate budget, add manager, add IC, remove manager, remove IC, and a few more requirements.
Design a chat application. Discussion covered topics such as handling 1:1 chatting, group chatting, offline messages, handling sudden surges of messages, database design, API contracts, and websockets.
In-depth discussion about my past projects and several behavioral questions. This round felt like a stress test with back-to-back questions and cross-questions.