There were a total of five rounds:

• Machine Coding
• Problem Solving
• Architecture
• Hiring Manager
• Bar Raiser

Uber looks for a very specific skill set of engineers for their backend teams. I chose a non-Java/Go language for my Machine Coding round, given my comfortability, and that negated the complexity of the round, apart from it not being understandable enough to the interviewer. The Problem Solving round consisted of a graph-based question, first easy, then medium, and then hard. I felt it was too late for feedback from the interviewer to be able to do anything about the hard part or to correct it. I don't think I was way off the actual logic, but it should have been given more attention before I started to code. Architecture went well, but they asked a very standard question that wasn't enough to test or differentiate my skills with respect to other candidates. I would have rather expected some very Uber-like problems related to locations and rides. The Bar Raiser and Hiring Manager rounds were standard interviews that focused more on my current work, questions on processes and people, and tough problems I had faced, apart from assessing if I am a culture fit.

I would probably clear the interviews if I gave them again, given that I had chosen a wrong language for the Machine Coding round (should have gone with Go, which was my second choice) and I likely had one slightly off day with the Problem Solving round. However, I think these two shouldn't be factors at all in judging a senior candidate. In all, the Problem Solving round consisted of one question that progressed from easy to medium to hard. I answered both the easy and medium parts correctly. I didn't get the hard part done, but there was a lack of communication, responsiveness, and time to be able to do it well.

Tell me about one bug that you faced that was very hard to solve.