Google Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 112 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Google.
Google
Engineer
Mid Average Positive experience No offer 1 round Same day
Interview process
Technical screen
Interview formats
Behavioral Technical
He was a great interviewer—structured, clear, and very knowledgeable. He asked solid engineering questions, dug into deeper layers when it made sense, and always focused on fundamentals. His style mixed strong technical depth with practical understanding, which made the interview both engaging and insightful.
Confirmed questions0 questions
No confirmed questions were included in this interview report.
Google
Engineer
Staff Average Neutral experience Decline offer 3 rounds About 2 months
Interview process
Onsite Panel
Interview formats
Behavioral Technical System Design
Multiple interviews with high level people (VPs, directors, principal and distinguished engineers). Some ask situational questions about how to solve a particular problem, some ask about your past experience, so you can get the job only if you already have it.
Confirmed questions1 question
- Tell me about a time when you had to drive a major technology shift across an engineering organization.
Google
Developer
Entry Difficult Positive experience Accept offer 5 rounds About 2 months
Interview process
Phone screen Technical screen Onsite Background check Offer
Interview formats
Behavioral Technical Coding Other
Overall nice experience, smooth hiring process and cooperative staff. Interviews were arranged based on candidate's time availability. The interview process usually includes application submission, screening, initial and final interviews, assessments, reference checks, and offer negotiations, ending in onboarding for the selected candidate.
Confirmed questions3 questions
- Describe how Java’s garbage collection functions.
- What is the difference between REST and SOAP APIs?
- Explain the idea of Big O notation with some examples.
Google Engineer Interview Questions
Quoted word for word from Google interview reports.
“Write a function that receives a string for a mathematical expression with nested operations like add, sub, and mul, and outputs the evaluated integer result.”
Read reports →“What is the difference between REST and SOAP APIs?”
Read reports →“How do you determine the time and space complexity of a recursive function?”
Read reports →“What kind of parameters can be used to detect a fraudulent posting and fake reviews on Google Maps?”
Read reports →“How would you drop an egg from a building so that it doesn’t break?”
Read report →“Explain the idea of Big O notation with some examples.”
Read report →“How would you go about planning a Google launch party.”
Read report →“Design a distributed system that can manage a huge volume of data, making sure it is fault tolerant, scalable, and supports efficient data retrieval. Think about the overall system architecture, how data is stored, how replication works, and how different components communicate with each other.”
Read report →“What has been a recent event that surprised you and why?”
Read report →Formats, difficulty and experience
Across all 112 Google interview reports.