The recruiter who emailed me was very nice and helpful. After the technical interview, he called me to discuss how it went. Unfortunately, I did not make it through the process. The recruiter does send you a book with things to know for your interview (Data Structures and Algorithms, etc.). The technical interview over the phone was a great experience. He asked me to write code for a Teoplitz matrix. It took me around 30 minutes to write the code, and I discussed each scenario with him. The interviewer was very helpful and gave clues on the areas where I was lacking.
When I was done, I got a chance to ask him a few questions. I asked him a technical question about airport runway flight requests landing every 15 minutes: how would you deal with it? He laughed and said he couldn't answer that question, joking that if his answer was wrong, I could tell the world. I clarified that I was just asking in general. He then asked me to rephrase the question, which I did. Finally, he answered that he would choose a HashMap.
Then I asked him one more question about his work and process. He explained all the processes and the areas he likes.
Overall, for me, it was a pretty positive experience.
Sorry, I cannot share the interview questions because they requested not to. However, I did provide some guidance on what to prepare for.
The following metrics were computed from 748 interview experiences for the Google Software Engineer role in Mountain View, California.
Google's interview process for their Software Engineer roles in Mountain View, California is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for Google's Software Engineer interview process in Mountain View, California.