Taro Logo

Android Engineer Interview Experience - San Francisco, California

April 1, 2022
Neutral ExperienceGot Offer

Process

  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. On-site 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 REST call with cities/countries, populate a RecyclerView 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 whatsoever). 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 created a new, decent sample project. (Some of the practices used have not been used in more than 5 years)
  • HM chat (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 made 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 (preferably one that you have contributed to).
  • 30 mins, interviewer gives you a new problem to design and architect. Tip: This was an okay round. Just watch YouTube videos regarding "Design and Architecture Interview."
  • Coding round (algorithms & data structures)
  • Similar to the virtual phone screen round.
  • LeetCode Easy/Medium coding & algorithm problem.
  • I wonder why they duplicated these rounds. A full 6-hour long interview session is too long. They could have just omitted this round, since it was already assessed in the phone-screen interview.

Questions

A difficult challenge and how you've handled it

Was this helpful?

Interview Statistics

The following metrics were computed from 2 interview experiences for the Uber Android Engineer role in San Francisco, California.

Success Rate

0%
Pass Rate

Uber's interview process for their Android Engineer roles in San Francisco, California is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive50%
Neutral50%
Negative0%

Candidates reported having very good feelings for Uber's Android Engineer interview process in San Francisco, California.

Uber Work Experiences