No phone interview - direct onsite.
5 technical rounds concentrating on problem-solving and coding.
Four out of five went really well.
The one interviewer from the start said he was going to be on the harder side and asked a question that was so ambiguous that I could not understand:
"How does a system return different output for the same input? Reasons for it."
It turned out to be more OS-related, combining probability, page swapping, and threads.
He was very rude from the beginning and was constantly evaluating me, smirking.
(One instance, when I asked him if I was proceeding in the right direction, he just gave a silly laugh and said, 'I must know it and must not ask him.' I did not find it very professional from an interviewer's point of view.)
But he also asked a coding question, and I did solve it, but before I could improvise and look at all the edge cases, the time was up.
(I must also say all other interviewers were friendly, and the problem-solving went on more like a discussion.)
After the interview, I waited for a month and also had a team match call with one of the teams that I interviewed with. So, indeed, I was very hopeful since it does not happen often.
But the recruiter called me after a month to say the hiring committee did not move forward.
The feedback given was nothing solid.
NDA.
But was asked about:
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.