Tell me about a time you had to influence a team without formal authority.

Google explicitly evaluates 'leadership' for IC roles — focus on how you built consensus, not on hierarchy.

Describe a situation where the requirements were unclear or kept changing.

Show comfort with ambiguity: how you made progress anyway and adjusted as things clarified.

Tell me about a time you were wrong about something technical.

Intellectual humility is explicitly screened for — own the mistake and describe what changed your mind.

Describe your approach to a coding problem you'd never seen before.

Narrate your thinking out loud: clarify constraints, discuss brute force first, then optimize — the process matters as much as the final answer.

Google Interview Questions & Process Guide

Overview

Google's process is built around 'Googleyness' (collaboration, comfort with ambiguity, intellectual humility) plus a strong emphasis on algorithmic problem-solving and clean, correct code written live — often on a shared doc rather than a whiteboard. Interviewers submit independent written feedback that goes to a hiring committee, not just the interviewers themselves, so a single strong or weak round rarely decides the outcome alone.

Interview Process

Recruiter screen
Background, team matching, logistics.
Phone screen(s)
1–2 rounds of live coding on a shared document, typically data structures and algorithms.
Onsite (4–5 rounds)
Coding, at least one system design round (for experienced hires), and a 'Googleyness & Leadership' behavioral round.
Hiring committee review
A committee independent of your interviewers reviews all written feedback before an offer decision.

What Google Looks For

General cognitive ability — how you reason through unfamiliar problems, not just whether you know the answer
Role-related knowledge — depth in your specific domain (e.g., distributed systems, ML, mobile)
Googleyness — comfort with ambiguity, intellectual humility, collaboration over ego
Leadership — influence without authority, even for individual-contributor roles

Practice Behavioral Questions

Tell me about a time you had to influence a team without formal authority.
Google explicitly evaluates 'leadership' for IC roles — focus on how you built consensus, not on hierarchy.
Describe a situation where the requirements were unclear or kept changing.
Show comfort with ambiguity: how you made progress anyway and adjusted as things clarified.
Tell me about a time you were wrong about something technical.
Intellectual humility is explicitly screened for — own the mistake and describe what changed your mind.
Describe your approach to a coding problem you'd never seen before.
Narrate your thinking out loud: clarify constraints, discuss brute force first, then optimize — the process matters as much as the final answer.

Tips

Practice coding on a plain shared document, not an IDE — no autocomplete, no syntax highlighting.
Narrate your thought process continuously; silent problem-solving reads poorly to Google interviewers.
For experienced/senior roles, expect the system design round to weigh as heavily as coding.