Google Interview Questions

Google Coding & Algorithms Interview Questions

Practice 518 real Google interview questions for 2026. Covers Coding & Algorithms, Behavioral & Leadership, Analytics & Experimentation, Machine Learning, and System Design across Software Engineer, Data Scientist, Machine Learning Engineer, Product Manager, and Data Engineer roles — real questions from actual interviews with detailed solutions to accelerate interview preparation. This collection highlights the coding-first bar Google uses: expect heavy algorithmic work, role-related data and ML problems, a Googleyness/leadership round, and level-specific differences in what’s decisive. What’s distinctive: for Software Engineers you’ll see spatial and streaming algorithms, concurrency and async primitives, LLM-foundations and GPU-job scheduling, plus object-design problems like room assignment; Data Scientists are weighted toward causal experiments, funnel and product-metric diagnostics, bootstrap inference, and percentile/sampling algorithms; ML Engineers focus on transformer blocks, recommendation design and ranking cold-starts; PMs get Maps/Android and product-ideation tradeoffs plus throughput and revenue sizing. New-grad and intern tracks emphasize phone screens and virtual onsites; Google L4 typically keeps the loop coding-heavy while Google L5 expects stronger system-design and cross-team leadership signals. Use focused practice, mock interviews, and level-specific stories to prepare.

518 Questions 1 Company08.01.2026
Showing 20 results
Role
Google logo
Google
Hard
Software Engineer

Navigate conflict, difficult people, and culture issues

Answer the following behavioral questions with clear examples (preferably using the STAR method: Situation, Task, Action, Result). Be explicit about y...

Behavioral & Leadership
3
0
35 people solved
Jan 4, 2026
Google logo
Google
Hard
Data Scientist Locked

Model Shot Success by Location

This question evaluates a candidate's skill in spatial probabilistic modeling, feature engineering, calibration, uncertainty quantification, and handl...

Machine Learning
3
0
76 people solved
Dec 3, 2025
Google logo
Google
Hard
Software Engineer

Design distributed transactions protocol

System Design: Distributed Transactions Across Multiple Services Context You must design a distributed transactions protocol to coordinate updates acr...

System Design
10
0
71 people solved
Sep 6, 2025
Google logo
Google
Hard
Data Scientist

Diagnose Google Meet Disconnections and Assess Business Impact

Diagnose Google Meet Disconnections and Assess Business Impact Enterprise clients report that Google Meet calls frequently disconnect. You need to dia...

Analytics & Experimentation
97
0
337 people solved
Jul 12, 2025
Google logo
Google
Hard
Product Manager

Project Leadership Deep Dive

Behavioral PM Onsite: End-to-End Project Leadership Deep Dive Choose one high-impact project you are proud of and walk through it end to end. Then add...

Behavioral & Leadership
14
0
90 people solved
Jul 4, 2025
Google logo
Google
Medium
Software Engineer Locked

Find Containing Range

This question evaluates the ability to design appropriate data structures and apply algorithmic reasoning for efficient interval containment queries, ...

Coding & Algorithms
4
0
19 people solved
Jun 4, 2026
Google logo
Google
Medium
Software Engineer Locked

Find top-k distinct elements

This question evaluates understanding of algorithms and data structures for selecting distinct top-k values and enforcing ordering constraints. It is ...

Coding & Algorithms
25
0
179 people solved
Mar 1, 2026
Google logo
Google
Medium
Data Scientist

Establish causality: commute playlist and driving speed

A lawyer worries that listening to a "Commute" playlist in a mobile app makes users drive faster. As the DS: a) Define the population, unit of analysi...

Analytics & Experimentation
4
0
86 people solved
Oct 13, 2025
Google logo
Google
Medium
Data Scientist

Diagnose 10–11% usage drop across geos

US usage is down 10% and Mexico is down 11%. List plausible confounders (seasonality, pricing, outages, marketing mix, competitor moves, feature rollo...

Analytics & Experimentation
6
0
77 people solved
Oct 13, 2025
Google logo
Google
Hard
Data Scientist

Measure outage impact; choose fix vs build

End-to-End Analysis Plan: Investigating Frequent Google Meet Call Drops Context A major enterprise customer reports frequent Google Meet call drops. A...

Analytics & Experimentation
8
0
58 people solved
Oct 13, 2025
Google logo
Google
Medium
Data Scientist Locked

Estimate sales impact from reviews causally

This question evaluates a data scientist's competency in causal inference, experimental design, observational modeling, and statistical reporting for ...

Analytics & Experimentation
5
0
59 people solved
Oct 13, 2025
Google logo
Google
Medium
Data Scientist

Decide between two vendors under constraints

You have two third‑party search vendors, A and B, plus historical order‑level data: lead_time_days, unit_price, on_time_rate, defect_rate, min_order_q...

Machine Learning
3
0
64 people solved
Oct 13, 2025
Google logo
Google
Hard
Data Scientist

Explain a favorite model end-to-end

Predictive Model Deep-Dive (End-to-End) Pick one predictive model you know deeply (e.g., logistic regression, gradient-boosted trees, transformer clas...

Machine Learning
4
0
60 people solved
Oct 13, 2025
Google logo
Google
Medium
Data Scientist

Analyze Call Drop Rates Pre- and Post-Update Implementation

Analyze Call Drop Rates Pre- and Post-Update Implementation Engineers shipped a new Google Meet version intended to reduce call drops, but a tradition...

Analytics & Experimentation
23
0
71 people solved
Jul 12, 2025
Google logo
Google
Hard
Software Engineer Locked

Find Dictionary Matches for a Jammed String

This question evaluates string-processing and pattern-matching skills, specifically run-length grouping of consecutive characters and efficient dictio...

Coding & Algorithms
7
0
63 people solved
Apr 9, 2026
Google logo
Google
Medium
Software Engineer

Design at-least-once notification delivery

System Design: At-Least-Once Notification System Context Design a multi-channel notification platform (email, SMS, push, in-app) that guarantees at-le...

System Design
12
0
116 people solved
Sep 6, 2025
Google logo
Google
Hard
Software Engineer

Design executable notebook service APIs

Design: Collaborative Notebook with Executable User Functions (JAR Upload) Context Design a collaborative, browser-based code notebook service. The sy...

System Design
10
0
88 people solved
Sep 6, 2025
Google logo
Google
Medium
Data Scientist

Decide confidence level and forecast video views

Decide confidence level and forecast video views Part A — Choosing 95% vs 99% confidence level You are running an A/B test and must choose the confide...

Analytics & Experimentation
3
0
46 people solved
Aug 5, 2025
Google logo
Google
Medium
Software Engineer

Describe a conflict with a colleague

In a behavioral interview for a software engineering or technical role, you are asked: > Tell me about a time you had a conflict or disagreement with ...

Behavioral & Leadership
6
0
64 people solved
Dec 8, 2025
Google logo
Google
Medium
Software Engineer Locked

Find Earliest Fully Connected Time

This question evaluates a candidate's understanding of dynamic graph connectivity, time-ordered event processing, and state maintenance in graphs, inc...

Coding & Algorithms
33
1
446 people solved
Apr 5, 2026

Frequently Asked Questions

How hard are Google interview questions and how does difficulty vary by level?
Google interview questions are challenging but predictable: they range from medium algorithmic problems for new grads to hard, system- and architecture-focused problems at senior levels. L3/new-grad interviews emphasize correct, clean code with solid complexity and edge-case handling; expect two to three coding rounds plus a Googleyness/leadership conversation. L4 requires optimal solutions, clearer trade-off communication, and sometimes a system-design or domain round. L5 raises the bar on system design, scalability, ownership, and leadership impact. Non-SWE roles shift emphasis toward statistics, experiment design, or model-building depending on the job.
What does the Google interview process look like and where do these 518 questions appear?
The typical loop starts with a recruiter screen, one or more phone or virtual coding screens, then a virtual or in-person onsite loop of 3–5 forty-five minute interviews: mostly coding, plus a Googleyness/leadership behavioral round and usually one domain or system-design session for mid and senior roles. The 518-question corpus covers those stages: phone-screen style coding, onsite deep-coding, system-design prompts, analytics/experiment questions for data roles, ML implementation prompts, and product-spec behavioral cases. Hiring committee review, level calibration, and team match happen after the loop and extend timelines by several weeks.
How should I schedule my preparation and how much time do I need to prepare effectively?
Plan prep based on level and role: new grads should spend 4–6 weeks focused on core data structures, algorithm patterns, and 4–6 polished STAR stories. Mid-level L4 candidates should budget 6–10 weeks, adding system design and production-readiness topics plus mock interviews. L5 and above need 8–12+ weeks emphasizing architecture, trade-offs, and leadership narratives. Break weeks into coding practice, timed mocks, system-design sprints, and role-specific work (experiments for DS, model lifecycle for MLE). Run at least 6–10 realistic mock interviews and iterate on communication and edge-case testing.
What specific subtopics and recurring themes should I expect by role at Google?
For Software Engineer interviews expect spatial and streaming geometry problems (counting or removing points within distance), concurrency and async primitives, deterministic task ordering and schedulers, calendar/free-slot algorithms, boolean-expression fixes, array/subarray patterns, and small-system OOD prompts like dorm room assignment. Data Scientist questions concentrate on causal and experiment design, funnel and product-metric computation, unbiased upgrade experiments, bootstrap and percentile estimation from buckets, sampling algorithms, and applied modeling like shot-conversion. Machine Learning Engineer rounds emphasize transformer/LLM building blocks and trade-offs, recommendation and ranking cold-start strategies, weighted sampling, and implementation details.
Any standout tips and common pitfalls, including level-specific advice (L3, L4, L5) and intern/new-grad notes?
Start by matching preparation to level: L3/new-grad must deliver correct, well-tested code and clear complexity; L4 must reach optimal solutions, explain trade-offs, and show production thinking; L5 must demonstrate architecture, scaling trade-offs, and cross-team impact. For interns/new-grads expect a phone coding screen followed by a virtual onsite; practice timed screens and basic system thinking. Across levels, talk through examples, define constraints, test edge cases, and avoid premature optimization or vague assumptions. Prepare 4–6 STAR stories for Googleyness, and don’t overlook clear, testable code and thought-out system trade-offs.

Explore more Google interview questions

Jump straight to Google questions for a specific role or category.

By role
By category
In-depth guides
Across all companies

Featured Google interview prep guides

Concept walkthroughs, worked examples, and the real questions from candidate reports.

Editorial prep
Machine Learning Engineer
Google interview
Read the guide