After the recruiter's phone call with general organizational questions, I had a short technical phone interview.
The interviewer was 10 minutes late, so we only talked for 30-35 minutes. In that time, he was able to ask me not very much: some of my previous experience, the most difficult bug I'd faced recently, and one technical question with coding in a shared document.
After that, he let me ask him something about Google. He answered one question and finished the interview, so I had no chance to find out everything I'd planned.
Also, I had the feeling the interviewer was not interested in being there, as he was not leading me through the resolution process and talked very little. His communication skills could also be better; I hardly understood his questions in Indian English and had to ask him to repeat several times. Google should send better-skilled and more open English speakers to interview, in my humble opinion.
I successfully resolved the technical coding question in two different ways (time and memory efficient), commenting on my resolution thoughts, but I received a negative response from the recruiter within a week.
Write code to find out if two string words are anagrams.
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.