I was first contacted by the recruiter for a phone interview, which lasted about 30 minutes. A document was shared over Google Docs where I had to answer a programming question and type my answer into the doc so the interviewer could see my code.
Once I passed that stage, the next round of interviews was on campus. This involved interviews with 4 different QA engineers, with a lunch break in between.
The questions were not particularly hard, but apparently, I didn't do well enough to get the job. Three out of the four QA engineers asked mostly programming questions, while the other asked mostly about QA-specific topics. There weren't a lot of data structure questions, no linked lists or anything like that. I did have to show how to do merge sort.
The interviewers were all very nice and knowledgeable.
How would you test Google Search?
How do you determine the relevancy of a search term within a document?
The following metrics were computed from 4 interview experiences for the Google Software Test Engineer role in Mountain View, California.
Google's interview process for their Software Test Engineer roles in Mountain View, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Google's Software Test Engineer interview process in Mountain View, California.