How Google Interviews in 2026: Process, Questions & What They Score
The complete process, reported questions, and what interviewers score.
Google / Interview snapshot
7
stages from
application to offer
32
reported questions
37
public sources
Independent: SupaCV is not affiliated with or endorsed by Google. This is one well-documented shape of Google's interviews, not a script: processes change and vary by role, team, level, and region, so confirm specifics with your recruiter.
On this page
01 / For every Google candidate
The process, start to finish.
Google is best known for hiring software engineers (SWE), and its interview process is widely documented as one of the most structured and rigorous in Big Tech. It is built around a resume/recruiter screen, one or more technical phone screens, a multi-round onsite/virtual "loop," and a distinctive committee-based decision process (Hiring Committee, then separate Team Matching) rather than a single hiring manager decision.
Google also hires Product Managers (including the well-known APM program) and other functions, but the SWE loop is the best-documented and most consistently reported across sources. Total time from application to offer commonly runs 6-12+ weeks, and can stretch to several months once team matching is included; this varies significantly by role, level, location, and current hiring climate.
Two things to flag for candidates prepping in 2026 specifically: hiring is tighter and more selective than a few years ago (longer team-matching waits are widely reported), and Google has been experimenting with the format itself (reintroducing some in-person interviewing and piloting an AI-assisted "code comprehension" round) in response to AI-assisted cheating on remote coding screens. Always confirm current format details with your recruiter rather than assuming the process below is fixed.
Stage 1: Resume/application screen
Days to a few weeks
Recruiters (sometimes aided by an internal screening tool) review resumes for role fit. A referral or recruiter outreach can accelerate this step.
Stage 2: Recruiter screen
~30 minutes
A non-technical call covering background, motivation, role fit, logistics, and (later in the process) compensation expectations and timeline.
Stage 3: Technical phone screen(s)
45-60 minutes per round
One or two rounds (sometimes with different engineers) conducted over video with a shared Google Doc or CoderPad (no syntax highlighting or autocomplete). Focus is on one or two data-structure/algorithm coding problems, generally medium difficulty or above. Worth knowing: starting in the second half of 2026, Google has been piloting a 'code comprehension' round for junior/mid-level SWE candidates on select teams (initially reported in Google Cloud and the Platforms & Devices org) that swaps writing code from scratch for reading, debugging, and improving an existing codebase with an AI assistant (e.g., Gemini). It explicitly scores prompting skill and your ability to catch the assistant's mistakes, not just passive code reading. This is a limited pilot, not yet the standard format, so ask your recruiter which format you'll get.
Stage 4: Onsite / virtual onsite loop
Full day (~5-6 hours total); each round ~45-60 minutes
The core evaluation stage: typically 4-5 (occasionally up to 6) back-to-back interviews, usually comprising 2-3 coding/algorithm rounds, one system design round, and one or two Googleyness-and-Leadership (behavioral) rounds. Each interview is conducted by a different Googler who was not involved in earlier stages. On system design: sources vary on exactly where it becomes standard: some put the line at L4/mid-level, others say it's most consistently a standalone round from L5/senior up, with L4 design questions sometimes folded into a coding round instead; it's rarely a standalone round at new-grad L3. On format: fully virtual loops became the default during the pandemic and are still common, but Google leadership has been pushing to bring back some in-person interviewing since 2025 specifically to counter AI-assisted cheating on remote rounds. Don't assume your loop will be virtual by default, confirm with your recruiter.
Stage 5: Hiring Committee (HC) review
About 1-2 weeks after the onsite (feedback collection, packet write-up, committee vote)
A committee of Googlers who did NOT interview the candidate reviews the full packet (interview feedback, resume, recruiter's write-up) and votes hire / no-hire, and can also recommend an adjusted level. This is a distinctive Google practice intended to reduce individual interviewer bias.
Stage 6: Team matching
Highly variable: roughly 2-3 weeks in fast cases, up to 2-3 months in slow or constrained-market cases
After passing HC, candidates (especially for generalist SWE hiring) enter a separate pool where hiring managers with open headcount interview/select them in short 'team match' conversations. Candidates are not guaranteed a team, and packets can expire (commonly cited as roughly 6-8 weeks) if no match is found, effectively ending the candidacy despite having passed HC.
Stage 7: Offer / compensation discussion
Days to ~2 weeks
Once matched, the recruiter extends and negotiates the offer (base, bonus, equity, sign-on).
Reported interview time, one scale in minutes
Where the minutes go
- Recruiter screen~30 min
- Technical phone screen45 to 60 min
- Onsite / virtual onsite loop~45 to 60 min
Not drawn: Resume/application screen, Hiring Committee review, Team matching and Offer / compensation discussion, whose durations are not given in minutes.
02 / What Google scores
Google's Four Hiring Attributes
01
Role-Related Knowledge (RRK): domain expertise, technical skills, and experience specific to the job being hired for
02
General Cognitive Ability (GCA): how a candidate reasons through ambiguous or novel problems, structures thinking, uses data, and learns/adapts (assessed through hypothetical and behavioral 'how did you solve X' questions, sometimes including estimation/Fermi-style questions)
03
Leadership, specifically 'emergent leadership': the ability to step up and lead within a team when relevant, and to step back when appropriate, rather than fixed people-management authority
04
Googleyness (also referred to as 'Googleyness & Leadership' in the interview round), cultural/values fit, commonly described as comprising: comfort with ambiguity, bias to action, intellectual humility, conscientiousness/taking ownership, being collaborative, and putting the user first
This four-attribute framework (RRK, GCA, Leadership, Googleyness) is consistently described across many independent interview-prep sources (IGotAnOffer, Exponent, ResumeAdapter, Hello Interview, and others) as the rubric Google interviewers score candidates against, typically via a written feedback form per attribute. Its origin is traceable: Laszlo Bock, Google's former SVP of People Operations, laid it out in his 2015 book 'Work Rules!' and it was also published on Google's since-retired internal-facing 're:Work' site, which now 404s.
Google's current public 'How We Hire' careers page does not restate this exact four-attribute framework in its own text. Bottom line: treat this as a well-corroborated, credibly-sourced framework rather than a word-for-word quote from Google's current careers site. It's solid enough to build prep around, but don't expect this exact wording on an official Google document today.
03 / Coach's notes
Coach's tips.
01
Map every behavioral story to one of Google's four attributes (RRK, GCA, Leadership, Googleyness) and say so implicitly through your framing. Interviewers score against a written rubric for these specific attributes, so a well-told STAR story that doesn't clearly demonstrate one of them will score lower than a less polished one that does.
02
For coding rounds, optimize out loud: Google interviewers consistently report wanting to see you reason about time/space trade-offs and edge cases, not just produce a working brute-force solution. Always state complexity and ask about constraints before coding.
03
Prepare 2-3 flexible 'emergent leadership' stories (situations where you led without formal authority, stepped back to let someone else lead, or drove a project cross-functionally) since Google's Leadership attribute is explicitly not about people-management titles.
04
For GCA/hypothetical or estimation questions, there is no single 'right' numeric answer. Narrate your assumptions, structure the problem (e.g., top-down Fermi decomposition), and show you can adjust cleanly when the interviewer challenges an assumption.
05
Practice on a shared Google Doc or plain-text editor (no autocomplete/syntax highlighting) before the phone screen, since that is the standard tool Google uses and losing time to unfamiliar tooling is a commonly cited unforced error.
06
Confirm the format ahead of time rather than assuming: ask your recruiter whether your loop will be virtual or in-person (Google has been reintroducing some in-person rounds since 2025 to counter AI-assisted cheating) and whether you're on a team piloting the newer AI-assisted 'code comprehension' round instead of classic from-scratch coding. You'll prepare differently for each.
07
Understand that passing the onsite loop and Hiring Committee is not the finish line. Budget for a potentially lengthy Team Matching phase (reported as anywhere from ~2 weeks to 2-3 months), and proactively network with hiring managers/teams during this window since packets can expire (commonly cited around 6-8 weeks) if no team match is found.
04 / The research
Where this page comes from.
Compiled from public sources across 20 sites. Google's own page is among them: google.com/about/careers/applications/how-we-hire.
- sites
- 20
- coaching and prep guides
- 33
- candidate reports and forums
- 3
- Google's own pages
- 1
Source composition
Where the research comes from
Grouped by the kind of site that published each source: Google's own domain, candidate forums, and everything else.
- Coaching and prep guides33
- Candidate reports and forums3
- Google's own pages1
05 / The questions
Reported questions, by category.
Showing questions for
Roles are grouped by the category each question fits, not by the source.
Coding & Data Structures/Algorithms
(phone screen + onsite)
8 questions
Given an encoded string, return its decoded string (string parsing/stack problem)
Stack-based string parsing; nested multipliers make an explicit stack or recursion the expected approach.
Design and implement an LRU Cache (one of the most consistently cited Google coding questions across multiple sources)
Classic data-structure design: hash map plus doubly linked list for O(1) get and put.
Number of Islands: count connected components in a grid (frequently reported across all levels)
Grid connected-components problem; flood fill with DFS/BFS and visited-state bookkeeping.
Word Ladder: find the shortest transformation sequence between two words using a dictionary (graph/BFS problem)
Shortest-path search over word transformations; model words as graph nodes and BFS level by level.
Merge Intervals: merge overlapping intervals in a list
Sort-then-sweep technique: order intervals by start and merge overlaps in one pass.
Implement a SnapshotArray supporting versioned get/set operations
Versioned data-structure design: per-index history with binary search over snapshot ids.
Two Sum / variants and Longest Substring Without Repeating Characters (common warm-up/phone-screen level questions)
Warm-up staples: hash map complement lookup and sliding window over characters.
Various tree/graph traversal, dynamic programming, and trie problems, especially at senior levels (L5+) where interviewers reportedly favor tries, graphs, and DP over simpler array problems
Senior-level pattern round: tries, graphs, and DP favored at L5+ over simple array problems.
Reported problems, listed so you know what to expect. Practice them in your own editor or on the platform you prefer; SupaCV's practice mode coaches how you talk through them.
System Design
(standard from L5/senior up; sometimes seen earlier at L4)
6 questions
Design a URL-shortening service (e.g., TinyURL/goo.gl)
System design staple: ID generation and encoding, redirect latency, and read-heavy caching.
Design a rate limiter (cited as one of the most universally asked system design questions across FAANG, including Google)
System design: token bucket versus sliding window algorithms and distributed counter state.
Design a webpage/system to display real-time status for 10M+ users (name, photo, badge, points), a specifically Google-reported question
System design: fan-out and caching for 10M+ users, freshness versus load trade-offs.
Design a job/task scheduler that assigns jobs to machines with constrained CPU/RAM, also specifically documented as a Google interview question
Resource-aware scheduling: bin packing jobs onto machines under CPU/RAM constraints with queuing and retries.
Design a recommendation system for a content platform (e.g., YouTube-style video recommendations)
System design with ML flavor: candidate generation, ranking, and feedback loops for content recommendations.
Design a scalable, high-throughput backend for a Google-scale product (search-adjacent, ads-adjacent, or infrastructure-flavored prompts are common given Google's product surface)
Tests capacity estimation, partitioning, replication, and latency budgets at Google scale.
Reported problems, listed so you know what to expect. Practice them in your own editor or on the platform you prefer; SupaCV's practice mode coaches how you talk through them.
General Cognitive Ability (GCA) / Analytical & Estimation
6 questions
Open-ended hypothetical prompts, e.g., 'X country has a high advertiser churn rate. As Country Marketing Manager, how would you solve it?' (a documented, specifically-reported Google GCA question)
'You're expected to organize an offsite for your team. How would you go about planning it?' (documented Google hypothetical/GCA-style question)
Fermi/estimation questions: 'How many tennis balls fit into a typical car?'
Fermi/estimation: 'Estimate the number of videos watched on YouTube per day'
Fermi/estimation: 'How much revenue does the Play Store generate per year?'
Fermi/estimation: 'What is the market size for driverless/self-driving cars?' (a specifically documented Google PM/GCA-style estimation question)
Product sense
(product manager)
1 question
What is your favorite product and why? How would you improve it?
Execution and metrics
(product manager)
1 question
Imagine you launch a new feature, and the day after launch usage drops dramatically. How do you investigate the incident?
Estimation and analytical
(product manager)
1 question
How many messages per second does Gmail receive?
Every role
Googleyness & Leadership / Behavioral
8 questions
Tell me about a time you faced a challenge or conflict with a colleague or stakeholder
Tell me about a time you had to come up with a creative solution to a problem
Tell me about a time you created something from nothing (0-to-1 ownership)
Tell me about a time you failed or made a mistake: what did you learn?
Tell me about a time you had to deal with significant ambiguity
Tell me about a time you disagreed with a decision or pushed back on the status quo
Describe a time you had to influence or lead a team without formal authority
Describe a time you received difficult feedback and how you responded
Every role
General Cognitive Ability (GCA) / Analytical & Estimation
1 question
Follow-up probing on a past project: how you defined assumptions, structured the problem, and adapted as new information emerged
Your next step
Interviewing at Google?
Make sure your resume gets you to the first round.
Practicing for Google against your resume is in Interview Prep on Career.
Common questions
Quick answers.
How many stages are in Google's interview process?
Google has 7 stages, set out in The process.
What framework does Google use to evaluate candidates?
Google evaluates candidates against Google's Four Hiring Attributes, set out in What Google scores.
What kinds of questions does Google ask?
Google's questions fall into 7 categories, grouped in The questions.
How reliable is this Google interview playbook?
It is compiled from public sources, and the evidence is in The research.
Sources (37)
Every public source this page was compiled from. Links open in a new tab.
20 sites, by sources
- igotanoffer.com10
- tryexponent.com4
- resumeadapter.com3
- onsites.fyi3
- teamblind.com2
- google.com1
- hellointerview.com1
- glassdoor.com1
- leonstaff.com1
- maryklamo.medium.com1
- coditioning.com1
- interviewing.io1
- designgurus.io1
- cnbc.com1
- entrepreneur.com1
- geeksforgeeks.org1
- aced.io1
- interviewkickstart.com1
- careerflow.ai1
- prepfully.com1
- 01google.com/about/careers/applications/how-we-hire
- 02igotanoffer.com/blogs/tech/google-interview-process
- 03igotanoffer.com/blogs/tech/google-software-engineer-interview
- 04igotanoffer.com/blogs/tech/google-gca-interviews
- 05igotanoffer.com/blogs/tech/google-rrk-interview
- 06igotanoffer.com/blogs/tech/google-behavioral-interview
- 07igotanoffer.com/blogs/tech/googleyness-leadership-interview-questions
- 08igotanoffer.com/blogs/tech/google-interview-questions
- 09igotanoffer.com/blogs/tech/google-system-design-interview
- 10igotanoffer.com/blogs/product-manager/google-associate-product-manager…
- 11igotanoffer.com/blogs/product-manager/google-product-manager-interview
- 12resumeadapter.com/companies/google/interview-process
- 13resumeadapter.com/companies/google/googleyness
- 14resumeadapter.com/companies/google/levels
- 15tryexponent.com/guides/google-swe-interview
- 16tryexponent.com/blog/google-interview-process
- 17tryexponent.com/blog/google-gca-interview
- 18tryexponent.com/blog/google-ai-coding-interview
- 19hellointerview.com/guides/google/l6
- 20glassdoor.com/Interview/Google-Software-Developer-Interview-Question…
- 21teamblind.com/company/Google/posts/google-interview
- 22teamblind.com/post/How-many-interview-loops-for-google-onsite-ogL1N8…
- 23onsites.fyi/blog/article/google-L3-software-engineer-interview-que…
- 24onsites.fyi/blog/article/google-L4-software-engineer-interview-que…
- 25onsites.fyi/blog/article/google-L5-software-engineer-interview-que…
- 26leonstaff.com/blogs/google-interview-response-time-what-to-expect-af…
- 27maryklamo.medium.com/google-hiring-comittee-team-matching-negotiation-10151…
- 28coditioning.com/blog/107/google-swe-team-matching-hiring-committee
- 29interviewing.io/guides/hiring-process/google
- 30designgurus.io/blog/google-system-design-interview-questions-ultimate…
- 31cnbc.com/2025/03/09/google-ai-interview-coder-cheat.html
- 32entrepreneur.com/business-news/google-is-testing-a-new-rule-transform-j…
- 33geeksforgeeks.org/design-a-webpage-that-can-show-the-status-of-10m-users…
- 34aced.io/guides/google-pm-interview
- 35interviewkickstart.com/interview-questions/companies/google/product-manager
- 36careerflow.ai/blog/google-product-manager-interview
- 37prepfully.com/interview-guides/google-product-manager
Related reading
- STAR, XYZ, or CAR: Which Resume Bullet Formula Actually Works?STAR, XYZ and CAR all collapse to the same bullet in practice, why "quantify everything" is more contested than it sounds, and the one modern use of STAR that actually earns its keep.
- Jake's Resume: Why One LaTeX Template Took Over Tech HiringThe history behind the internet's most-copied resume template, why its formatting choices actually work, and how to get the same layout without touching LaTeX.
How similar companies interview
Compare Google's process with other Big Tech companies in this playbook: