← Back to Directory

Google interview notes, page 31 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

Apr 2026
Google SWE interview with a multi-part algorithmic problem about simulating infection spread on a 2D grid. The problem kept building on itself across four parts, which was either clever or exhausting depending on how your brain works under pressure.
  • Given a 2D grid where cells can be healthy, infected, recovered, or walls, compute the state of the grid after exactly one step of infection spread. Healthy cells become infected if any orthogonal neighbor is infected; all other cells stay the same. Updates are simultaneous.
  • Extend the single-step simulation to run for k steps, where walls permanently block infection spread and recovered cells are immune. Return the grid after k steps.
  • Add a recovery mechanic: each infected cell tracks how many steps it has been infected. After exactly d steps of infection, the cell recovers permanently. Simulate k steps and return the final grid.
  • Combine all previous rules and add early stopping: halt the simulation as soon as the grid reaches a fixed point where no further changes are possible. A fixed point requires both that no healthy cell is adjacent to an infected cell AND that no infected cells remain. Return the final grid and the actual number of steps taken.

“Pretty clean setup, just scan every cell and check neighbors.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
Google PM interview with a single open-ended product design question about rest. No frills, just one big ambiguous prompt and you're on your own.
  • Design a product to help people feel more rested.

“I spent the first minute just staring at how broad this was.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
Google PM interview with a product sense question that felt deceptively casual but had some real teeth once you got to the KPI part.
  • Name three apps you love, then pick one and imagine you're the CEO. What's the single most important KPI you'd track?

“The first part is easy enough, you just list apps you actually use.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
Product management case question at Google, the burger shop sales decline scenario. Pretty classic root cause analysis framing but I fumbled the structure more than I expected.
  • You own a burger shop and sales have been declining. How do you investigate what's going wrong?

“I went straight to external factors first, which in hindsight was backwards.”

View Post

Google·Software Engineer·Technical Phone Screen

Apr 2026
Google SWE interview with a file processing problem. Pretty straightforward premise but the scale angle is what makes it interesting.
  • You have a very large text file where each line contains a number. How do you find the maximum value in the file?

“My first instinct was to just read everything into memory and call it a day, which is obviously wrong when they say 'very large.' Had to backtrack and think about streaming line by line.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
Google PM interview with one product sense question that sounds deceptively casual but has some real depth to it if you're not careful.
  • Tell me about an app you dislike using. How would you go about improving it?

“I picked an app I genuinely find frustrating which felt smart in the moment, but I spent too long venting about what's wrong with it and not enough time actually structuring a real improvement plan.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
Google PM interview with a product design question built around a hypothetical real-time Street View feature. Pretty open-ended and required covering a lot of ground fast, from user segmentation to privacy risks.
  • Imagine Google Maps' street-level photos updated in real time. What product or major feature would you build on top of that, and how would you think through users, use cases, MVP scope, success metrics, and privacy risks?

“This question is deceptively large.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
Product strategy question at Google, just the one question about whether Facebook should consolidate its messaging apps. Pretty classic case-style prompt but there's more to unpack than it looks.
  • Should Facebook consolidate its various messaging applications into a single unified product?

“I went straight to user segmentation and started listing out the different audiences for each app, which felt right but I never really landed on a clear recommendation.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
Google PM interview with a single accessibility-focused product design question. Pretty open-ended, which sounds nice until you're actually in it and realize there's no obvious right answer to anchor on.
  • Design a product (app or device) that helps visually impaired users navigate public buildings and spaces.

“I started with user segmentation, which felt right, but I spent way too long on it.”

View Post

Google·Data Scientist·Technical Phone Screen

Apr 2026
Google Data Scientist interview with a coding-heavy technical phone screen. The whole thing was basically one meaty array problem taken to its logical extremes, which I did not fully expect going in.
  • Given an integer array and a target value k, find the longest contiguous subarray whose elements sum to exactly k. Return its length and the start/end indices. Break ties by choosing the earliest start index, then the earliest end index.

“Started with the brute force and they let me finish it before asking for something better, which was nice.”

View Post