Google Software Engineer candidates report coding rounds with heavy follow-ups, a Googleyness behavioral round, and team matching after the loop. Prep accounts stress medium problems, graphs and BFS/DFS, and clearly explaining tradeoffs.
$213K
Avg. Base Comp
$295K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Candidates describe the Google Software Engineer interview as coding-heavy, with a separate Googleyness behavioral round. One reported coding prompt centered on searching, and the candidate was expected to reason through the approach, write working code and talk through tradeoffs. An L4 candidate who received an offer focused prep on graphs and BFS/DFS while drilling mostly medium problems. That candidate noted that you can code in Python, C++ or Java.
Follow-up questions can eat into your time. One senior candidate who completed a coding and a Googleyness round was rated L5 by both interviewers. They attributed it to running out of time under heavy follow-ups and to not stating their scope and ownership explicitly. Treat each follow-up as part of the problem and practice timed variations. In the behavioral round, say plainly what you owned and where you influenced other teams.
For preparation, the L4 candidate spent five or six weeks on a pattern-based problem list. They also wrote six to eight STAR stories for Googleyness and ran a couple of mock rounds. A candidate who received an L6 offer split about six months of prep between system design and LeetCode. They favored Google-tagged questions from the last 12 months over a generic top list.
Logistics can be bumpy. One candidate reports sessions moved at the last minute and interviewers who did not appear, so confirm each slot with your recruiter. After the loop, candidates describe a team matching stage, and one offer recipient found its timing and team fit unclear. These reports are a small sample, so treat them as directional rather than a fixed script.
Synthesized from 523 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Google process.
Graphs were the headline for me. The coding questions leaned heavily on graph problems, and the interviewers were collaborative and friendly, which kept the technical rounds from feeling as harsh as they could have. The interview felt streamlined overall.
There was also a concurrency question. It could be solved with a heap, so the useful lesson was to think about which data structure fits the shape of the problem rather than reaching for whatever you practiced most.
I didn't get an offer. My main takeaway is to treat graphs as a core topic and practice adapting standard problems to unfamiliar framings. There's been online chatter about Google moving toward code comprehension style interviews and about how many rounds the loop has, but I can't speak to any of that from my own experience.
Prep tip from this candidate
Lean heavily on graph problems and be ready to apply those patterns to a concurrency problem where a heap is the natural tool.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Google
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Empty Neighborhoods | |
| Top Three Salaries | |
| Merge Sorted Lists | |
| String Shift | |
| Top 3 Users | |
| Raining in Seattle | |
| First Touch Attribution | |
| Job Recommendation | |
| Minimum Change | |
| Find the First Non-Repeating Character in a String | |
| Daily Retention Summary | |
| Find the Index with Equal Left and Right Sum | |
| Find Bigrams | |
| Delivery Estimate Model | |
| Detecting ECG Tachycardia Runs | |
| Size of Joins | |
| Last Transaction | |
| Friendship Timeline | |
| The Brackets Problem | |
| P-value to a Layman | |
| Level Of Rain Water In 2D Terrain | |
| Google Maps Improvement | |
| N-gram Dictionary | |
| Third Purchase | |
| Four Person Elevator | |
| Nearest Common Ancestor | |
| Basic Regex | |
| Type-ahead Search | |
| Cyclic Detection |
Synthesized from candidate reports. Individual experiences may vary.
Candidates describe coding rounds in which they reason through an approach, write working code and discuss tradeoffs. One prompt centered on searching. Interviewers may ask many follow-up questions, which one candidate said cost the time needed to finish cleanly. Python, C++ and Java are among the accepted languages.
Candidates report a behavioral Googleyness round alongside the coding interviews. One senior candidate suggests stating your scope and ownership explicitly rather than assuming the interviewer will infer it. Prepared STAR stories helped one L4 candidate.
After the loop, candidates report team matching, level ratings, and offer discussions. One candidate was rated L5 by both interviewers and awaited a decision, while others report L4 and L6 offers. One candidate described team-matching timing and fit as unclear.
