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.
I went in expecting the coding to be the whole story, and it mostly was, though the process had more steps than I expected. It started with the Google Hiring Assessment, which I had to finish before anything else happened. Then I had a conversation with a recruiter, and after that I moved on to the coding stage. The first technical round was online and looked like a LeetCode-style problem, but it was tweaked enough that a memorized solution wouldn't get you through. I had to work through the changed version as it was presented.
The next stage was an in-person technical portion with three rounds of coding. Some of the questions were about my own experience: my past teams and the work I'd done. Those were straightforward, but I'd recommend having a few concrete examples ready so you aren't building them on the spot. There was also a Googlyness behavioral round, which the process kept separate from the technical rounds. Everything then went to a hiring committee, which made the final decision. I didn't receive an offer.
Prep tip from this candidate
Finish the Google Hiring Assessment early, since it comes before everything else. Practice LeetCode-style problems with variations rather than memorized solutions, and prepare specific stories about your past teams and work.
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 | |
| Delivery Estimate Model | |
| Find Bigrams | |
| 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 | |
| N-gram Dictionary | |
| Google Maps Improvement | |
| 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.
