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 91–120 of 486 results

  • Decide string transform with directional tokens and walls evaluates algorithm design, data structures, correctness, complexity, edge cases, and implementation details 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 EngineerCoding & AlgorithmsTechnical Screen
  • This question tests the ability to handle nested structures using recursion or a stack-based approach to expand string patterns based on repetition factors.

    GoogleSoftware EngineerCoding & AlgorithmsOnsite
  • Design both a batch algorithm and a streaming processor to deduplicate and chronologically order log records under different resolution policies, accounting for out-of-order delivery, late data, and bounded memory.

    GoogleSoftware EngineerSoftware Engineering FundamentalsOnsite
  • This question evaluates proficiency in SQL data manipulation and analytical querying—specifically deduplication using idempotency keys, window functions/CTEs for ranking, distinct aggregation by date, timestamp tie-breaking, and awareness of indexing and scalability trade-offs in large tables; the domain is Data Manipulation (SQL/Python).

    GoogleData ScientistData Manipulation (SQL/Python)Technical Screen
  • This question assesses a candidate's ability to articulate the engineering rationale behind technical decisions, balancing trade-offs against project constraints and evolving requirements.

    GoogleSoftware EngineerBehavioral & LeadershipTechnical Screen
  • A Google data scientist analytics screen: propose actionable Gmail user segments from behavioral metadata, validate their stability and separability over eight weeks, design targeted interventions with metrics and guardrails, and run a privacy-aware experiment to measure per-segment lift. Covers segmentation axes, validation metrics, k-anonymity and differential privacy, CUPED, and RICE roadmap prioritization.

    GoogleData ScientistAnalytics & ExperimentationTechnical Screen
  • This question evaluates leadership in data ambiguity, assessing competencies in diagnosing underperforming metrics or models, articulating quantified trade-offs, influencing cross-functional stakeholders with data and experiments, and designing operational safeguards and accountability mechanisms.

    GoogleData ScientistBehavioral & LeadershipOnsite
  • This question evaluates a candidate's stakeholder communication and influence using data, specifically assessing the ability to present analysis to non-technical partners, manage pushback, make trade-offs, and demonstrate measurable outcomes in a cross-functional decision context for a Data Scientist role.

    GoogleData ScientistBehavioral & LeadershipTechnical Screen
  • Tests directed graph modeling, cycle detection, and Kahn's algorithm using a min-heap to produce a lexicographically smallest topological sort.

    GoogleSoftware EngineerCoding & AlgorithmsOnsite
  • This question evaluates proficiency in parametric inference and probability theory, specifically maximum likelihood estimation, bias of estimators, and conditioning in univariate and bivariate Normal distributions including constrained estimation of parameters.

    GoogleData ScientistStatistics & MathTechnical Screen
  • This question evaluates interpersonal and leadership competencies—including communication, conflict resolution, teamwork, accountability, problem-solving, and adaptability—by eliciting concrete behavioral examples from past internships or projects.

    GoogleSoftware EngineerBehavioral & LeadershipTechnical Screen
  • Evaluates behavioral interview storytelling for persuading non-data colleagues and resolving workplace challenges. Strong answers use STAR, translate analysis into business terms, handle objections, show collaboration, quantify outcomes, and reflect on lessons learned.

    GoogleData ScientistBehavioral & LeadershipTechnical Screen
  • Evaluates behavioral storytelling for research rigor and cross-functional collaboration in data science. Strong answers explain problem framing, methodology, validation, stakeholder alignment, impact, and limitations.

    GoogleData ScientistBehavioral & LeadershipTechnical Screen
  • This behavioral interview question evaluates a candidate's self-awareness, accountability, and capacity to convert a significant technical or project setback into enduring operational or personal improvements.

    GoogleSoftware EngineerBehavioral & LeadershipOnsite
  • This question evaluates a data scientist's ownership, technical depth in research and modeling, decision-making under constraints, stakeholder management, measurable impact orientation, and reflective learning, and it is categorized under Behavioral & Leadership for Data Scientist roles.

    GoogleData ScientistBehavioral & LeadershipHR Screen
  • This question evaluates leadership, communication, problem‑solving, technical ownership, and the ability to describe trade‑offs, diagnostics, measurable impact, and lessons learned within a software engineering project.

    GoogleSoftware EngineerBehavioral & LeadershipOnsite
  • This question evaluates a candidate's interpersonal conflict-resolution, communication, and leadership competencies within software engineering teams, including stakeholder management and accountability.

    GoogleSoftware EngineerBehavioral & LeadershipOnsite
  • This question evaluates a candidate's behavioral and leadership competencies, including problem-solving, resilience, ownership, communication, and teamwork within academic, internship, or professional technical projects.

    GoogleSoftware EngineerBehavioral & LeadershipOnsite
  • Prepare a Google Data Engineer behavioral answer about building and improving a stakeholder dashboard. The solution covers business goals, KPI design, data validation, BI tooling, anomaly detection, root-cause analysis, feedback handling, and measurable impact.

    GoogleData EngineerBehavioral & LeadershipTechnical Screen
  • This question evaluates interpersonal and leadership competencies such as conflict resolution, accountability, communication, and reflective learning, along with proficiency in structuring responses using the STAR behavioral framework.

    GoogleMachine Learning EngineerBehavioral & LeadershipOnsite
  • This question evaluates a candidate's conflict-resolution and stakeholder-management competencies, including mediation, expectation management, and clear communication when navigating disagreements among peers, managers, and cross-functional partners.

    GoogleSoftware EngineerBehavioral & LeadershipOnsite
  • This question evaluates interpersonal and leadership competencies for a Software Engineer role—specifically conflict resolution, handling ambiguity, process improvement, cross-functional collaboration, and the ability to articulate technical decisions.

    GoogleSoftware EngineerBehavioral & LeadershipOnsite
  • This question evaluates leadership, ownership, prioritization, communication, and adaptability skills within the Behavioral & Leadership domain for a Machine Learning Engineer role.

    GoogleMachine Learning EngineerBehavioral & LeadershipTechnical Screen
  • This question evaluates cross-functional communication, stakeholder management, expectation-setting, and risk escalation competencies in an engineering context.

    GoogleSoftware EngineerBehavioral & LeadershipOnsite
  • This question evaluates teamwork, leadership, problem-solving, communication, and self-awareness by probing examples of helping an underperforming teammate, managing challenging projects, and describing personal achievements.

    GoogleSoftware EngineerBehavioral & LeadershipTechnical Screen
  • This question evaluates leadership, communication, and product-focused machine learning engineering competencies, including end-to-end project ownership, technical decision-making, cross-functional collaboration, metrics-driven impact measurement, and risk management; it is categorized as Behavioral & Leadership within the Machine Learning Engineering domain. It is commonly asked to determine how candidates articulate trade-offs, quantify outcomes, justify technical choices, and demonstrate both conceptual understanding and practical application of ML systems, constraints, and tooling in real-world projects.

    GoogleMachine Learning EngineerBehavioral & LeadershipTechnical Screen
  • Design a distributed storage quota accounting and enforcement service for a cloud drive platform that handles concurrent multi-part uploads, deletions, retries, and usage drift reconciliation.

    GoogleSoftware EngineerSystem DesignTechnical Screen
  • This interview question evaluates metric design, causal reasoning, experiment setup, diagnostics, SQL/statistical checks, and recommendations in a realistic interview setting. A strong answer for Design A/B Test for Google Maps UI Change states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

    GoogleData ScientistAnalytics & ExperimentationOnsite
  • Evaluates experiment design for SaaS subscription pricing and a multivariate sign-up CTA test. Strong answers address pricing-test risks, LTV metrics, factorial design, interaction effects, and guardrails.

    GoogleData ScientistAnalytics & ExperimentationOnsite
  • Evaluates experimentation strategy for diagnosing a simultaneous product usage drop in the U.S. and Mexico. Strong answers identify confounders, design tests or quasi-experiments, control variables, and report causal lift.

    GoogleData ScientistAnalytics & ExperimentationTechnical Screen

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