Google Interview Guide

🎯 Google’s Interview Process

Typical Google SWE Interview (L3/L4):
├── Phone Screen (1): 45 min coding
├── On-site (4-5 rounds):
│   ├── Coding Round 1: Data structures & algorithms
│   ├── Coding Round 2: Data structures & algorithms
│   ├── System Design (L4+ only): Distributed systems
│   ├── Googleyness & Leadership: Behavioral
│   └── "Googleyness" (sometimes separate)
└── Hiring Committee Review

📊 What Google Evaluates

Google's Four Evaluation Criteria:
├── General Cognitive Ability (problem-solving)
│   ├── How you approach problems
│   ├── How you break down complexity
│   └── How you handle ambiguity
│
├── Leadership (emergent leadership)
│   ├── Taking initiative
│   ├── Driving results
│   └── Mentoring others
│
├── Role-Related Knowledge (technical skills)
│   ├── Coding proficiency
│   ├── System design ability
│   └── CS fundamentals
│
└── Googleyness (culture fit)
    ├── Comfort with ambiguity
    ├── Bias to action
    ├── Valuing diverse perspectives
    └── Doing the right thing

💻 Coding at Google

What Makes Google Different

• Algorithmic depth: Problems often require advanced algorithms
• Code quality matters: Clean, readable, well-structured code
• Multiple solutions expected: Discuss trade-offs between approaches
• Follow-ups are common: “What if the input is streaming?” “What if memory is limited?”

Common Topics at Google

1. Trees & Graphs — Very common, know all traversals
2. Dynamic Programming — Frequent, especially optimization problems
3. Strings & Arrays — Medium to Hard difficulty
4. System Design — L4+ required, L5+ weighted heavily

Example Google Question

Given a binary tree, find the maximum path sum between any two nodes.

Follow-ups:
- What if the tree is a BST?
- What if we need to return the actual path?
- What if the tree is too large to fit in memory?

🏗️ System Design at Google

What Google Looks For

• Scalability: Design for Google-scale (billions of users)
• Trade-off analysis: Every decision has pros and cons
• Depth: Go deep into 2-3 components
• Novel thinking: Don’t just repeat textbook answers

Common Google System Design Questions

1. Design Google Search
2. Design Google Maps
3. Design YouTube
4. Design Google Drive
5. Design Gmail

🤝 Googleyness & Leadership

What Interviewers Look For

Googleyness Signals:
✅ Comfortable with ambiguity
✅ Makes decisions with incomplete data
✅ Values collaboration over individual heroics
✅ Willing to change opinion when presented with new evidence
✅ Cares about doing the right thing (not just what's fastest)

Red Flags:
❌ "I did everything myself"
❌ Rigid thinking, unwilling to adapt
❌ Blaming others for failures
❌ Only motivated by money or prestige

Sample Questions

1. “Tell me about a time you had to work with incomplete information”
2. “Describe a situation where you changed your mind based on new evidence”
3. “Tell me about a time you helped a teammate succeed”
4. “How do you handle ambiguity in projects?”

💡 Tips for Google

1. Practice Hard problems — Google’s Medium ≈ other companies’ Hard
2. Think out loud — Silence is your enemy
3. Ask clarifying questions — Shows thoughtfulness
4. Discuss trade-offs — Google loves nuanced thinking
5. Be humble — Acknowledge what you don’t know
6. Prepare for follow-ups — Every answer leads to “what if…”

🔗 Cross-References

• Coding Patterns — Patterns commonly tested at Google
• System Design — Google-scale design problems
• Behavioral Questions — Googleyness preparation