The interview started with a phone screen. The interviewer told me that I solved the question faster than 95% of people they'd interviewed. I was very happy to hear this.
The next step was an on-site interview at the Mountain View campus. The interview included:
The coding interviews were where I struggled.
The first interviewer presented a question that took me a bit of time to design, given its complexity. I managed to finish a design and understand the algorithm implementation but was not able to completely write the code on the whiteboard.
The second interview bothered me. The interviewer wasted a lot of time at the beginning of the 45-minute session talking about random things, leaving me with almost no time to complete the question they proposed, with about 15 minutes remaining. They also started the interview with a rude remark about their peers, stating that "Every engineer at Google has their opinion, and they all think their opinion matters." This was harsh to hear from an employee of the company I was interviewing for.
The final coding challenge was fairly straightforward. I completed it with enough time for the interviewer to "bump the difficulty up" twice before the interview concluded.
Not allowed to disclose information.
The following metrics were computed from 4 interview experiences for the Google Release Engineer role in Mountain View, California.
Google's interview process for their Release Engineer roles in Mountain View, California is very selective, failing most engineers who go through it.
Candidates reported having very negative feelings for Google's Release Engineer interview process in Mountain View, California.