The interview process began with an application via the Google Careers website, followed by a phone call a few days later from a recruiter at the location of the posted job.
The phone call included a more detailed description of the job and some computer science questions in a quiz-like format.
This was then followed up by a phone interview a week later with a Google employee in London. This interview consisted of a 45-minute programming challenge conducted via Google Hangouts and a shared Word document.
This phone interview was then followed by another phone call from recruitment, detailing the pros and cons of the phone interview. As there was no possibility for an in-person interview in the city I was applying for, a choice of other cities in Europe for the interview was presented. I got to choose one, and Google covered the cost.
The in-person interview lasted from 10 am to 3:30 pm and involved:
(Total: 3 technical, 1 system design, 1 Googleyness)
Find the shortest complete alphabet in a string, given an alphabet and a string. O(n).
Design a distributed high-score system for a game.
Replace instances of words in a string by passing in configuration.
Design and optimize a system that can display log messages that are being repeated once every N seconds/iterations.
How to compute the key of a doubly encrypted algorithm given a plaintext string and an encrypted cipher, where the key is an integer.
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.