J'ai passé un entretien chez Uber (Hyderâbâd) en nov. 2017
Entretien
Multi round interview. Started with online meeting with online editor. Had to switch camera on for some company policy - don't understand the real reason for not trusting the candidate. Expectation was to get correct output code for 2 problems in 40 mins - seems unfair considering you are coding on unfamiliar web IDE. Went ok for me. Following is onsite interview review. 4.5 hrs spent on site for 3 interviews.
Overall experience is marked negative because
1. I felt interviewers were rigid on expected solution on a non-calibrated design question. I still doubt their solution will work. Read thru answers to think about details.
2. Compared to other companies in this pay bracket the interview was unstructured (leave out coding round).
3. The reason for rejection given to me was not even checked in interviews.
Given two async streams -
Trip : {tripId, date, city}
Bill: {billId, tripId, date, amount}
Design a system to get real time aggregated view of following nature
City, TripCount, TotalAmount
Events in both streams can be out of sync or duplicate. But result needs to be accurate and realtime.
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.