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 241–270 of 486 results

  • This question evaluates a candidate's end-to-end machine learning competencies, including problem framing, objective and loss selection, inductive biases, feature engineering, validation strategies, training and regularization practices, production issues, monitoring, and fairness/privacy considerations.

    GoogleData ScientistMachine LearningOnsite
  • This question evaluates understanding of Simpson's paradox, confounding, and causal reasoning, checking numerical interpretation of subgroup versus aggregate statistics and the ability to recognize when aggregated averages can mislead.

    GoogleData ScientistStatistics & MathTechnical Screen
  • This question evaluates time management, prioritization, communication, teamwork, and leadership competencies in delivering technical work under pressure.

    GoogleSoftware EngineerBehavioral & LeadershipOnsite
  • This question assesses the ability to communicate complex statistical models to non-technical stakeholders, focusing on clarity, intuition, and identifying limitations.

    GoogleData ScientistMachine LearningTechnical Screen
  • This question evaluates understanding of mixed effects models, the conceptual distinction between fixed and random effects, interpretation of coefficients and variance components, and awareness of practical pitfalls when modeling hierarchical or panel data.

    GoogleData ScientistStatistics & MathOnsite
  • This question evaluates end-to-end ML ownership and operational troubleshooting skills, including detection of data and modeling issues, trade-off analysis, and evidence-based impact measurement within the Machine Learning/MLOps domain.

    GoogleMachine Learning EngineerMachine LearningTechnical Screen
  • This question tests your ability to design strategies for surfacing new items and serving new users in a large-scale recommendation system while maintaining relevance and diversity.

    GoogleMachine Learning EngineerMachine LearningTechnical Screen
  • This question evaluates a candidate's mastery of transformer architecture and related competencies such as attention mechanisms, positional encodings, encoder/decoder variants, computational complexity and scaling, stability and initialization practices, and adaptation of sequence models to molecular representations.

    GoogleMachine Learning EngineerMachine LearningTechnical Screen
  • This question evaluates a candidate's understanding of process creation and execution, shell command resolution, kernel and VFS filesystem interactions, and how directory entries and file metadata are retrieved; category/domain: Software Engineering Fundamentals.

    GoogleSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • Prepare for a Product Manager internship behavioral interview by structuring your PM transition story, project examples, career goals, stakeholder relationship approach, and personal-interest answer. This guide shows what strong interviewers listen for and how to avoid generic or unsupported answers.

    GoogleProduct ManagerBehavioral & LeadershipTechnical Screen
  • Practice explaining technical work to non-technical stakeholders with a clear problem, plain-language approach, measurable outcomes, trade-offs, cross-functional collaboration, before-and-after metrics, and interview-ready communication tips.

    GoogleProduct ManagerBehavioral & LeadershipTechnical Screen
  • Given a satellite image as a grid of land and water cells and a starting cell, traverse the island containing that cell with breadth-first search, then extend the solution to count lakes, bodies of water completely enclosed by land. It tests grid traversal, precise problem definitions, connectivity rules and linear-time flood fill.

    GoogleSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • Practice a PM onsite prompt about products you worked on, admired products, and improvement metrics. The guide covers product storytelling, North Star and input metrics, product taste, a non-tech improvement example, primary and guardrail metrics, and practical experiment design.

    GoogleProduct ManagerProduct / Decision MakingOnsite
  • Practice a product sense and roadmapping prompt about admired products and improvement planning. The solution compares Google Maps, Notion, and IKEA, then deep-dives on a Google Maps parking confidence roadmap with target users, pain points, MVP phases, success metrics, experiments, and guardrails.

    GoogleProduct ManagerBehavioral & LeadershipOnsite
  • Design an algorithm to rate-limit and deduplicate a stream of robot status messages so identical messages only display if strictly more than ten seconds have elapsed since their last displayed occurrence.

    GoogleSoftware EngineerCoding & AlgorithmsTechnical Screen
  • Find the minimum security clearance needed to travel between two nodes in a graph where edges exceeding a given latency threshold cannot be used.

    GoogleSoftware EngineerCoding & AlgorithmsTechnical Screen
  • Tests your ability to process and merge multiple sets of time intervals to find mutually available time windows within a given working day.

    GoogleSoftware EngineerCoding & AlgorithmsOnsite
  • This problem tests your ability to optimize interval lookup operations by preprocessing data into an efficient search structure to handle containment queries in sub-linear time.

    GoogleSoftware EngineerCoding & AlgorithmsTechnical Screen
  • This problem tests your ability to normalize input strings by grouping consecutive identical characters and efficiently searching a dictionary for potential word matches.

    GoogleSoftware EngineerCoding & AlgorithmsTechnical Screen
  • This problem tests your ability to efficiently track the connectivity of a graph as edges are added over time, requiring an understanding of Union-Find data structures and graph theory.

    GoogleSoftware EngineerCoding & AlgorithmsOnsite
  • Tests interval processing, sorting, and tracking concurrent overlapping ranges using heaps or two-pointer sweep-line techniques.

    GoogleSoftware EngineerCoding & AlgorithmsTechnical Screen
  • Implement algorithms to analyze top-to-bottom paths in a blocked, cell-weighted grid: reachability check, deterministic path enumeration, and minimum-cost path finding with lexicographic tie-breaking.

    GoogleSoftware EngineerCoding & AlgorithmsOnsite
  • This problem tests your ability to optimize search operations across multiple data sources, focusing on minimizing high-latency API calls by using heuristic strategies and efficient state management.

    GoogleSoftware EngineerCoding & AlgorithmsOnsite
  • Tests computational geometry and algorithmic efficiency by finding a horizontal line that bisects the total area of non-overlapping rectangles using sweep-line or binary search techniques.

    GoogleSoftware EngineerCoding & AlgorithmsTechnical Screen
  • This problem tests your ability to efficiently match a query string against a dictionary of patterns containing wildcards and determine the best match based on predefined precedence rules.

    GoogleSoftware EngineerCoding & AlgorithmsOnsite
  • This problem tests your ability to navigate tree structures and perform post-order traversal to identify an ancestor node based on a custom aggregate criterion (the minimum value).

    GoogleSoftware EngineerCoding & AlgorithmsOnsite
  • This problem tests your ability to optimize search operations within a hidden set of dependencies by minimizing calls to a costly black-box oracle.

    GoogleSoftware EngineerCoding & AlgorithmsOnsite
  • This question evaluates computational geometry and algorithm design skills, focusing on area computation, monotonicity reasoning, existence proofs, root-finding under floating-point constraints, and considerations of numerical stability and complexity.

    GoogleSoftware EngineerCoding & AlgorithmsOnsite
  • This question evaluates algorithmic problem-solving with ordered data structures, specifically understanding how to combine two sorted arrays efficiently, priority-queue or merge-based reasoning, and time/space complexity analysis in the coding and algorithms domain.

    GoogleSoftware EngineerCoding & AlgorithmsTechnical Screen
  • This question evaluates a candidate's ability to reason about digit-based frequency analysis and efficient counting on arrays, testing competencies in combinatorics and algorithmic optimization for grouping elements by shared features.

    GoogleSoftware EngineerCoding & AlgorithmsOnline Assessment

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