Uber Android Software Engineer interview questions

The technical questions themselves were not too hard ( if you actually prepared ) . 1 ) Had a recruiter phone screen 2 ) Had a technical phone screen : The guy told me he liked me and the recruiter got back to me within an hour , with an onsite interview 3 ) Onsite : I got good vibes , recruiter got back to me before i even got back home asking me to proceed to next round . Very fast 4 ) Had a code challenge 5 ) Had a request to walk through the code challenge with an engineer : I walked through it and got the feeling he liked it. Considering how fast they usually responded i expected a fast response here too , no such luck. They got back to me a week later with a simple 1 line recruiter email saying they were "going with someone else" . I tried to reach them but got no further response. Very rude.

I applied at Uber through its online portal. I got a call for a video interview in a week. Shared Screen Interview: The interviewer asked my about the cool stuff that I had done in Android and talked around it. He later went on to a simple programming question which I had to code on a shared screen. Though the question was pretty easy but I think the intent was to see my coding style. At the end of the first interview, he told me about the entire interview process and informed I will be receiving a home assignment if I get through the first one. After two days I received the assignment which had to done in 3 days. The assignment was to build an app using the api's they have provided. I got it done on time and was called for an onsite interview soon after it. The onsite interview consisted of 5 rounds. Product Design, OOD, Assignment Code Review, Algorithms and Data Structure, Android. Product Design: The first interview was about making me comfortable and to get a sense of my product design capabilities. They asked about my experience with designing a product, I had done some stuff but that wasn't much. So they asked me a real life problem, the key to which was keep asking them your specific questions and come up with the solution you think would do the needful. I found the interview very fun and refreshing. Went great. OOD: They asked me how would I design an app like Uber or something similar. Here I had to talk about the big building blocks of the systems and the meaningful classes. But I was stuck in the smaller picture and how would I code the same. Went pretty bad I guess. Code Review: The interviewer looked around my code and kept asking me why I made those decisions. He also advised what could have been the better practice. He was mainly focussing on my coding principles and how correctly have I solved the problem. Unfortunately I made a hack which I realised in the interview :). Went fine but the hack! DSA: Contrary to the common belief, this interview was pretty straight forward. There were no questions on DP, Graphs or complicated trees. The questions I was asked were on threads, linked lists and a easy problem with a hash map solution. The interviewer did not care much about the toughness of the problem but rather my approach. Went fine. Android: I was asked about every major Android components. I mostly knew all that I have used, but still feel it is good to know all of it. Went cool. I was informed about the decision in a matter of hours on the same day. The lead recruiter gave me the feedback on a phone call, which helped me in knowing what went wrong and what went right. Uber had a nice office in the beautiful city of Amsterdam. The guys were very friendly and the overall environment was like a middle aged start-up. It never felt like an interview, but more of a discussion with colleagues. I had to arrange everything on my own for travel but I got the reimbursement on time.