J'ai postulé en ligne. J'ai passé un entretien chez Uber (Amsterdam) en juill. 2024
Entretien
I applied to the job through their career website. The interview process had the following rounds:
1. Recruiter call (30 minutes/Online): We discussed my qualifications and fit for the company. This was a standard recruiter call.
2. Live coding with hiring manager (60 minutes/Online): After a brief introduction, I solved a Leetcode 200 (Number of islands) variant. Passing this round led to an onsite interview.
3. Design & Architecture, New Problem (60 minutes/Onsite): I designed a chat system, as same as in Alex Xu's "System Design Interview – An insider's guide." We discussed how to scale it to Uber's scale.
4. Data Structures (60 minutes/Onsite): I solved a Leetcode 692 (top k frequent words) variant and discussed alternative solutions and their advantages/disadvantages.
5. Collaboration & Leadership, Design & Architecture - Previously Solved Problem Interview (75 minutes/Onsite): We conducted a behavioral interview and I presented a previously designed system architecture by me. The interviewer asked about the architecture, my involvement, potential failures, and decision-making steps.
6. Depth in specialization (60 minutes/Onsite): I solved a Leetcode 791 (custom sort string) variant and discussed production implementation and backend service architecture.
Unfortunately, I was rejected after completing all rounds. The feedback call revealed that I struggled to scale the design to Uber's scale in the third interview and missed how to implement my solution in production in the final interview.
I found three issues with the interview process:
Discrimination: Everyone except the recruiter seemed to look down on me due to my lack of experience at a big company, which was demoralizing.
Excessive coding rounds: Solving three Leetcode questions seemed excessive.
Same-day interviews without advancement: Completing all interviews on the same day, even after being rejected in the third round, was a waste of time.
Overall, I felt that this process lacked identity and was designed to hire only from other FAANG companies.
The phone screen lasted about 30 minutes and began with general questions about my background before diving into technical topics. I was asked to solve a DSA question on finding the top K frequent elements, discussing both the min-heap and bucket-sort approaches. Surprisingly, I had recently practiced a similar problem on the algorithm section of PracHub, which helped me articulate my thought process clearly. The interview continued with an onsite where I tackled system design and behavioral questions, and overall, the experience was straightforward and positive, leading to an offer that I happily accepted.
Questions d'entretien [1]
Question 1
Top K Frequent Elements: given an integer array and integer k, return the k most frequent elements. Walk through both the min-heap approach (O(n log k) time) and the bucket-sort approach (O(n) time), then discuss the trade-offs in time, space, and which one you'd pick for a streaming variant where new numbers keep arriving.
Surprisingly, the interview felt quite straightforward, especially for a senior role. I started with a technical screen, where I was asked to design an Uber Eats cart service. It caught me off guard initially, but then I remembered a specific mock I had practiced on PracHub that was nearly spot-on with this scenario. The final round included some behavioral questions, and although I received an offer, I ultimately decided to decline. Overall, it was a positive experience.
J'ai postulé en ligne. J'ai passé un entretien chez Uber (Bengaluru)
Entretien
Round 1 - Coding
Question: Count Rectangle-Line Intersections. Given a set of rectangles and a set of vertical line segments, count how many places the vertical lines intersect the rectangle edges (ignoring edge-on-edge overlaps).
Questions d'entretien [1]
Question 1
Count Rectangle-Line Intersections. Given a set of rectangles and a set of vertical line segments, count how many places the vertical lines intersect the rectangle edges.