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 151–180 of 486 results

  • This question evaluates a candidate's competency in designing large-scale, low-latency real-time recommendation systems, covering feature engineering and feature-store consistency, candidate generation and ranking architectures, cold-start handling, latency versus accuracy trade-offs, monitoring, and operational scalability.

    GoogleMachine Learning EngineerML System DesignOnsite
  • This question tests the ability to design an efficient data structure for time-series aggregation using a sliding window approach with O(1) time complexity per operation.

    GoogleSoftware EngineerCoding & AlgorithmsTechnical Screen
  • This question evaluates relational database design and data engineering competencies—including schema modeling, many-to-many relationships, idempotent ingest, indexing and partitioning, OLTP versus analytics integration, GDPR-compliant deletion strategies, and query formulation—within the Data Manipulation (SQL/Python) domain for a Data Scientist role. It is commonly asked to assess both conceptual understanding and practical application of scalable data architectures, performance tuning, and compliance trade-offs, focusing on the ability to reason about schema choices, read/write optimization, and analytics integration without implementation details.

    GoogleData ScientistData Manipulation (SQL/Python)Technical Screen
  • This question tests your ability to design a waitlist system using efficient data structures to handle insertions, removals, and lookup operations.

    GoogleSoftware EngineerSoftware Engineering FundamentalsOnsite
  • This problem tests your ability to design a dynamic waitlist using efficient data structures to support logarithmic time complexity for insertions, deletions, and ranking operations.

    GoogleSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • Design the watch-next recommendations shown while a user watches a video, from objectives and candidate generation to ranking, serving and evaluation. The interview probes modeling depth: exact loss functions for retrieval and multi-task ranking, the gradient at the output logit, and the update rules of the optimizers used to train each model.

    GoogleMachine Learning EngineerML System DesignOnsite
  • This question tests the ability to design a statistically sound A/B test for a search ranking algorithm, focusing on metric selection, hypothesis formulation, and common pitfalls in experimentation.

    GoogleData ScientistAnalytics & ExperimentationHR Screen
  • Design an enterprise search agent that provides grounded, cited answers over internal knowledge repositories while strictly enforcing access control lists (ACLs) and handling prompt injection.

    GoogleSoftware EngineerML System DesignTechnical Screen
  • Design an embeddable chat-agent widget with resumable streaming, virtualized history, safe caching, accessibility, and meaningful metrics.

    GoogleFrontend EngineerSystem DesignOnsite
  • This problem tests your ability to handle overlapping intervals and state tracking using a sweep-line algorithm combined with a mapping structure.

    GoogleSoftware EngineerSoftware Engineering FundamentalsOnsite
  • Prepare for a Google system design interview about design an enterprise ai adoption agent for a global company. This question focuses on requirements, architecture, trade-offs, reliability, and follow-up discussion areas.

    GoogleSoftware EngineerSystem DesignOnsite
  • Design an LLM-powered agent for a manufacturing business that checks production progress, opens work orders and gives customers price quotes. Probes tool design for reads and writes, how to stop the agent from inventing statuses or prices, and how to enforce user permissions outside the model.

    GoogleSoftware EngineerML System DesignTechnical Screen
  • Design the client side of an app where users keep editing data offline, store every edit locally, and sync with the server when the network returns. Covers the local data model and edit queue, a sync protocol that is safe to retry, and detecting and resolving version conflicts when several devices change the same data.

    GoogleSoftware EngineerSystem DesignOnsite
  • This question tests the ability to design a high-throughput, secure, and fault-tolerant distributed system capable of executing untrusted user code in isolated environments.

    GoogleSoftware EngineerSystem DesignOnsite
  • This question tests the ability to design an A/B test for a software upgrade, specifically focusing on handling non-compliance, selection bias, and the identification of causal effects in a real-world product environment.

    GoogleData ScientistAnalytics & ExperimentationTechnical Screen
  • This question tests the ability to design a retrieval system using a priority queue and the implementation of efficient operations to maintain a sorted collection of ad candidates.

    GoogleSoftware EngineerSoftware Engineering FundamentalsOnsite
  • This question evaluates understanding of mutable ordered sequence data structures, marker semantics and invariants, API and data model design, and algorithmic time-complexity trade-offs for insert, delete, and move operations.

    GoogleSoftware EngineerSoftware Engineering FundamentalsOnsite
  • This question evaluates system design skills including architectural modeling of components, scheduling and concurrency control, state-machine design, and fault-tolerance for real-time control systems, and falls under the System Design domain.

    GoogleSoftware EngineerSystem DesignOnsite
  • This question evaluates a candidate's competency in designing end-to-end ML-driven systems that handle large-scale, low-latency OS snapshot ingestion, binary anomaly detection, decisioning and action orchestration with multi-tenant security, auditability, and failure rollback.

    GoogleSoftware EngineerML System DesignTechnical Screen
  • This question evaluates expertise in reliable distributed systems design, including at-least-once delivery semantics, idempotency and deduplication strategies, retry and dead-letter handling, API and message-schema design, ordering and out-of-order handling, and scalability for high-throughput multi-tenant notification platforms.

    GoogleSoftware EngineerSystem DesignTechnical Screen
  • This problem tests your ability to design a memory-efficient data structure for sparse or repetitive vector data and implement an arithmetic operation without fully decompressing the representation.

    GoogleSoftware EngineerCoding & AlgorithmsOnsite
  • This question evaluates system design and storage engineering competencies, including multi-tenant isolation, authentication and authorization models, content-addressable storage and deduplication, reference counting and garbage collection, concurrency control, API surface design, and scaling across nodes using only filesystem primitives.

    GoogleSoftware EngineerSystem DesignTechnical Screen
  • This question evaluates a candidate's expertise in designing distributed storage systems, covering partitioned append-only logs, high-throughput writes and reads, replication, retention, indexing, compaction, leader/follower roles, and recovery mechanisms.

    GoogleSoftware EngineerSystem DesignTechnical Screen
  • This question evaluates a candidate's understanding of distributed transactions, coordination protocols, fault tolerance, consistency, and reliability across microservices and databases.

    GoogleSoftware EngineerSystem DesignTechnical Screen
  • This question evaluates a candidate's competence in designing secure, scalable systems for executing user-supplied code, covering API design, sandboxing and isolation, dependency management, resource limits, scheduling, and streaming proxies for logs/results.

    GoogleSoftware EngineerSystem DesignTechnical Screen
  • Design feedback-driven recommender evaluates ML product requirements, data/labeling, modeling, serving architecture, evaluation, monitoring, and trade-offs in a realistic interview setting. A strong answer states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

    GoogleMachine Learning EngineerML System DesignOnsite
  • This question evaluates a candidate's ability to design scalable, fault-tolerant event ingestion and subscription architectures, covering distributed systems, high-throughput messaging, content-based filtering, multi-tenant isolation, API/webhook design, delivery semantics, backpressure, sharding, security, and operational observability.

    GoogleSoftware EngineerSystem DesignTechnical Screen
  • This interview question evaluates statistical assumptions, formulas, estimation strategy, uncertainty, edge cases, and interpretation in a realistic interview setting. A strong answer for Design human review to estimate model accuracy states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

    GoogleData ScientistStatistics & MathOnsite
  • This question evaluates system design and security competencies—specifically cryptographic key lifecycle management, HSM integration, access control, auditing, multi-tenant isolation, and scalability—within the System Design domain.

    GoogleSoftware EngineerSystem DesignTechnical Screen
  • This question tests the ability to design an end-to-end pipeline for detecting near-duplicate videos at a massive scale, focusing on embedding generation, vector indexing, and trade-offs between precision and recall.

    GoogleMachine Learning EngineerSystem DesignOnsite

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