I was first contacted by a recruiter who asked if I was interested in working at Google. After some informational talk and a phone call to clarify my preferred location, I was invited to a hangout interview.
After that, an onsite interview was scheduled. There, I had five interviews in one day.
During the hangout interview, I was asked to code some simple code in a Google Docs file. The interviewer asked some questions, and it took about 45 minutes. This interview was to make sure the candidate had a chance at the onsite interview. If you regularly solve HackerRank or Topcoder questions, or if you are an experienced developer, this should be easy.
The onsite interviews are more difficult. One interview was about design questions and was more of a discussion about possible solutions for big problems, like how would you design service XY. The interview can go in different directions from there, depending on your interviewer.
The other interviews were all about algorithms. None of them was particularly difficult, but you only have about 45-50 minutes, including a lot of questions asked. Also, everything was done on a whiteboard, which takes some time.
There was only one typical HackerRank question, and the others involved writing very small games, for example.
The following metrics were computed from 30 interview experiences for the Google Software Engineer role in Munich, Bavaria.
Google's interview process for their Software Engineer roles in Munich, Bavaria is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for Google's Software Engineer interview process in Munich, Bavaria.