Google interview guide
Data-driven, 10x thinking, psychological safety. Intellectual humility is valued.
Interview process
The hiring committee makes all offer decisions; no single interviewer can approve or block an offer alone. All interviewers submit written scorecards before the committee meets. Typical timeline from screen to offer is 6 to 12 weeks. Google's levels are notoriously conservative; most external hires come in one level below their previous role.
- 1Recruiter screen · 30 minBackground, motivation, team preferences
- 2Manager screen · 45 minLeadership style, management philosophy
- 3Googleyness · 45 minAmbiguity, inclusion, psychological safety, collaboration
- 4Leadership (manager-specific) · 45 minStrategic thinking, influence, people development
- 5Coding (SDM) · 45 minTypically 1 to 2 coding rounds; easier than the SWE bar
- 6System design · 45 minLarge-scale distributed systems at Google scale
- 7Hiring committee review · N/AAll feedback is reviewed by a committee before offer
Most asked questions
1. How do you approach decisions when data is ambiguous or conflicting?
2. Tell me about a time you drove innovation in a large organization.
3. Describe how you've created psychological safety in a team.
4. Tell me about a time you had to learn something entirely new quickly to do your job.
5. Describe a time you made a significant mistake. How did you handle it?
6. How have you built inclusive teams and diverse pipelines?
Interview tips
- Google values intellectual humility: say "I don't know" confidently, then reason through it
- Data and analysis drive Google decisions: always reference data in your examples
- Googleyness includes creating psychological safety and inclusive environments
- "Think 10x, not 10%": frame your stories around bold, transformative impact
- The hiring committee reviews all feedback before offers; no individual interviewer can make the offer
- Show curiosity: "great just isn't good enough" means ongoing learning is expected
Compensation by level
Medians read from levels.fyi on 2026-09-12. A median is the middle reported package, not a floor or a ceiling.
Google managers share the numeric engineer ladder. L6 is an engineering manager, L7 a senior manager, L8 a director. L5 manager exists and is the entry manager rung.
| Level | Base | Total | Basis |
|---|---|---|---|
| L6Engineering manager | median $271K | median $732K | US |
| L7Senior engineering manager | median $326K | median $920K | US |
| L8Director of engineering | median $374K | median $1.38M | US |
| L5Engineering manager, entry manager rung | median $234K | median $416K | US |
- L6: Stock reported at about $408K a year.
- L7: Stock reported at about $501K a year.
- L8: Stock reported at about $875K a year.
- L5: Listed for completeness. External manager hiring usually targets L6.
Equity. Equity is GSUs, Google stock units, which are RSUs under a Google name. They vest over four years, monthly or quarterly depending on grant size, and most reports describe a front-loaded schedule of roughly 33 percent, 33 percent, 22 percent, 12 percent for newer grants. Google refreshes grants every year, so the running total after a few years is usually larger than the offer letter suggests.
Negotiation. Commonly reported as negotiable: the equity grant and the level, set by a hiring committee rather than the hiring manager. Base is commonly reported as band-bound, and a competing offer is commonly reported as the thing that actually moves the number.
Source: levels.fyi. Verify before you negotiate; see the negotiation guide.
What they really evaluate
- Evidence-based decision making: opinions backed by data win
- Long-term investment in platform and infrastructure
- Collaborative culture: consensus matters at Google
- Intellectual depth: be ready to go deep on any topic you mention
- Openness to failure as a learning opportunity
Candidacy killers
- Overconfidence without data: "I just knew it was right"
- Inability to articulate how you've created inclusive or psychologically safe environments
- Treating the Googleyness round as unimportant; it is a real evaluation with real weight
- Not asking clarifying questions in the system design or coding rounds