Company
Google interview questions
486 practice questions in the style of Google's interviews, covering Behavioral & Leadership, Coding & Algorithms, Machine Learning, Statistics & Math, Data Manipulation (SQL/Python), Analytics & Experimentation, Product / Decision Making, Software Engineering Fundamentals, ML System Design, System Design, Product Design & Strategy.
35 easy348 medium103 hard
Google interview questions by the numbers
Last updated
Katkat has 486 Google interview questions. The largest topics are Coding & Algorithms (40%), Behavioral & Leadership (19%) and System Design (8%). By difficulty: 7% easy, 72% medium and 21% hard. The most common round is Technical Screen (52%). Frequent concepts include Data Structures, Greedy, Algorithms and Optimization.
Topics
- Coding & Algorithms40% · 192
- Behavioral & Leadership19% · 94
- System Design8% · 40
- Statistics & Math7% · 32
- Machine Learning6% · 28
- Analytics & Experimentation5% · 23
- ML System Design3% · 15
Difficulty
- Easy7% · 35
- Medium72% · 348
- Hard21% · 103
Interview rounds
- Technical Screen52% · 253
- Onsite42% · 204
- Online Assessment2% · 12
- Other2% · 10
- HR Screen1% · 7
Roles
- Software Engineer65% · 317
- Data Scientist20% · 96
- Machine Learning Engineer7% · 35
- Product Manager5% · 25
- Data Analyst1% · 5
Frequent concepts
- Data Structures5% · 24
- Greedy5% · 22
- Algorithms4% · 21
- Optimization4% · 19
- Arrays3% · 17
- Graph3% · 14
Most mentioned in interview experiences
- 1.Choose Your Workplace Style3 reports
- 2.Select MOST/LEAST appropriate actions (SJT)3 reports
- 3.Choose best/worst actions in workplace ethics scenarios2 reports
- 4.Choose Non-Overlapping Weighted Jobs to Maximize Total Profit2 reports
- 5.Decide string transform with directional tokens and walls2 reports
- 6.Describe a conflict with a colleague2 reports
- 7.Describe a major challenge you faced2 reports
- 8.Design a Spam Review Workflow with Classifiers, AI Agents, and Human Labelers2 reports
- 9.Explain handling a tight project deadline2 reports
- 10.Grid Reachability From Start to Target With Impassable Water Cells2 reports
Counted from 74 candidate interview experiences on Katkat. How we collect and count
Showing 181–210 of 486 results
This question evaluates proficiency in multi-GPU parallelism and system-level ML engineering, covering data partitioning, inter-GPU communication primitives, compute scheduling and overlap, memory layout and buffer reuse, numerical precision trade-offs, synchronization, scalability, and failure handling.
GoogleMachine Learning EngineerML System DesignTechnical ScreenThis question assesses the ability to design a high-concurrency geospatial system that maintains real-time state for moving entities and supports low-latency queries.
GoogleSoftware EngineerSystem DesignTechnical ScreenThis question evaluates a candidate's understanding of distributed system design and engineering competencies related to quota enforcement, high-throughput rate limiting, consistency models, sharding, and concurrency control under very high QPS.
GoogleSoftware EngineerSystem DesignTechnical ScreenThis question evaluates a candidate's competency in designing a relational-to-NoSQL migration pipeline, covering distributed systems and data engineering concepts such as consistent snapshotting, change-data-capture, per-key ordering, idempotency, exactly-once behavior, schema evolution, partitioning, and operational reliability.
GoogleSoftware EngineerSystem DesignTechnical ScreenThis question evaluates understanding of scalable resource-allocation and matching systems, encompassing data-structure and index design, availability tracking, fragmentation minimization, concurrency control, and failure handling for large node pools.
GoogleSoftware EngineerCoding & AlgorithmsTechnical ScreenThis question evaluates skill in designing a composite data structure that supports average O(1) insertion, deletion, and uniform random access, and tests understanding of hashing, indexing, randomness, and concurrency control.
GoogleSoftware EngineerCoding & AlgorithmsTechnical ScreenThis question tests the ability to design a high-throughput, fault-tolerant ingestion pipeline for massive geospatial media, focusing on distributed storage strategies, data integrity, and efficient retrieval at scale.
GoogleSoftware EngineerSystem DesignTechnical ScreenThis problem tests your ability to design a dynamic data structure that maintains elements while efficiently querying the k-th largest value, necessitating a balance between insertion speed and retrieval performance.
GoogleSoftware EngineerCoding & AlgorithmsOnsiteA Google Data Scientist onsite case on measuring the causal impact of reduced YouTube video-start latency on engagement. It spans A/B design (primary metric, diagnostics, error/buffering guardrails), randomization unit and interference, power/MDE for heavy-tailed watch time, variance reduction (CUPED, stratification), analysis of conflicting movements, ratio-metric decomposition with Simpson’s paradox, and propensity score matching when randomization isn’t possible.
GoogleData ScientistAnalytics & ExperimentationOnsiteThis question evaluates a candidate's ability in large-scale system design, covering distributed state management, API design, data modeling for per-user progress, idempotent update semantics, cross-device synchronization, and privacy/compliance considerations.
GoogleSoftware EngineerSystem DesignTechnical ScreenAssess the candidate's understanding of reward hacking (specification gaming) in reinforcement learning from human feedback (RLHF), focusing on diagnosing exploitation patterns, designing detection metrics, applying conservative policy updates, and implementing recovery safeguards.
GoogleMachine Learning EngineerMachine LearningTechnical ScreenDetermine which players in a competition have a uniquely determined ranking given a set of pairwise match outcomes.
GoogleSoftware EngineerCoding & AlgorithmsOnsiteDetermine Impact of New Chat-Notification on User Engagement evaluates statistical assumptions, formulas, estimation strategy, uncertainty, edge cases, and interpretation in a realistic interview setting. A strong answer states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.
GoogleData ScientistStatistics & MathTechnical ScreenEvaluates hypothesis testing for a single observation against a fully specified standard normal distribution. Strong answers state hypotheses, use z = x, define critical values and p-values, and note limitations.
GoogleData ScientistStatistics & MathTechnical ScreenThis question evaluates understanding of hierarchical relationship modeling, transitive inference across relations, and dynamic data-structure design for tracking manager and peer links.
GoogleSoftware EngineerCoding & AlgorithmsTechnical ScreenThis problem tests the ability to implement a depth-first search (DFS) with backtracking to find a specific sequence within a grid, while managing state to avoid reusing the same path.
GoogleSoftware EngineerCoding & AlgorithmsOnsiteThis interview question evaluates algorithm design, data structures, correctness, complexity, edge cases, and implementation details in a realistic interview setting. A strong answer for Determine validity after digit-constrained deletions states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.
GoogleSoftware EngineerCoding & AlgorithmsOnsiteThis problem tests your ability to determine connectivity between two nodes in a directed graph, specifically modeling ancestry relationships.
GoogleSoftware EngineerCoding & AlgorithmsTechnical ScreenThis problem tests your ability to model a combinatorial game using the Sprague-Grundy theorem and memoization to determine the winner of a state-dependent stack-merging process.
GoogleSoftware EngineerCoding & AlgorithmsTechnical ScreenThis question tests the ability to implement Kahn's algorithm for topological sorting while using a min-priority queue to satisfy specific tie-breaking requirements.
GoogleSoftware EngineerCoding & AlgorithmsOnsiteEvaluates reliability analytics for Google Meet disconnections and enterprise renewal impact. Strong answers define call drops, use client and server logs to localize root causes, estimate account-level retention impact, and prioritize fixes using quantified business risk.
GoogleData ScientistAnalytics & ExperimentationTechnical ScreenThis question evaluates a data scientist's competency in precise metric and population definition, time‑to‑event and survival/hazard modeling, time‑series decomposition and change‑point analysis, instrumentation and traffic forensics, and experimental design for root‑cause identification.
GoogleData ScientistAnalytics & ExperimentationOnsiteThis question tests your ability to diagnose poor model performance in a binary classification task involving imbalanced data, high-cardinality categorical features, and potential bias.
GoogleData ScientistMachine LearningTechnical ScreenThis question evaluates a data scientist's competency in product analytics and experimentation, covering precise metric definition and validation, instrumentation and event quality checks, rapid triage of adoption regressions, hypothesis generation, experiment design, and causal inference.
GoogleData ScientistAnalytics & ExperimentationOnsiteThis question assesses your ability to navigate workplace friction and manage competing priorities through structured reflection and professional communication.
GoogleSoftware EngineerBehavioral & LeadershipOnsiteThis question assesses a candidate's ability to analyze distributed system failures, communicate technical post-mortems clearly, and demonstrate personal accountability and iterative improvement.
GoogleSoftware EngineerBehavioral & LeadershipTechnical ScreenDetermine the earliest timestamp at which all nodes in a network become part of a single connected component using a chronological sequence of edge additions.
GoogleSoftware EngineerCoding & AlgorithmsOnsiteA system design exercise where a country provides an API reporting whether an IP address is banned and the service must refuse connections from banned addresses. It tests scoping questions such as IPv6 and address ranges, fast local enforcement at the edge, keeping ban data fresh, and fail-safe compliance behavior.
GoogleSoftware EngineerSystem DesignOnsiteEvaluates core statistical inference skills across p-values, confidence intervals, standard error reduction, tail probability estimation, efficient conversion-rate sampling, and truncated-normal estimation. Strong answers state assumptions, use appropriate intervals and weights, and avoid common interpretation errors.
GoogleData ScientistStatistics & MathOnsiteEstimate a percentile from histogram buckets by locating the cumulative-count bucket, explaining why midpoint can be poor, interpolating within the bucket under explicit assumptions, handling log-spaced buckets and edge cases, and reporting uncertainty when buckets are coarse.
GoogleData ScientistStatistics & MathTechnical Screen
Google interview experiences
All 103 →- A Huge YAML Merge Problem and a Knapsack That Wants QuickselectGoogle · Software Engineer · Intern · Technical Screen · Oct 2026
The first-round interviewer was really nice, but the problem was super long. Reading and understanding the problem plus the examples can take maybe 20 minutes. Roughly, it is merging two trees (YAML files), where every node has merge rules, and there are a lot of rules. The approach is DFS plus rule matching. The second-round interviewer gave me a knapsack problem, but for this one DP or DFS with…
- Back-to-Back Phone Screens: Behavioral, Then an HTTP RouterGoogle · Software Engineer · Technical Screen · Oct 2026
After I finished the psychological test, they scheduled my phone interviews right away. It was two rounds back to back, 45 minutes each, and I don't know if that's normal. The first round was a behavioral round with a really nice interviewer. All the questions were the usual ones: what do you do if you disagree with a coworker, what do you do if you disagree with another team, what do you do if a…
- In-Person Onsite with a Design Round and a Train Schedule QuestionGoogle · Software Engineer · Onsite · Oct 2026
The onsite was in-person (but virtual was an option) and only two rounds. I only had 4 interviews total with Google. Onsite was solutions design and Leetcode question. Solutions design question was design a review ingestion platform for an e-commerce site that takes reviews and summarizes them with an LLM for an internal dashboard. Focus on trust and safety, prompt injection, data sanitization, P…
- 10-Minute Resume Grill, Then First Missing Positive in O(1) SpaceGoogle · Software Engineer · Intern · Technical Screen · Sep 2026
The interview started right on time and went straight into an intense 10-minute resume grill. The interviewer homed in on my recent backend work, specifically asking detailed questions about the Kafka streaming architecture and Redis caching implementations from my previous internship in the Platform Cloud org. They also dug into the technical trade-offs I made when building Bastion, focusing hea…
- An Unexpected Forecasting Question and a Fast Offer TimelineGoogle · Data Scientist · Onsite · Sep 2026Offer
I signed Google's offer a couple of days ago, though I still have a few other issues to resolve. I'm sharing my interview experience and preparation package, and hoping I can start smoothly. First round Stats: Questions about p-values, simple linear regression, confidence intervals, and similar topics. Data: Compare two vendors' models. There are similar questions in other interview reports. Seco…
More companies
- Meta666
- Amazon653
- OpenAI342
- Capital One268
- Microsoft252
- DoorDash241
- Anthropic225
- Uber217
- Apple177
- TikTok176
- Pinterest161
- ByteDance160
- LinkedIn154
- Stripe139
- Snowflake130
- Databricks122
- Airbnb112
- Rippling106
- Oracle104
- Coinbase99
- Netflix97
- NVIDIA95
- Snapchat94
- Citadel90
- Waymo90
- Instacart87
- Roblox84
- Salesforce77
- Optiver76
- Shopify63
- Robinhood60
- Atlassian55
- Hudson River Trading55
- Two Sigma55
- J.P. Morgan53
- PayPal53
- xAI53
- Lyft52
- Tesla52
- Other51
