Taro Logo

Android Software Engineer Interview Experience - Mountain View, California

December 1, 2016
Neutral ExperienceNo Offer

Process

Google was my dream company, and I knew that applying online wouldn't get me a call. Three weeks later, my application was picked up by a recruiter who called me to set up a time for the following week. I had to ask him twice if he was actually calling from Google.

The discussion was a standard profile review and some objective-type Android developer questions. Once I passed that and expressed that this is my dream company, he told me the process and what would happen next. An hour after this call, he called me again and said that he had found me a team and they were looking for someone with my experience immediately. So, we were going to skip the phone interviews and move directly to on-site, and he passed me on to the next recruiter.

The next recruiter took a few days to respond, but we discussed the dates and the team's requirements for whom I was interviewing. When going on-site, I was told that the role was a core Android developer and I should concentrate on the front-end prep materials.

At the on-site, I met the recruiter face-to-face, and we went into a conference room. He went over the interview packet to tell me what to expect in the next six hours. As I was told before, there would be four Android/Java interviews, one Android system design, and one algorithm/data structures interview. Oddly, there was not going to be a system design interview.

Anyhow, the first interviewer came in, and we started talking Android. Time flew by. We had ten minutes left at the end to discuss my questions. The next interviewer started with Android and then moved to the algorithm problem. I was caught off guard, and after discussing the question and getting up to speed, I failed to complete the code by the end of the interview.

Next, for lunch, I was taken to a different building because I was told that all the remaining interviews would not happen in that room again, which was very odd as this never happens, and the guy who took me to lunch said so himself.

After lunch, I sat in the room, and the next interviewer came in. We directly started off with algorithms, and it felt like a design interview because we began discussing the Friend of a Friend algorithm design. I told him that I had read the question before, and we moved on to a different question. I thought I would get honesty points (this may have been a mistake as I could have written the whole code and would have had time for a discussion).

The next interviewer started off with Java and moved to one Android question, then asked me to design and code a memory heap. We discussed a lot, including receiving hints, and had a solution mapped out but ran out of time to code the create method's free swap. The last interview was also an algorithm, a number-to-character mapping, and the interviewer was not very keen on discussing the approach.

Overall, at the end, I didn't know if she was the last interviewer or if there were a few more. One thing that I noted was that the interviewers were versed on the order of interviewing, as they got confused when I told a couple of them that they were the third and fifth interviewers.

I emailed the recruiter that I had four algorithm and two Android interviews and that I had not prepared for them at all. A week later, he called me and told me that I had not done well on two of the six interviews and was not moving to the hiring committee for review, but I was encouraged to apply in a year.

Was this helpful?

Interview Statistics

The following metrics were computed from 2 interview experiences for the Google Android Software Engineer role in Mountain View, California.

Success Rate

0%
Pass Rate

Google's interview process for their Android Software Engineer roles in Mountain View, California is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive50%
Neutral50%
Negative0%

Candidates reported having very good feelings for Google's Android Software Engineer interview process in Mountain View, California.

Google Work Experiences