I applied online and a recruiter contacted me.
I had two phone screens, both involving coding on CoderPad.
The first one went okay and involved coding a smart collection with binary search trees. The second one went very well, with two coding questions: one on reversing a number and another on sorting an array based on another array.
I received feedback that they were impressed with my second phone screen and invited me for an onsite interview at SFO.
The onsite involved five rounds:
The whole interview went well from my side, except in the coding round. I solved one question out of two and gave the approach for the second, but ran out of time to code it.
I had a good experience with the way the interview went, but unfortunately, I was not given an offer.
Binary search with duplicate values.
The following metrics were computed from 2 interview experiences for the Uber Android Engineer role in San Francisco, California.
Uber's interview process for their Android Engineer roles in San Francisco, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Uber's Android Engineer interview process in San Francisco, California.