← Back to Directory

Google interview notes, page 121 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·Product Manager·Onsite - System Design / Architecture

May 2026
Google PM interview with a system design question that was way more technical than I expected for a product role. One question, but it had a lot of layers.
  • How would you design the architecture for Google Maps so that it loads in under 100ms?

“I spent the first minute just staring at this like wait, am I being asked to do a system design interview or a PM interview.”

View Post

Google·Software Engineer·Take-home Assignment

May 2026
Got a product thinking exercise for a Google bizops role, framed around Udemy's course platform. One question, but it had enough moving parts to keep me busy for a while.
  • You're on the Udemy product team. Write 2 to 3 agile user stories for a feature that lets learners submit and watch short videos (under 2 minutes) within courses.

“I spent way too long debating whether to write 2 or 3 stories.”

View Post

Google·Software Engineer·Technical Phone Screen

May 2026
Google SWE coding round, one problem about scheduling requests across servers. Pretty clean setup but the follow-up complexity caught me a bit flat-footed.
  • Given a list of server response times, determine the total time needed to process n requests across those servers.

“The core setup is basically a scheduling problem and I went straight to a min-heap because that felt right.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

May 2026
Google PM interview with a product sense question about Google TV. The question was deceptively meaty and I don't think I handled the ambiguity as well as I should have.
  • Google TV gets great coverage from tech reviewers, but customer reviews are deeply polarized: 40% give it 1 star and 40% give it 5 stars. What would you do?

“I went straight to 'let's segment the 1-star users' which felt right but I skipped over something important: the bimodal distribution itself is the signal.”

View Post

Google·Software Engineer·Onsite - Behavioral / Leadership

May 2026
Behavioral round at Google for a SWE role, just the one question but it took up most of the time.
  • Tell me about a time you had to convince a team that disagreed with your approach.

“I had a story ready but partway through I realized it made me sound more stubborn than persuasive.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

May 2026
Interviewed at Google for a product strategy role, got hit with a market entry question about modular phones. Pretty short on details from my end but I'll share what I remember.
  • Should Apple enter the modular phone market?

“I fumbled the setup a bit because I started talking about Apple's brand positioning before actually defining what modular even means in this context.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

May 2026
Google PM interview, got hit with an accessibility-focused product design question. Pretty open-ended and I spent a lot of time second-guessing whether I was going deep enough on the user empathy side versus the technical constraints.
  • How would you design an ATM specifically for blind users?

“I jumped straight into listing features and had to pull myself back.”

View Post

Google·Software Engineer·Onsite - System Design / Architecture

May 2026
Google system design screen for a software engineering role. Just one question but it had a lot of surface area and I don't think I covered it well enough.
  • Design a system that maps IP address ranges to geographic region labels.

“I started with a basic trie structure for prefix matching and that was fine, but I got stuck when they pushed on scale.”

View Post

Google·Software Engineer·Onsite - Coding / Algorithms

May 2026
Google SWE coding round, one algorithmic problem about grouping numbers by shared digits. Pretty clean problem on the surface but the edge cases tripped me up a bit.
  • Given a list of two-digit numbers, find the maximum subset where every element shares at least one digit with at least one other element in the subset.

“My first instinct was union-find but I second-guessed myself and started rambling about graphs.”

View Post

Google·Technical Program Manager·Onsite - Behavioral / Leadership

Jun 2026
TPM interview at Google with a behavioral question about making decisions under uncertainty. Pretty standard stuff but the question has some teeth if you're not prepared for it.
  • Describe a situation where you had to make an important decision without having all the data you needed.

“I fumbled this a bit because my first instinct was to talk about a time I got more data before deciding, which kind of misses the point.”

View Post