← Back to Directory

Google interview notes, page 115 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 - Product Sense / Strategy

May 2026
Interviewed for a PM role at Google and got hit with a product opinion question that felt deceptively casual but had some real depth to it if you pushed past the surface.
  • What is a product you genuinely dislike, and what makes it fall short for you?

“I picked something I actually had strong feelings about which helped, but I spent too long on the complaint and not enough on the why underneath it.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

May 2026
Google PM interview, one product design question for YouTube. Pretty open-ended and I felt like I was flailing a bit trying to scope it down.
  • Design a new feature for YouTube.

“I spent way too long on the problem space before picking a user segment.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

May 2026
Google PM interview with a product sense question that sounds casual but has some real depth to it if you're not careful.
  • Name four Google products you like, then pick one and walk through the challenges it might be facing.

“The first part felt like a warmup and I kind of treated it that way, which was a mistake.”

View Post

Google·Product Manager·Onsite - Behavioral / Leadership

May 2026
Interviewed at Google and got hit with a classic execution question about taking something from idea to launch. Not much else to report, pretty standard behavioral round.
  • Walk me through a time you took an idea all the way from conception to launch.

“I had a story ready but halfway through I realized I was spending way too long on the backstory and not enough on what I actually did.”

View Post

Google·Software Engineer·Technical Phone Screen

May 2026
Two coding problems for a Google SWE round, nothing too wild but the second one had a subtle edge case that tripped me up a bit. Pretty standard algorithmic fare overall.
  • Given an integer, determine whether it reads the same forwards and backwards. Negative numbers should return false. Try to solve it without converting to a string.
  • Given a list of intervals in any order, merge all overlapping ones and return the result sorted by start value.

“The no-string constraint is the whole point of this problem.”

View Post

Google·Software Engineer·Technical Phone Screen

May 2026
Google SWE coding question involving log file processing. Pretty algorithmic, required thinking through data structures carefully to get an efficient solution.
  • Given two log files where each record has a timestamp, object ID, and client ID, find all object IDs that appear in both files and are associated with at least two distinct client IDs across those files.

“My first instinct was to just do a nested loop and i had to stop myself.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

May 2026
Product sense question at Google, one question about evaluating a platform change for Instagram's messaging. Pretty open-ended, no obvious right answer, which made it harder than it looked.
  • A PM wants to open up Instagram's messaging system so users can interact with third-party businesses through it. How would you evaluate whether this is a good idea?

“I spent too long on the user side and barely touched the business model angle.”

View Post

Google·Software Engineer·Hiring Manager Screen

May 2026
Interviewed for a bizops role at Google, and the focus was almost entirely on communication skills, specifically how well you can break down technical stuff for non-technical audiences.
  • How do you explain difficult technical concepts to someone without a technical background? Walk me through a specific example.

“I had an answer ready in theory but fumbled when they pushed for a concrete example.”

View Post

Google·Software Engineer·Onsite - Coding / Algorithms

May 2026
Google SWE coding round with a graph connectivity problem that has a twist: edges can be removed, not just added. The UNFRIEND operation is what makes this tricky and pretty much kills any naive Union-Find approach.
  • Given N people and a list of timestamped FRIEND and UNFRIEND events (not necessarily sorted), find the earliest timestamp at which all N people form a single connected component. Return -1 if it never happens.

“My first instinct was Union-Find and I started going down that road before realizing UNFRIEND completely breaks it.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

May 2026
Interviewed at Google for a product role and got hit with a trust and safety design question. Pretty open-ended, which I wasn't fully prepared for.
  • How would you prevent cyberbullying on Reddit?

“I froze a little because I wasn't expecting a third-party platform as the canvas.”

View Post