← Back to Directory

Google interview notes, page 171 of 215

FAANG / Big Tech

Most of these Google write-ups come from Software Engineers (1,167), then Product Managers (686) and Data Scientists (125). The most reported rounds are the product sense round (667), the technical phone screen (660), the behavioral / leadership round (252) and the onsite coding round (214).

2146 interview notes · updated Oct 2026

Google·Software Engineer·Onsite - Coding / Algorithms

Jun 2026
Google SWE interview that hit a DP matrix problem, apparently showing up in both intern and new grad rounds. Pretty focused on one core pattern but the devil was in the details.
  • Given an m x n grid of colored cells, count all square sub-grids where every cell is the same color.

“The classic all-ones squares DP problem but generalized to multiple colors.”

View Post

Google·Software Engineer·Onsite - Cross-functional / Panel

Jun 2026
Went through a research talk round at Google for a Research Scientist position. You pick one of your major works, present for up to an hour, and then the room basically interrogates you on every decision you made. Intense but kind of fun if you know your stuff cold.
  • Walk the audience through a major research work of yours, covering the motivation, your approach, key results, and where the work falls short.
  • Why did you make the specific design choices you did in this work, and what alternatives did you consider?
  • What are the natural follow-up directions from this research, and which would you prioritize?

“This is the whole format, not just one question.”

View Post

Google·Data Scientist·Technical Phone Screen

Jun 2026
Google data scientist technical screen, one meaty probability/algorithms question that took up most of the time. Felt like a math exam more than a coding interview.
  • You have a function rand_bit() that returns 0 or 1 with equal probability, each call independent. How would you use it to generate a random number approximately uniformly distributed on [0, 1)? Walk through a simple algorithm, explain how the approximation error relates to the number of bits used, and analyze the time complexity in terms of rand_bit() calls.

“The core idea clicked pretty fast for me: just treat the bits as a binary fraction, so bit 1 is worth 1/2, bit 2 is 1/4, and so on.”

View Post

Google·Software Engineer·Onsite - System Design / Architecture

Jun 2026
System design round at Google for a software engineer role. The whole thing was basically one big distributed systems question about building a global metrics platform, and it went deep fast.
  • Design a metrics collection system that ingests high-volume counters, gauges, and histograms from services across multiple global data centers, stores them, and serves dashboards and alerts with low query latency.
  • How would you handle cross-region replication and federation for metric data, and what are the consistency trade-offs when querying across regions?
  • How would you approach downsampling or sampling of metric data to manage storage costs and query performance at scale?

“I started with the write path since the throughput constraint was the obvious anchor.”

View Post

Google·Software Engineer·Onsite - Behavioral / Leadership

Jun 2026
Behavioral screen for a software engineer role at Google. Just the one question but it took up most of the conversation, they kept pushing for more detail.
  • Tell me about a time you worked in an environment where things were constantly changing.

“I had an example ready but it was maybe too safe.”

View Post

Google·Software Engineer·Hiring Manager Screen

Jun 2026
Interviewed for a sales rep role at Google, basically one question that felt like the whole thing hinged on it.
  • Why should we hire you for this role?

“I rambled.”

View Post

Google·Software Engineer·Technical Phone Screen

Jun 2026
Pretty standard Google coding round. One question, not too brutal, and the interviewer was a relaxed older guy which made the whole thing less stressful than I expected.
  • Design a class that handles range queries. Given a list of ranges like [1,3] and [50,100], implement a method that returns which range a given integer falls into.

“Binary search problem once you see it clearly.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
Google PM interview, two product sense questions back to back. Pretty standard stuff but the follow-up on improvement caught me a little flat-footed.
  • What is your favorite product and why?
  • How would you improve that product?

“I had an answer ready but it came out more like a fan rant than a structured response.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
Got a product design question for a Google PM role, focused on YouTube specifically. Pretty open-ended, which sounds fun until you're actually in it and realize you have to pick a direction fast.
  • How would you design an educational product for YouTube?

“The scope here is massive and I think I wasted the first few minutes trying to cover too much ground.”

View Post

Google·Software Engineer·Technical Phone Screen

Jun 2026
Google coding interview with a single pattern matching problem. Short on details but the core question is a classic.
  • Given a pattern and a string, determine whether the string matches the pattern.

“Classic problem that looks easy until you start coding it.”

View Post