← Back to Directory

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

Apr 2026
Product sense round at Google for a PM role. One question about DoorDash metrics, which sounds straightforward until you're actually sitting there trying to decide what matters most.
  • What are the most important metrics you would track for DoorDash?

“I went straight to GMV and order volume and the interviewer just kind of waited.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
Got a product strategy question at Google that was deceptively open-ended. The kind where you think you know where to start and then realize five minutes in you've been talking in circles.
  • The CEO of YouTube asks you to double total watch time on the platform. How do you approach this?

“I jumped straight into feature ideas and immediately regretted it.”

View Post

Google·Software Engineer·Onsite - Coding / Algorithms

Apr 2026
Google SWE interview that went deep into a cyclic meeting rooms problem, starting from a sweep-line baseline and then scaling it up to millions of intervals. The follow-up discussion on distributed approaches was where things got interesting and a bit uncomfortable.
  • You have a meeting rooms problem on a 24-hour cyclic clock where intervals can wrap past midnight. Find the maximum number of overlapping meetings using a sweep-line approach.
  • Now assume there are millions of meetings. How would you optimize the solution? Walk through bucketed difference arrays, parallelism, streaming, and distributed merging, and how the cyclic boundary affects each.

“Got the basic sweep-line down pretty quickly.”

View Post

Google·Software Engineer·Technical Phone Screen

Apr 2026
Coded for Google SWE and got hit with a classic array manipulation problem. Clean constraint (no division, O(n)) made it trickier than it looks at first glance.
  • Given an integer array, return a new array where each element is the product of all other elements in the original array. You cannot use division, and the solution must run in linear time.

“My first instinct was to just divide the total product by each element, which is the obvious wrong answer given the constraint.”

View Post

Google·Software Engineer·Onsite - Coding / Algorithms

Apr 2026
Google onsite coding round, got hit with a tree traversal problem that looked straightforward but had some subtle state management to it. Not sure how I did.
  • You're given a binary expression tree where internal nodes are logical operators (AND, OR, XOR) and leaf nodes are boolean values. Traverse the leaves left to right; for each one, flip its value, compute the tree's result, then restore the leaf before moving on. Return all the results.

“My first instinct was to just recompute the whole tree from scratch after each flip, which works but I kept second-guessing whether they wanted something smarter.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
Google PM interview, one question about what you'd build with a billion dollars and generative AI. Pretty open-ended, which sounds fun until you're actually sitting there trying to not sound like every other candidate who says 'an AI assistant for X.'
  • If you had $1 billion to spend, what would you build using generative AI?

“The budget framing is a trap you don't realize is a trap.”

View Post

Google·Software Engineer·Onsite - Product Sense / Strategy

Apr 2026
Interviewed for a data analyst role at Google and got a product strategy question that felt more like something you'd see in a PM loop. Not a bad experience but I was not expecting to think this hard about market positioning.
  • Pick a product you use and walk through how you would go about identifying its competitors.

“I picked Google Maps because I figured talking about a Google product would show I'd done my homework.”

View Post

Google·Software Engineer·Technical Phone Screen

Apr 2026
Google SWE interview, one coding question that turned into a slow-motion disaster. The interviewer was patient and kept nudging me toward a solution but I still couldn't get there.
  • Given a definition of 'Perfect Wake Numbers', count how many such numbers exist from 1 to n.

“This was a follow-up to an earlier problem and I just fell apart.”

View Post

Google·Software Engineer·Onsite - Behavioral / Leadership

Apr 2026
Behavioral round at Google for a software engineer role, pretty much one meaty question about conflict and how you handle it. Not a lot of fluff, just dig in and tell a real story.
  • Tell me about a time you disagreed with a teammate, manager, or cross-functional partner. How did you raise your perspective, work toward a resolution, and what came out of it? Also be ready to talk about what you'd change and how you kept the relationship intact.

“This one has a lot of moving parts and I kind of underestimated it.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
Google PM interview with a product sense question about re-engaging a lapsed YouTube TV subscriber who happens to own a bunch of Google hardware. Interesting angle because it's basically a cross-product ecosystem problem disguised as a churn question.
  • A subscriber is paying for YouTube TV but hasn't been using it. They own a smart fridge, a Chromecast, and a Google Nest device. How would you increase their engagement with the platform?

“I spent the first minute or two trying to figure out what kind of problem this actually was.”

View Post