Interview experience
Google Interview Questions
Overview
Section titled “Overview”Google’s loop runs a recruiter screen, a phone screen, and a 4-5 round onsite (coding, system design at L5+, and a Googleyness/Leadership round) - then a Hiring Committee outside your team, not your interviewers, makes the actual decision.
Google interview process at a glance
Section titled “Google interview process at a glance”| Stage | Duration | What it tests |
|---|---|---|
| Recruiter screen | 20-30 min | Background, logistics, timeline, initial fit |
| Online Assessment (new grad/L3) | ~90 min | ~2 coding problems; L4+ often skips this stage |
| Phone screen | 45-60 min | 1 live coding problem in a shared Google Doc |
| Onsite - Coding (2-3 rounds) | 45-60 min each | DSA, often phrased non-standardly to test clarifying questions |
| Onsite - System design (L5+) | 45-60 min | Distributed systems fundamentals |
| Onsite - Googleyness/Leadership | 45-60 min | Ambiguity, learning agility, influence without authority |
| Hiring Committee | 1-2 weeks | Independent packet review; committee decides, not interviewers |
| Team matching | Varies | Hiring managers with open headcount review your packet |
Recruiter screen and Online Assessment
Section titled “Recruiter screen and Online Assessment”A short call covering background, location/visa logistics, and timeline - no coding. New grad and L3 candidates then typically get an Online Assessment (roughly 2 coding problems); L4+ candidates often skip straight to the phone screen.
Common questions
- Array/string manipulation problems at LeetCode-medium difficulty
- A second problem testing a different pattern (graphs, DP, or intervals)
Phone screen
Section titled “Phone screen”A single 45-60 minute live coding round with a Google engineer, done in a shared Google Doc - no IDE, no autocomplete, no ability to compile or run your code. Google is explicitly evaluating whether you can write syntactically clean code while narrating your reasoning, not just whether the final answer is correct.
Common questions
- Interval problems with a deliberately unusual phrasing that requires clarifying questions first
- Topological sort or graph traversal variants not found verbatim on LeetCode
- Sliding window / two-pointer array problems
Full round-by-round breakdowns are on the Google interview experience page.
Onsite: coding rounds
Section titled “Onsite: coding rounds”2-3 back-to-back 45-60 minute rounds, similar format to the phone screen. Google reuses fewer “standard” LeetCode problems than some peers - expect a familiar pattern wrapped in an unfamiliar problem statement.
Common questions
- Implement a rate limiter (fixed window, sliding window, token bucket)
- Find the median of two sorted arrays
- Design a data structure for range-sum queries (segment tree)
- Longest palindromic substring
Onsite: system design (L5+)
Section titled “Onsite: system design (L5+)”Mainly weighted at L5 and above, though some L3/L4 loops include a lighter design discussion. Google is checking whether you can reason about scale, trade-offs, and failure modes, not just recite a memorized architecture.
Common questions
- Design a URL shortener
- Design a distributed cache or rate limiter
- Design a distributed logging/metrics pipeline
Onsite: Googleyness and Leadership
Section titled “Onsite: Googleyness and Leadership”A behavioural round distinct from a generic “culture fit” chat. Google explicitly evaluates four signals across the loop - General Cognitive Ability, Role-Related Knowledge, Leadership, and Googleyness - and this round leans hardest on the last two: comfort with ambiguity, intellectual humility, and leading through influence rather than authority.
Common questions
- Tell me about a time you had to work through ambiguity with little direction
- Describe a situation where you influenced a decision without formal authority over the people involved
- Tell me about a time you disagreed with a teammate’s approach
- Tell me about a time you learned a new technology or domain quickly
Sample STAR frameworks for these are on the Google HR interview questions page.
The Hiring Committee
Section titled “The Hiring Committee”This is Google’s most distinctive step: your interviewers don’t decide whether you’re hired. Each writes independent feedback and a vote (Strong Hire, Hire, Leaning Hire, Leaning No-Hire, No-Hire, Strong No-Hire) without seeing anyone else’s score, specifically to avoid anchoring bias. A separate committee of senior Googlers from outside your target team then reviews the full packet and makes the actual call - which is why one weak round can be outweighed by strong, consistent signal across the rest of the loop, but one round that flatly contradicts the others is a real risk.
Frequently asked questions about Google interviews
Section titled “Frequently asked questions about Google interviews”What is the Google interview process?
Google’s loop usually runs: 1. Recruiter screen (20-30 min) - background, logistics, timeline. 2. Online Assessment (new grad/L3 only - roughly 2 coding problems; L4+ often skips this). 3. Phone screen (45-60 min) - one live coding problem in a shared Google Doc, no IDE or autocomplete. 4. Onsite loop (4-5 rounds, 45-60 min each) - 2-3 coding rounds, one system design round (mainly L5+), and one Googleyness/Leadership behavioural round. 5. Hiring Committee review (1-2 weeks) - a panel outside your team reviews written feedback and votes, not your interviewers. 6. Team matching. Total timeline: 6-8 weeks.
What questions are asked in Google interviews?
Coding rounds cover arrays/strings, trees and graphs, dynamic programming, and interval problems - often phrased in a non-standard way that requires clarifying questions rather than pattern-matching to a memorized LeetCode problem. System design (L5+) covers distributed systems basics: URL shorteners, rate limiters, distributed caches, logging pipelines. The Googleyness round asks about ambiguity, learning agility, and collaborative leadership without formal authority.
What is the Google Hiring Committee?
A panel of senior Googlers (typically L6+) from outside your interviewing team who make the actual hire/no-hire decision - not your interviewers. Each interviewer writes independent feedback and a vote (Strong Hire to Strong No-Hire) without seeing others’ scores, to avoid anchoring. The committee reviews the full packet, which is why consistency across rounds matters more here than performing well in just one interview.
How many rounds are there in the Google interview?
Typically 6-7 touchpoints: recruiter screen, an online assessment (new grad/L3), a phone screen, a 4-5 round onsite loop, Hiring Committee review, and team matching. Experienced (L4+) candidates often skip the online assessment and go straight to the phone screen.
How should I prepare for Google interviews?
Practice explaining your approach out loud before writing code - Google’s Google-Docs format has no autocomplete or compiler, so clarity matters as much as correctness. Prepare system design fundamentals if you’re L5+, and prepare STAR stories specifically about ambiguity, learning agility, and driving a decision without formal authority for the Googleyness round.