2 coding phases + 1 system design + 1 behavior.
It followed the Big Tech interview process.
The interviewers were nice and supportive,
I really enjoyed the process.
You must be sharp at your coding skills for sure,
they are very technical.
1
Altre recensioni di colloqui per Sr. Software Engineer presso Uber
Ho presentato la mia candidatura online. Ho sostenuto un colloquio presso Uber (Bengaluru)
Colloquio
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).
Domande di colloquio [1]
Domanda 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.
A former colleague referred me to this opportunity, so the initial call felt friendly. The process included a phone screen focused on behavioral questions. Next came a technical round where I had to design a large-scale driver-rider matching system, tackling aspects like geospatial indexing and handling outages. Funny enough, the PracHub mock interview I had done a week earlier mirrored that exact problem closely. The overall experience was decent, but I didn't receive an offer in the end, which was disappointing.
Domande di colloquio [1]
Domanda 1
Design Uber's driver-rider matching system. Cover how you'd match riders to nearby drivers in real time at city scale, your geospatial indexing approach (geohash vs quadtree vs H3), how you'd handle surge zones, and the tradeoffs between match latency and match quality. Then discuss how the system degrades gracefully during a regional outage.
