Real, anonymous reports from people who interviewed for DevOps Engineer at Google, newest first and distilled into what to expect across the loop.
After an HR screen, the process included a coding screening round and then a final stage with multiple coding rounds plus either design or additional coding, depending on the sequence. Interview problems were described as medium to hard, and no offer was made.
A recruiter call was followed by a system design interview that the candidate passed, then additional rounds including two coding interviews, another system design, and a culture-focused “Googleyness” interview. The outcome was rejection.
The interview process typically starts with an HR or recruiter screening, followed by multiple rounds that may include coding, system design, and behavioral interviews, often culminating in an onsite interview.
Candidates can expect several coding interviews focusing on data structures, algorithms, and debugging, with questions generally rated as medium to hard in difficulty.
There are usually one or more system design interviews that assess candidates' ability to architect solutions, with questions often being open-ended and challenging.
Candidates will face behavioral interviews that evaluate cultural fit, often referred to as 'Googleyness', assessing alignment with the company's values and work style.
Some candidates reported challenges related to communication during interviews, which may impact their performance and outcome, highlighting the importance of clear dialogue.
Candidates generally describe the interview process as difficult, with many reporting no offers despite positive experiences, indicating a competitive selection process.