This was a long process with a lot of back and forth.
I interviewed for an Engineering Manager, Tools and Infrastructure role.
The process started with a recruiter introduction and a call with managers. This was followed by an onsite interview consisting of five sessions.
The onsite sessions included:
Overall, the people were really nice, and the interview was not super hard.
I would say this is a good place if you are looking for a stable big company.
After the onsite, you enter the headcount (HC) approval process, and after that, the offer committee determines your compensation level. This is a very tiring and long process, especially if you have other offers pending.
During the offer stage, you get to meet different groups to select where you want to work. The people I met sounded arrogant and made me think twice about whether I wanted to work there.
Google is a very bottom-up organization, and engineers have a lot of power. Managers are there primarily to support them, so it's not for everyone.
I turned down their offer as I had an offer from a company I liked more.
Typical management/behavior questions:
Design and coding are also standard.
The following metrics were computed from 15 interview experiences for the Google Engineering Manager role in Mountain View, California.
Google's interview process for their Engineering Manager roles in Mountain View, California is very selective, failing most engineers who go through it.
Candidates reported having good feelings for Google's Engineering Manager interview process in Mountain View, California.