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 451–480 of 486 results

  • This question evaluates proficiency in parsing and expression evaluation, recursion/stack management, and string-processing for nested function-style arithmetic, alongside graph modeling, geometric distance reasoning, and traversal algorithms for the bomb chain-reaction scenario; the category is Coding & Algorithms.

    GoogleSoftware EngineerCoding & AlgorithmsOnsite
  • This question tests the ability to solve two distinct algorithmic patterns: using a prefix sum hash map to count subarrays with a target sum, and using flood fill to determine the size of connected components in a grid.

    GoogleSoftware EngineerCoding & AlgorithmsTechnical Screen
  • Validate feature configuration strings using modular polynomial checksums and resolve valid deployment sequences using dependency graph analysis and cycle detection.

    GoogleSoftware EngineerCoding & AlgorithmsOnline Assessment
  • This problem tests your ability to model complex system dependencies as a directed graph and determine the minimum time to complete a set of tasks given sequential constraints.

    GoogleSoftware EngineerCoding & AlgorithmsOnsite
  • This problem tests your ability to manage hierarchical dependencies using topological sorting and perform block-wise aggregate computations on grid-based data structures.

    GoogleSoftware EngineerCoding & AlgorithmsTechnical Screen
  • This problem tests your ability to manage overlapping intervals using a priority queue and calculate the shortest path in a DAG representing dependencies.

    GoogleSoftware EngineerCoding & AlgorithmsOnsite
  • This problem tests your ability to use Fenwick trees for order statistics and the properties of prefix XORs to solve counting problems efficiently.

    GoogleSoftware EngineerCoding & AlgorithmsOnsite
  • This problem tests your ability to perform string-based arithmetic and handle edge cases in digit-by-digit computation.

    GoogleSoftware EngineerCoding & AlgorithmsTechnical Screen
  • Implement an ML pipeline optimization engine that calculates critical path latency and peak parallelism for a task DAG, and optimizes streaming checkpoint placement under sliding-window constraints using dynamic programming.

    GoogleMachine Learning EngineerCoding & AlgorithmsOnsite
  • This set tests proficiency in recursive string decoding, dynamic programming for sequential decision-making, and graph-based traversal algorithms for grid analysis.

    GoogleSoftware EngineerCoding & AlgorithmsOnsite
  • This set of problems evaluates algorithmic problem-solving across combinatorics and enumeration (finding the N-th lexicographic license plate), constrained geometric and graph traversal reasoning (counting Android-style 3x3 unlock patterns), and interval-processing algorithms (computing intersections of sorted, non-overlapping intervals) within the domain of algorithms and data structures. These questions are commonly asked because they reveal ability to reason about discrete enumeration, constraint handling, and efficient time/space implementations for edge-case-heavy inputs, and the level of abstraction spans both conceptual understanding (combinatorial and geometric constraints) and practical application (efficient algorithm and data-structure implementation).

    GoogleSoftware EngineerCoding & AlgorithmsOnsite
  • This problem tests the ability to maintain and query a dynamic sorted collection of points to perform efficient proximity-based removals.

    GoogleSoftware EngineerCoding & AlgorithmsOnsite
  • A behavioral round for a senior software engineer covering a successful project, a conflict with teammates, a time your negative view of a teammate turned positive, and the organizational values you want next. It tests ownership, conflict handling, self-awareness and genuine motivation.

    GoogleSoftware EngineerBehavioral & LeadershipTechnical Screen
  • Technical deep-dive question from a senior software engineer loop at Google: explain the architecture of a service you own and walk through its technical details. It tests whether a candidate can present purpose, scale and data flow clearly, then defend design choices, failure handling and trade-offs under probing.

    GoogleSoftware EngineerSystem DesignOther
  • A behavioral conflict question asking for a time you had to compromise, followed by probes on whether you were satisfied with the result, what you did afterwards to achieve what you gave up, and how you will act differently. It tests conflict handling, judgment, follow-through and honest self-reflection.

    GoogleSoftware EngineerBehavioral & LeadershipTechnical Screen
  • This question evaluates a candidate's competence in statistical inference for linear regression—specifically hypothesis testing for OLS coefficients, construction of t-statistics, estimation of standard errors, and the role of estimated error variance—within the Statistics & Math domain for Data Scientist roles.

    GoogleData ScientistStatistics & MathTechnical Screen
  • This question tests the ability to perform statistical hypothesis testing on a single observation, evaluate the limitations of small sample sizes, and explain the trade-offs between Type I and Type II errors.

    GoogleData ScientistStatistics & MathTechnical Screen
  • Six behavioral questions for a software engineer covering the most challenging project, collaboration with another team, mentoring, receiving criticism, handling ambiguity, and responding when someone disagrees with you. It tests story selection, a clearly personal role, honest reflection, and concise STAR-style delivery without a warm-up introduction.

    GoogleSoftware EngineerBehavioral & LeadershipTechnical Screen
  • Report the initial number of grid islands and update that count after each requested water-to-land addition. The problem probes incremental connectivity, duplicate additions, local merge effects, scalability to large grids, and alternatives to recomputing the entire map.

    GoogleSoftware EngineerCoding & AlgorithmsOnsite
  • Design a class that records undirected messages between users and returns the user who has talked with the most distinct people, then make that query constant time and add a top-K query whose k changes on every call. It tests deduplication with hash sets, space analysis of per-user sets, and incremental ranking structures.

    GoogleSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • Implement a request router that registers path templates with {variable} and {*catch-all} segments and resolves a concrete path to its handler and captured values. Tests trie design, literal-over-variable precedence with backtracking, conflict detection, and lookup complexity.

    GoogleSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • This question evaluates system troubleshooting and diagnostic competencies, including Linux CPU and IO performance analysis, network latency and packet-level investigation, and DNS resolution and query tooling knowledge.

    GoogleSoftware EngineerCoding & AlgorithmsOnsite
  • A product strategy prompt asking how a product manager would take a newly developed text-to-video generation model to market. It tests choosing a first segment, product form and distribution, safety and likeness safeguards, pricing under high compute costs, and a staged launch with clear success metrics.

    GoogleProduct ManagerProduct Design & StrategyOther
  • This interview question evaluates statistical assumptions, formulas, estimation strategy, uncertainty, edge cases, and interpretation in a realistic interview setting. A strong answer for Understand Simpson's Paradox with Simple Examples states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

    GoogleData ScientistStatistics & MathOnsite
  • This question evaluates a candidate's ability to process semi-structured event data using grouping, deduplication, and timestamp arithmetic in Python. It falls under coding and algorithms, commonly asked to assess practical data-wrangling skills such as aggregating per-key counts and computing time-based metrics while handling edge cases like unordered records and single-event users.

    GoogleData EngineerCoding & AlgorithmsTechnical Screen
  • This question evaluates understanding of graph algorithms and data validation, specifically dependency analysis, cycle detection, and topological ordering.

    GoogleSoftware EngineerCoding & AlgorithmsTechnical Screen
  • Design a multiresolution map that turns over one hundred million points into cached heat maps and detailed pins without overwhelming the browser.

    GoogleFrontend EngineerSystem DesignOnsite
  • This question evaluates leadership, stakeholder management, technical decision‑making, and execution competencies by requesting detailed resume project walkthroughs and responses to leadership hypotheticals.

    GoogleSoftware EngineerBehavioral & LeadershipOnsite
  • Practice troubleshooting intermittent slowness in a multi-tier web application. The solution covers impact scoping, client and network checks, app traces, database and search diagnostics, cache behavior, background jobs, hypothesis testing, mitigation, stakeholder communication, and prevention.

    GoogleProduct ManagerProduct / Decision MakingTechnical Screen
  • A behavioral interview question asking what you do when two people disagree, backed by a concrete example from your work. It tests how you understand both sides, move a disagreement toward evidence and shared criteria, decide or escalate when needed, and keep the working relationship intact.

    GoogleSoftware EngineerBehavioral & LeadershipOnsite

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