Google interview prep
the complete guide
Google's interview process is different from every other company. The hiring committee model, the Googleyness criterion, the level-setting compensation committee — none of it works the way candidates expect. Here's the full picture.
Google's hiring process — stage by stage
Most prep guides skip the process and jump straight to Leetcode. Understanding what happens at each stage and why changes how you prep for it.
Recruiter screen
15–20 minutes
A Google recruiter reaches out — typically via LinkedIn or your application. This call covers your background, what you're looking for, comp expectations, and timeline. It's mostly a fit check, not a technical screen.
How to pass this stage
Be concrete about what you want (role, team type, impact). Have a clear current comp figure ready. Express genuine interest in Google specifically — recruiters talk to hundreds of people and can tell when someone is treating this as a backup. Ask about team fit and what the role's first 90 days look like.
Technical phone screen(s)
45–60 minutes each, 1–2 rounds
A software engineer (not a recruiter) asks you to solve 1–2 coding problems in a shared editor like Google Docs or Coderpad. Problems are typically Medium Leetcode difficulty, sometimes Hard. Focus: data structures, algorithms, code quality.
How to pass this stage
Think out loud before you type. State your approach, time/space complexity, and edge cases before writing a single line. Google engineers score how you reason, not just whether your code compiles. A working solution with good communication beats a perfect solution in silence.
Virtual onsite
4–5 rounds, 45 minutes each
The full interview loop. Typically: 2 coding rounds, 1 system design round (for L4+), 1 behavioral round, and sometimes a role-specific round (e.g., ML for ML roles). All conducted over video with a shared coding environment.
How to pass this stage
Treat each round as independent. A weak round doesn't automatically eliminate you — the hiring committee weighs the full packet. Don't rush: take a moment to think at the start of each problem instead of typing immediately. If you're stuck, say so and walk through your reasoning — interviewers can give hints if you've shown structured thinking.
Hiring committee review
1–2 weeks after onsite
No single interviewer decides your fate. A group of senior engineers who didn't interview you reads your packet — feedback, scores, and resume — and votes. This is unique to Google. Your fate is in the hands of people who've never met you.
How to pass this stage
You can't influence the committee directly — but your interviewers write the feedback. Make their job easy by being memorable, specific, and articulate. Interviewers summarize you in writing; the clearer your thinking, the better the summary.
Compensation committee
1 week after HC approval
Google sets your level (L3, L4, L5, etc.) and comp package through a separate committee. You may be approved at a different level than what you interviewed for if you performed significantly above or below expectations.
How to pass this stage
Have a competing offer or counter-offer ready. Google has salary bands per level and will negotiate within the band. Equity (GSUs) is often where the most negotiation room exists. The first offer is almost never the best offer.
The 4 criteria Google actually scores you on
Every Google interviewer fills out a structured scorecard after your session. These are the 4 dimensions — understanding them changes what you optimize for.
General cognitive ability
Google cares about how you think more than what you know. This isn't IQ — it's your ability to structure a novel problem, identify assumptions, and think through implications. It shows up in how you approach coding problems and how you reason through ambiguous behavioral questions.
What it looks like in the room
When stuck on a coding problem, don't stare at the screen. Say: 'I know brute force is O(n²) — I'm trying to think about whether a hash map could reduce the lookup cost to O(1).' That kind of visible reasoning is what scores well.
Leadership
Leadership at Google is not about managing people. Even for individual contributors, they want to see evidence that you took initiative, influenced others without authority, and drove outcomes beyond your job description. Every level is expected to lead something.
What it looks like in the room
Interviewers specifically look for: 'I noticed this problem wasn't getting solved, so I did X' rather than 'my manager asked me to do X.' If you can only point to things you were assigned, you'll score low on leadership regardless of seniority.
Googleyness
The most misunderstood criterion. Googleyness is not about liking Google's products or having the right personality. It's about: comfort with ambiguity, intellectual humility (you can be wrong), bias toward action, and being enjoyable to work with under pressure. Google explicitly does NOT want people who are arrogant or who shut down when they don't know something.
What it looks like in the room
When an interviewer says 'your approach won't scale — how would you change it?', the Googley response is curiosity: 'Good point — what's the constraint I'm missing?' The non-Googley response is defensiveness: 'It would scale because...'
Role-related knowledge
For software roles: your ability to actually write good code, design systems, and understand the domain of the role. This is the easiest criteria to prep for — it's the technical competency check. However, it's NOT the most heavily weighted. You can have excellent technical skills and still fail on the other three.
What it looks like in the room
Write clean, readable code with meaningful variable names. Comment on non-obvious choices. Handle edge cases explicitly. Don't just solve the problem — demonstrate that you write the kind of code you'd want to read in a code review.
Coding topics by priority for Google
Not all Leetcode topics are equally common at Google. These appear with the highest frequency across engineering interviews at every level.
Arrays and strings
Sliding window, two pointers, prefix sums — show up in almost every Google coding round.
Hash maps and sets
Used to optimize brute-force O(n²) solutions to O(n). Know when to reach for a map instinctively.
Trees and graphs
BFS, DFS, topological sort. Google loves tree traversal problems — binary trees, N-ary trees, and graph problems disguised as trees.
Dynamic programming
Not always a direct DP problem, but memoization and recognizing subproblems appears in many Hard problems.
Heaps and priority queues
K-th largest, merge K sorted lists, scheduling problems — common in onsite rounds.
System design (L4+)
Design a URL shortener, design Twitter's feed, design a distributed cache. Scale matters: think billions of users, not thousands.
Google interview FAQs
How long does the Google interview process take?
From first recruiter contact to offer, expect 6–10 weeks. The phone screens happen in weeks 1–3. The onsite is typically 2–3 weeks after. Hiring committee review takes 1–2 weeks. Offer and negotiation takes another 1–2 weeks. Timelines can compress if you have competing offers — tell your recruiter if you have deadlines and they will expedite.
What programming language should I use for Google coding interviews?
Python, Java, C++, or Go are all well-accepted at Google. Python is the most popular choice because it's concise — you can express more with less code, which leaves more time for problem-solving. Google has used Go internally for years, so it's accepted without hesitation. Avoid JavaScript if you can — it's allowed but interviewers are less familiar with its edge cases.
How competitive is the Google interview process?
Acceptance rates at Google are estimated at 0.2–0.5% of applicants. Most candidates who reach the onsite stage are technically qualified — the differentiator is usually Googleyness and cognitive ability signals. The hiring committee process means that a single weak round rarely eliminates you, but consistent mediocre scores across rounds will. Preparation specifically for Google's criteria (not just general Leetcode grinding) materially improves outcomes.
Can I negotiate the Google offer?
Yes — and you should. Google's first offer is rarely their best. The most negotiable components are base salary (within your level's band) and RSU count. If you have competing offers, present them — Google will match or beat them to close candidates they want. Signing bonuses are also common when Google is competing for a candidate. The offer doesn't expire during negotiation; recruiters expect it.
Get AI coaching for your Google interview
Zari coaches you on behavioral answers with STAR evaluation, Googleyness framing, and how to articulate your thinking the way Google interviewers score highest.
Start coaching free