Google Software Engineer candidates report coding-heavy loops with behavioral/Googleyness and system-design interviews. Preparation commonly centers on clear reasoning, optimization follow-ups, and level-appropriate design depth.
$179K
Avg. Base Comp
$211K
Avg. Total Comp
5-6 rounds
Typical Rounds
4 months
Process Length
Google Software Engineer reports describe a process centered on coding, with behavioral evaluation and, particularly in the supplied L5 accounts, system design. Candidates describe data-structures-and-algorithms work including dynamic programming and graph traversal. Explain the initial solution, its complexity, and how you would handle follow-ups rather than relying on recognition or memorization alone. One successful candidate encountered a hard dynamic-programming question with several extensions.
System design was substantial in the L5 reports. Candidates said the discussion could be more abstract than their daily architecture work and might not align closely with their previous product background. Prepare to clarify requirements, state assumptions, compare tradeoffs, and defend decisions at the level expected for the role. The evidence does not establish one universal design prompt or format.
Behavioral or Googliness interviews also appear in the reports. Prepare concrete examples and be ready to explain your choices and prior work clearly. Candidates should also distinguish interview performance from the eventual hiring outcome: several supplied accounts describe hiring-committee review or team matching after the interviews, and passing earlier stages did not necessarily mean an offer was complete.
For team matching, make your technical background and preferred work easy for a recruiter or hiring manager to scan. Ask how matching works for your level and specialty, while treating any timeline as candidate-specific. Match the depth of coding and design preparation to the level and role communicated by the recruiter.
Synthesized from 410 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.
The most demanding part of my Google process was the systems-design discussion: I had to design a solution for a stream of server logs containing timestamps, service names, and latency values, then return the top k services by 99th-percentile latency within a sliding one-hour window. The interviewer wanted both the data structures and an explanation of how the approach would behave as the stream scaled, so it was not enough to sketch a high-level design.
For this systems-focused SWE role, I first spoke with a recruiter and then completed a 45-minute phone technical interview. The virtual onsite consisted of three coding interviews, one system-design interview, and a Googleyness round. The coding side was strongly DSA-focused, with medium-level LeetCode-style problems; at least one round included two questions that ranged from medium to hard. I also encountered a dynamic-programming optimization question, and there were questions on core CS fundamentals and my prior experience. The interviewers were smart and easy to work with, and they left time at the end for my questions.
The process felt lengthy, but I received feedback about a week after the onsite and ultimately did not receive an offer. My main advice is to prepare beyond standard medium coding questions: practice explaining a DP optimization clearly, refresh CS fundamentals, and be ready to reason concretely about streaming data structures, sliding windows, percentile calculations, and scalability for the system-design round.
Prep tip from this candidate
For the systems-design round, practice streaming log-data problems with a sliding one-hour window, top-k results, and 99th-percentile latency; be ready to justify the data structures and scaling behavior. Also prepare a dynamic-programming optimization problem alongside medium-to-hard coding questions and CS fundamentals.
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 | |
| First Touch Attribution | |
| Raining in Seattle | |
| Job Recommendation | |
| Minimum Change | |
| Find the First Non-Repeating Character in a String | |
| Daily Retention Summary | |
| Find Bigrams | |
| Delivery Estimate Model | |
| Last Transaction | |
| Detecting ECG Tachycardia Runs | |
| Find the Index with Equal Left and Right Sum | |
| Friendship Timeline | |
| Size of Joins | |
| The Brackets Problem | |
| P-value to a Layman | |
| Level Of Rain Water In 2D Terrain | |
| Google Maps Improvement | |
| N-gram Dictionary | |
| Third Purchase | |
| Nearest Common Ancestor | |
| Four Person Elevator | |
| Basic Regex | |
| Cyclic Detection | |
| Type-ahead Search |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report recruiter conversations and, in some cases, an online assessment before interviews. One assessment was described as situational judgment, while another was reported as data-structures-and-algorithms work; treat the format as role-dependent and clarify it with the recruiter.
Several candidates report an initial technical or algorithm interview, sometimes lasting 45 minutes. Reported questions include sliding-window strings, easy LeetCode-style work, and implementation discussions; candidates emphasize confirming constraints before committing to an approach.
Candidates report multiple coding rounds covering dynamic programming, DFS, graphs, trees, grids, parsing, and hashing. A correct brute-force solution may lead to follow-ups, so articulate time and space complexity and explain how you would improve the approach.
Candidates report system-design interviews alongside coding, including a paging-system prompt and a streaming-log design with percentile and top-k requirements. Prepare to identify requirements, choose data structures, and discuss the behavior of the design as scale changes.
Candidates report behavioral or Googleyness discussions about leadership, initiative, creativity, conflict, and prior work. Some accounts continue through hiring-committee review and team matching, although the order and availability of those stages vary by candidate and level.
