Uber Android Engineer interview questions

Nice conversation with HR managers and engineers, all of then were attentive and friendly. Professional HR managers, great hiring process with clear steps, rich and quick feedback by email. It was nice experience.

1. Recruiter introduction chat. (30 min) Recruiter was very helpful and friendly. 2. Virtual Phone screening Interview (1h) Leetcode Easy/Medium coding & algorithm problem. Interviewer was very helpful throughout the process. 3. OnSite Interview: * Walk-in with recruiter (15 mins) - Just a simple walkthrough of what the day holds. - Open to any questions from you. * Coding (in depth Android) (1 hour) - You are given a sample project .zip file. Open it in android studio and add a feature to it. - Given a restCall with cities/countries, populate a recyclerviewer to match a given design. - In this round where I thought I would perform perfectly, I performed the poorest. Reasoning: The sample project was terribly coded (no architecture what-so-ever) Rest calls were all mocked, but somehow you had to use the most 'efficient' function from a bloated class with methods. Forget about writing clean code in this given project. tip: Don't spend time on quality, just get the task done. This round was very poorly planned. They should have either shared the sample project a day or two prior to the interview, or just create a new decent sample project. (Some of the practices used have not been used in more than 5 years) * HM chant (1 hour) - Behavioral questions. - Past experience. - Examples of past projects. - Most difficult task. - How have you dealt with a difficult coworker. - Any improvements you've done to the DevOps process in your team? * break (1 hour) * Design and Architecture (1 hour) - 30 mins, talk about designing a project that you're familiar with (preferrably one that you have contributed to) - 30 mins, interviewer gives you a new problem to design and architect. - tip: this was an ok round. Just watch youtube videos regarding "Design and architecture Interview" * Coding round (algorithms & data structures) - Similar to Virtual phone screen round - Leetcode Easy/Medium coding & algorithm problem - I wounder why they duplicate these rounds. A full 6 hour long interview session is too long. They could have just ommited this round, since it was already assessed in the phone-screen interview.