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 421–450 of 486 results

  • Behavioral interview questions on handling conflict: a disagreement with a coworker, a disagreement with another team, and a junior engineer you mentor who does not accept your direction. They test how you listen, use evidence, influence without authority, decide when to escalate, and develop others.

    GoogleSoftware EngineerBehavioral & LeadershipTechnical Screen
  • This question assesses the candidate's ability to maintain professional objectivity, analyze constructive criticism, and implement measurable behavioral changes.

    GoogleSoftware EngineerBehavioral & LeadershipOnsite
  • Return all unique value triples that reach a target using three distinct input positions, with canonical ordering despite duplicate values. Candidates are evaluated on duplicate control, overflow-safe sums, nonmutation, output-sensitive complexity, and careful boundary cases.

    GoogleSoftware EngineerCoding & AlgorithmsOnsite
  • Practice a Google coding interview problem focused on return words matching a typed prefix. The prompt emphasizes edge cases, clean implementation, and verifiable test behavior without revealing the solution.

    GoogleSoftware EngineerCoding & AlgorithmsOnsite
  • Given a binary search tree in level-order form and an inclusive range of values, return every key in the tree that falls inside the range, in ascending order. Tests use of the search tree ordering, unbalanced trees, empty results and inclusive boundary handling.

    GoogleSoftware EngineerCoding & AlgorithmsOnsite
  • This problem evaluates string-processing and filtering skills, focusing on exact prefix matching, case sensitivity, duplicate handling, and edge-case management over arrays of strings. Commonly asked in Coding & Algorithms interviews, it assesses practical implementation ability and understanding of algorithmic complexity at an implementation-level (basic to intermediate).

    GoogleSoftware EngineerCoding & AlgorithmsTechnical Screen
  • Find the lexicographically smallest pair of distinct indices whose array values sum to a target. Success depends on deterministic tie handling, duplicates, missing-result behavior, nonmutation, hash-based performance, and comparison with sorting-based alternatives.

    GoogleSoftware EngineerCoding & AlgorithmsOnsite
  • Design a pipeline that turns a firehose of untrusted app reviews into LLM-written theme digests for internal product teams, with defenses against prompt injection, spam and personal data leakage.

    GoogleSoftware EngineerSystem DesignOnsite
  • Design a recurring job scheduler that selects the highest-priority eligible job and enforces cooldown periods measured by subsequent retrieval invocations.

    GoogleSoftware EngineerCoding & AlgorithmsOnsite
  • Tests binary tree traversal combined with streaming pattern matching (such as the Knuth-Morris-Pratt algorithm) to detect substrings across leaf boundaries without buffering the entire text in memory.

    GoogleSoftware EngineerCoding & AlgorithmsOnsite
  • This question evaluates situational judgment, ethical decision-making, and adherence to data confidentiality and respectful workplace policies relevant to a Data Scientist role.

    GoogleData ScientistBehavioral & LeadershipOnsite
  • A four-question senior-engineer behavioral round covering a project you're proud of, a team conflict, a teammate you misjudged at first, and what you're looking for in your next role — testing ownership at scope, fair conflict handling, and genuine self-awareness.

    GoogleSoftware EngineerBehavioral & LeadershipTechnical Screen
  • Staff-level system design question on building a distributed in-memory cache shared by many backend services. It covers the client API, node memory layout and eviction, key placement and rebalancing, replication and failover, freshness against the database, hot keys, miss storms and cold starts.

    GoogleSoftware EngineerSystem DesignOther
  • Find the smallest distance between occurrences of two given words in a list, then build a class over the word list that answers repeated distance queries and checks whether two words are anagrams. It tests linear-time scanning, precomputation for repeated queries, and correct letter-count comparison.

    GoogleSoftware EngineerSoftware Engineering FundamentalsOnsite
  • Show leadership and teamwork evaluates behavioral evidence, ownership, communication, trade-offs, and measurable outcomes in a realistic interview setting. A strong answer states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

    GoogleSoftware EngineerBehavioral & LeadershipOnsite
  • This question evaluates understanding of randomized algorithms, uniform probability distributions over permutations, in-place array manipulation, and time/space complexity analysis within the Coding & Algorithms domain.

    GoogleSoftware EngineerCoding & AlgorithmsTechnical Screen
  • This question evaluates a candidate's ability to perform simulation-based hypothesis testing by implementing Monte Carlo sampling and computing an empirical two-sided p-value from observed coin-flip counts, emphasizing statistical computation and numerical accuracy.

    GoogleData ScientistCoding & AlgorithmsOnsite
  • This Coding & Algorithms question for a Data Scientist evaluates understanding of randomized algorithms, bit-level representation of real numbers, and probabilistic error and time-complexity analysis, situated at an algorithmic and mathematical abstraction level that requires both conceptual design and quantitative reasoning.

    GoogleData ScientistCoding & AlgorithmsOnsite
  • A Google coding problem that simulates an in-memory file system through a sequence of mkdir, ls, add and read operations, with missing directories created on demand and existing files appended to. It tests tree modeling, path parsing, sorted directory listings and precise operation semantics.

    GoogleSoftware EngineerCoding & AlgorithmsOther
  • This problem tests your ability to manage interval-based resource allocation using a priority queue and a frequency map to track usage statistics.

    GoogleSoftware EngineerCoding & AlgorithmsOnsite
  • This problem tests your ability to manage resources over time using a priority queue and sorting, focusing on handling events and tie-breaking logic for room availability.

    GoogleSoftware EngineerCoding & AlgorithmsTechnical Screen
  • This problem tests your ability to maintain order and perform efficient removals within a sliding window using balanced data structures or heaps.

    GoogleSoftware EngineerCoding & AlgorithmsTechnical Screen
  • Maintain sliding-window means after removing the largest k occurrences, with duplicate-aware rebalancing, exact fractions, and bounded streaming state.

    GoogleSoftware EngineerCoding & AlgorithmsTechnical Screen
  • Solve minimum eating speed and merge intervals for a new graduate phone screen. The solution covers binary search on answer, integer ceiling division, monotonic feasibility, interval sorting, overlap merging, correctness, complexity, and edge cases.

    GoogleSoftware EngineerCoding & AlgorithmsTechnical Screen
  • Implement algorithms for two interview tasks: minimal directory deletion in a hierarchical filesystem using tree traversal, and valid flower placement on a grid using constraint satisfaction.

    GoogleSoftware EngineerCoding & AlgorithmsOnsite
  • This question evaluates skills in grid-based graph traversal and connected-component detection for the island counting task, and combinatorial counting with multiset considerations for the target-word formation task.

    GoogleSoftware EngineerCoding & AlgorithmsTechnical Screen
  • This multi-part question evaluates algorithmic problem-solving across selection algorithms, graph/tree traversal, and string processing, testing competencies such as Quickselect behavior and pivot reasoning, computation of node distances in a tree, and prefix-based substring counting.

    GoogleSoftware EngineerCoding & AlgorithmsOnsite
  • Design an online resource scheduler that dynamically allocates compute rooms to incoming streaming sessions and tracks the top-k most active streams by cumulative duration.

    GoogleSoftware EngineerCoding & AlgorithmsTechnical Screen
  • This problem tests your ability to combine graph traversal (Dijkstra's) with greedy interval scheduling to optimize fleet distribution across multiple locations.

    GoogleSoftware EngineerCoding & AlgorithmsOnsite
  • Tests multi-paradigm algorithmic fluency across dynamic programming with auxiliary states, greedy interval coverage, and monotonic deque optimization for bounded subarrays.

    GoogleSoftware EngineerCoding & AlgorithmsOnsite

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