← Back to Directory

Google interview notes, page 72 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
Google product interview, one question about a hypothetical ML summarization product and how the company could use it. Pretty open-ended, felt more like a strategy brainstorm than a structured case.
  • You have an ML product that can summarize text of any length. How would Google leverage this?

“I went straight to Search and Docs integration, which felt obvious in retrospect.”

View Post

Google·Software Engineer·Onsite - Coding / Algorithms

May 2026
Google SWE coding round with a subarray optimization problem. The question looked deceptively simple at first glance but the key insight took me an embarrassingly long time to land on.
  • Given an integer array, find a contiguous subarray such that the sum of its minimum and maximum values is as large as possible. Return that maximum sum.

“I stared at this for a bit before realizing the answer is just pick any single element and you get 2x that element's value.”

View Post

Google·Software Engineer·Onsite - Behavioral / Leadership

May 2026
Behavioral round at Google for a software engineer role, just the one question about creative problem solving.
  • Tell me about a time you approached a problem in an unconventional or creative way.

“Knew this type of question was coming and still fumbled the setup.”

View Post

Google·Product Manager·Hiring Manager Screen

May 2026
PM interview at Google with a pretty introspective question about what draws you to the role and what frustrates you about it. Short post, one question, not much else to go on.
  • What do you enjoy about product management, and what do you find difficult or frustrating about it?

“I rambled a bit on the 'like' side and then soft-pedaled the 'dislike' part, which I think was a mistake.”

View Post

Google·Software Engineer·Onsite - System Design / Architecture

May 2026
Google system design round for a software engineering role. Single question about designing a job search platform, which sounds straightforward until you actually start pulling on the threads.
  • Design a job search platform similar to Naukri.

“I went straight to the search indexing layer and spent probably too long on it.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

May 2026
Google PM interview with a classic 'day one on the job' growth question about Google Home. Pretty open-ended, which sounds freeing until you're actually sitting there trying to figure out where to even start.
  • It's your first day as a Google PM. How would you grow Google Home sales by 10X?

“I started by trying to segment who's actually buying smart speakers and why, which felt right, but I spent too long on the user breakdown and rushed the actual strategy part.”

View Post

Google·Software Engineer·Technical Phone Screen

May 2026
Google SWE coding round with a string algorithm problem. The question looked approachable at first but the constraint about handling long strings is what makes it actually hard.
  • Given a string, find the longest substring that appears more than once. If there are ties, return the one with the earliest starting position. The string can be very long, so a brute force approach won't cut it.

“The naive O(n^2) solution is obvious but they're clearly fishing for something better.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

May 2026
Google PM interview, one question about diagnosing a usage drop for a competitor product. Pretty open-ended, felt like a case study more than a traditional product question.
  • TikTok is seeing a decline in usage. How would you diagnose what's causing it?

“I went straight into segmenting the drop by user type and surface area, which felt right at first.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

May 2026
Got a product design question for Google, pretty open-ended stuff about designing a convenience store for a retirement community. Not a lot of context given upfront, which made it both interesting and a little disorienting.
  • How would you design a convenience store specifically for a retirement home?

“My first instinct was to just list features for elderly people and call it a day, but that felt too shallow so I tried to slow down.”

View Post

Google·Software Engineer·Technical Phone Screen

May 2026
Google SWE interview with a 2D grid problem that looks straightforward until you actually sit down to think about it. The DP angle isn't obvious at first glance.
  • Given a 2D grid of characters where each character represents a color, count the total number of monochromatic squares (submatrices of any size k×k where all cells share the same character).

“My first instinct was brute force: check every possible top-left corner, every possible size.”

View Post