Katkat

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.

Questions486

35 easy348 medium103 hard

Your progress0/486

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.

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

Showing 61–90 of 486 results

  • Evaluates binary classification model selection with limited labeled data. Strong answers explain logistic regression and cross-entropy loss, compare it with Random Forests, cover L1 and L2 regularization, diagnose overfitting, and contrast Random Forests with boosting.

    GoogleData ScientistMachine LearningOnsite
  • This question tests the conceptual understanding of tokenization strategies in NLP and the architectural trade-offs when integrating LLMs into recommendation systems.

    GoogleMachine Learning EngineerMachine LearningOnsite
  • This question evaluates a data scientist's skills in experimental design, causal inference (including difference-in-differences), measurement and metric construction for profitability, uncertainty quantification (confidence intervals and power checks), and operational guardrails for real-world data collection.

    GoogleData ScientistAnalytics & ExperimentationTechnical Screen
  • Practice a comprehensive Spotify product improvement case covering product taste, target users, North Star metrics, Smart Offline Mode, roadmap prioritization, experiments, guardrails, and stakeholder alignment. The solution emphasizes quality-adjusted listening, offline pain points, MVP scope, and cross-functional execution.

    GoogleProduct ManagerProduct / Decision MakingOnsite
  • Implement methods to compute the recursive byte size of an entity in a hierarchical file system and validate the structural integrity of the file system graph.

    GoogleSoftware EngineerSoftware Engineering FundamentalsOnsite
  • This problem tests your ability to manage state in a queue-based simulation and implement complex tie-breaking logic using data structures like heaps or prioritized queues.

    GoogleSoftware EngineerCoding & AlgorithmsTechnical Screen
  • Implement and compare recursive and iterative traversals to compute the depth-weighted sum of an arbitrarily nested list of integers, handling deep nesting and edge cases.

    GoogleSoftware EngineerCoding & AlgorithmsOnsite
  • This problem tests your ability to efficiently compute shortest path distances from multiple sources to all reachable grid cells using multi-source Breadth-First Search (BFS).

    GoogleSoftware EngineerCoding & AlgorithmsTechnical Screen
  • This question evaluates combinatorial optimization, state-space reasoning, and algorithmic design for constrained token movements on a linear board, and falls under the Coding & Algorithms domain.

    GoogleSoftware EngineerCoding & AlgorithmsOnline Assessment
  • This question tests the ability to solve pathfinding problems using non-standard cost metrics: first, finding a minimax path in a grid, and second, calculating the earliest arrival time in a network with weighted edges.

    GoogleSoftware EngineerCoding & AlgorithmsTechnical Screen
  • This problem tests your ability to manage overlapping intervals in a circular domain by converting cyclic tasks into linear sub-intervals and applying a sweep-line or greedy approach to determine resource requirements.

    GoogleSoftware EngineerCoding & AlgorithmsTechnical Screen
  • This question evaluates a data scientist's competency in model evaluation for imbalanced binary classification, covering understanding of precision–recall dynamics, calibration, AUPRC, cost‑sensitive metrics, and practical implementation concerns like computing thresholds and handling ties and numerical edge cases; domain: Coding & Algorithms and machine learning model evaluation. It is commonly asked in technical interviews because it assesses both conceptual understanding of evaluation trade‑offs and the practical application of efficient, robust metric computation and threshold selection under asymmetric costs and operational constraints.

    GoogleData ScientistCoding & AlgorithmsTechnical Screen
  • This question evaluates understanding of interval-based resource allocation and job grouping by identifier, testing competency in managing overlapping time intervals, capacity planning, and handling day-boundary truncation.

    GoogleSoftware EngineerCoding & AlgorithmsTechnical Screen
  • This question evaluates understanding of graph traversal and shortest-path techniques under constraints, including avoidance of forbidden nodes, multi-criteria optimization (minimizing dangerous-node visits then steps), and reasoning about augmented state and visited-structure design.

    GoogleSoftware EngineerCoding & AlgorithmsOnsite
  • This question evaluates proficiency with graph algorithms, shortest-path and reachability concepts when nodes are removed or blocked, and the ability to analyze time and space complexity across directed and undirected graphs.

    GoogleSoftware EngineerCoding & AlgorithmsTechnical Screen
  • This problem tests your ability to maintain order statistics in a sliding window using balanced data structures or heaps to perform efficient removals and updates while excluding the top k elements.

    GoogleSoftware EngineerCoding & AlgorithmsTechnical Screen
  • This problem tests your ability to identify contiguous subarrays that follow an arithmetic progression with a common difference of 1 (consecutive steps) and calculate the sum of elements within these subarrays efficiently.

    GoogleMachine Learning EngineerCoding & AlgorithmsOnsite
  • Merge two sorted lists of disjoint closed intervals into a single sorted list of disjoint intervals in linear time.

    GoogleSoftware EngineerCoding & AlgorithmsOnsite
  • This question assesses the candidate's ability to bridge their past academic or research expertise with the practical, scaled objectives of a commercial product team while demonstrating technical humility and goal alignment.

    GoogleResearch ScientistBehavioral & LeadershipOnsite
  • Consolidate overlapping on-call shift intervals into non-overlapping segments, each annotated with the sorted list of active engineers.

    GoogleSoftware EngineerCoding & AlgorithmsOnline Assessment
  • This problem tests your ability to design a constructive grid layout that satisfies connectivity and size constraints, followed by pathfinding through dynamic or constrained environments.

    GoogleMachine Learning EngineerCoding & AlgorithmsTechnical Screen
  • This problem tests your ability to model geometric data as a graph and identify connected components using traversal algorithms or Disjoint Set Union (DSU).

    GoogleSoftware EngineerCoding & AlgorithmsTechnical Screen
  • Tests modeling geometric proximity as a graph problem, using Disjoint Set Union or graph traversal to identify connected components while ensuring exact integer arithmetic and handling duplicate coordinates.

    GoogleSoftware EngineerCoding & AlgorithmsTechnical Screen
  • Practice counting binary-grid components when diagonal neighbors connect, changing the usual four-direction island definition.

    GoogleFrontend EngineerCoding & AlgorithmsOnsite
  • Tests graph traversal, bitmask dynamic programming or backtracking with pruning, and prefix counting on small labeled graphs.

    GoogleSoftware EngineerCoding & AlgorithmsTechnical Screen
  • Implement an algorithm to compute cell-by-cell coverage counts for an n x n grid given multiple inclusive rectangular regions.

    GoogleSoftware EngineerCoding & AlgorithmsOnsite
  • Count the paths across an n by m grid from the bottom-left to the bottom-right cell when each move goes up-right, right or down-right, optionally passing through checkpoints in a required order, modulo a large prime. It tests column-by-column dynamic programming and reducing memory use.

    GoogleSoftware EngineerCoding & AlgorithmsOnsite
  • Count super-streak segments in a time-ordered event stream with an O(n) scan. The solution explains maximal segment boundaries, inclusive gap handling, duration and count checks, edge cases, streaming behavior, and changing-threshold follow-ups.

    GoogleData ScientistCoding & AlgorithmsTechnical Screen
  • This question evaluates a candidate's ability to parse and process large-scale event logs, perform sessionization based on time gaps, handle out-of-order records and memory constraints, and reason about time and space complexity and optimization strategies in the Coding & Algorithms domain.

    GoogleSoftware EngineerCoding & AlgorithmsOnsite
  • This question evaluates a candidate's competency in decision modeling and cost‑sensitive machine learning, including causal inference for selection bias, propensity estimation, constrained optimization for capacity and SLA trade‑offs, and offline/online evaluation in the Machine Learning domain for a Data Scientist role.

    GoogleData ScientistMachine LearningOnsite

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 2026
    Offer

    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