Taro Logo

Software Engineer Interview Experience - Munich, Bavaria

February 1, 2020
Positive ExperienceNo Offer

Process

  1. HR call with general information and a first technical question about the runtime complexity of a sorting algorithm.

  2. Technical interview via phone, where I had to solve an algorithmic problem in C++ using just a text editor without an IDE.

  3. On-site interviews comprising four technical interviews (solving problems on a whiteboard) and one "Googliness" interview. This was a lunch break chatting with a Googler, and it's important to remember that this is also part of the interview process. Each interview took one hour with only a few minutes break. I went home exhausted and with headaches, but it was still a very interesting interview, as I was really challenged technically.

Feedback was that I did well in the interviews, but there was no team match. Google has a somewhat different approach to hiring.

Questions

Technical problems were presented.

  1. Asked to give some solution, usually brute force. Pay attention to corner cases.
  2. After an initial solution, asked to find a solution that has better runtime complexity, memory complexity, or both.
  3. Sometimes boundary conditions are changed, and you are asked to find yet another solution.

Was this helpful?

Interview Statistics

The following metrics were computed from 30 interview experiences for the Google Software Engineer role in Munich, Bavaria.

Success Rate

20%
Pass Rate

Google's interview process for their Software Engineer roles in Munich, Bavaria is very selective, failing most engineers who go through it.

Experience Rating

Positive73%
Neutral27%
Negative0%

Candidates reported having very good feelings for Google's Software Engineer interview process in Munich, Bavaria.

Google Work Experiences