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 301–330 of 486 results

  • A product manager system design prompt about using retrieval-augmented generation to help moderate misinformation on a platform at large scale. It tests pipeline design from claim detection through evidence retrieval to human review, evidence freshness, precision and recall trade-offs, success metrics, and risks such as prompt injection.

    GoogleProduct ManagerSystem DesignOther
  • Tests ethical decision-making, conflict-of-interest disclosure, data confidentiality adherence, and principled stakeholder communication under delivery pressure.

    GoogleSoftware EngineerBehavioral & LeadershipHR Screen
  • This question evaluates interpersonal communication, conflict resolution, and leadership competencies, focusing on handling underperformance and interpersonal tension within a technical team.

    GoogleSoftware EngineerBehavioral & LeadershipTechnical Screen
  • This prompt evaluates behavioral leadership competencies—conflict resolution, stakeholder management, prioritization under tight deadlines, ownership and accountability, and the ability to synthesize differing perspectives—within a software engineering context.

    GoogleSoftware EngineerBehavioral & LeadershipTechnical Screen
  • This interview question evaluates behavioral evidence, ownership, communication, trade-offs, and measurable outcomes in a realistic interview setting. A strong answer for Handle overwhelmed team as senior manager states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

    GoogleSoftware EngineerBehavioral & LeadershipOnsite
  • This question evaluates teamwork, prioritization, conflict resolution, mentoring, feedback delivery, and time-management competencies for a software engineering role in the Behavioral & Leadership category.

    GoogleSoftware EngineerBehavioral & LeadershipTechnical Screen
  • This question evaluates leadership competencies such as cross-team communication, stakeholder alignment, prioritization, and conflict-resolution skills.

    GoogleSoftware EngineerBehavioral & LeadershipTechnical Screen
  • A two-part behavioral interview asking how you would handle a colleague taking credit for your work, and how you manage your time and coordinate with others when juggling several tasks with different priorities. It evaluates conflict resolution, communication and prioritization judgment.

    GoogleSoftware EngineerBehavioral & LeadershipOnsite
  • Practice answering a behavioral prompt about clarifying unclear names or questions in remote meetings. The guide gives respectful exact language, proactive meeting setup, paraphrase-and-confirm techniques, chat and caption usage, large-meeting flow control, and recovery when you answered the wrong question.

    GoogleProduct ManagerBehavioral & LeadershipTechnical Screen
  • This question evaluates a candidate's competency in handling ambiguous requirements, focusing on requirement elicitation, clarification, incremental delivery, documentation, and risk management within a family-tree prompt.

    GoogleSoftware EngineerBehavioral & LeadershipTechnical Screen
  • Practice designing a historical FX-rate service for 10k QPS with APIs, data models, precision, versioned corrections, hot and cold storage, caching, consistency, snapshot semantics, scalability, multi-region reliability, monitoring, and operations.

    GoogleProduct ManagerProduct / Decision MakingOnsite
  • A role-related question for software engineers: if your feature detects smiling faces in Google Photos, how would you verify that the detection is correct? It tests defining ground truth, choosing evaluation metrics and thresholds, covering hard cases and demographic slices, and validating the feature before and after launch.

    GoogleSoftware EngineerMachine LearningTechnical Screen
  • A behavioral question asks how you handle a project whose scope is unclear or highly ambiguous. It tests how you clarify goals with stakeholders, decide which unknowns to resolve first, make progress on documented assumptions, communicate changes, and back your approach with a real example.

    GoogleSoftware EngineerBehavioral & LeadershipTechnical Screen
  • A behavioral interview question asking how you prioritize when you have a large amount of work, illustrated with a real example. It tests the criteria you use to order work, how you handle dependencies and conflicting requests, what you choose to defer, and how you communicate those trade-offs.

    GoogleSoftware EngineerBehavioral & LeadershipOnsite
  • This question evaluates a candidate's conflict resolution, communication, teamwork, leadership, ethical judgment, influence, and adaptability skills in a software engineering context.

    GoogleSoftware EngineerBehavioral & LeadershipOnsite
  • This question evaluates collaboration, ownership, conflict management, influence without authority, leadership/mentorship, and feedback skills within the Behavioral & Leadership domain for software engineering roles, emphasizing practical application through concrete examples rather than purely conceptual understanding.

    GoogleSoftware EngineerBehavioral & LeadershipTechnical Screen
  • This question evaluates interpersonal and leadership competencies, including communication, conflict resolution, de-escalation, stakeholder alignment, and maintaining team collaboration.

    GoogleSoftware EngineerBehavioral & LeadershipTechnical Screen
  • Answer the coding interview follow-up "what if the input is huge?" Covers memory checks, streaming, chunking, external sort, approximate structures, distributed processing, and engineering tradeoffs.

    GoogleSoftware EngineerSoftware Engineering FundamentalsOnsite
  • Evaluates knowledge of DNS, HTTP/HTTPS request routing, TLS certificate management, and operational/security trade-offs when hosting multiple domains on a single public IP. Commonly asked to probe architectural reasoning and practical deployment trade-offs in the System Design domain at an architectural/operational level of abstraction.

    GoogleSoftware EngineerSystem DesignTechnical Screen
  • This question evaluates leadership and team-management competencies—including delegation, prioritization, conflict resolution, and feedback communication—within a software engineering context and the Behavioral & Leadership interview category.

    GoogleSoftware EngineerBehavioral & LeadershipTechnical Screen
  • Evaluates proficiency with propensity score matching and broader causal inference concepts for observational treatment effect estimation, including identification assumptions, propensity score estimation and covariate selection, matching algorithms and common support, balance diagnostics, choice of estimand (ATE vs ATT) and uncertainty quantification, plus sensitivity checks and alternative methods. Common in Analytics & Experimentation interviews for Data Scientist roles because it probes understanding of confounding and identification in nonrandomized settings and requires intermediate-to-advanced applied statistics reasoning about methodological trade-offs.

    GoogleData ScientistAnalytics & ExperimentationOnsite
  • Evaluates predictive-model audit skills across month encoding, feature scaling, and imbalanced classification. Strong answers fix cyclical seasonality, standardize where needed, and adjust losses or thresholds for recall.

    GoogleData ScientistMachine LearningTechnical Screen
  • This question evaluates understanding of state management, undo/redo semantics, batched transactional edits, and memory-efficient change history representation for map-based document layers.

    GoogleSoftware EngineerCoding & AlgorithmsTechnical Screen
  • This question evaluates string processing, checksum computation with modular indexing, parsing of dependency data, and business-logic evaluation for feature rollouts, including conditional eligibility checks and dependency resolution.

    GoogleSoftware EngineerCoding & AlgorithmsOnline Assessment
  • This question evaluates string processing, pattern matching, greedy algorithm reasoning, and data structure design for efficient longest-prefix token replacement, and is categorized under Coding & Algorithms.

    GoogleSoftware EngineerCoding & AlgorithmsTechnical Screen
  • This problem tests object-oriented design and grid traversal logic by requiring the implementation of a generic N-player Tic-Tac-Toe game where win conditions are evaluated based on a specific run-length.

    GoogleSoftware EngineerCoding & AlgorithmsOnsite
  • This question evaluates proficiency in probability and numerical methods, focusing on sampling from truncated distributions and analytical properties of estimators under various loss functions.

    GoogleData ScientistCoding & AlgorithmsTechnical Screen
  • Implement trie insertion and exact-word search for up to a million total characters, distinguishing terminal words from mere prefixes and returning search results in operation order.

    GoogleSoftware EngineerCoding & AlgorithmsTechnical Screen
  • This problem tests your understanding of iterator protocols, generator patterns, and memory-efficient data buffering for multi-consumer streams.

    GoogleSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • Design and implement a locker bank management system that assigns the lowest available locker index, handles invalid store and pickup operations, releases lockers immediately, and tracks the last package successfully stored in each locker.

    GoogleSoftware EngineerCoding & AlgorithmsTechnical 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