← Back to Directory

Google interview notes, page 88 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·Online Assessment (OA)

May 2026
Google SWE coding problem involving string manipulation and greedy movement logic. Pretty niche problem type, not your typical graph or DP warmup.
  • Given a string of 'T' and 'C' characters, a 'T' can move up to three positions to the right but cannot jump over another 'T'. Any 'C' characters it passes through are collected. Find the maximum number of 'C's that can be collected.

“Took me a bit to realize this isn't just a greedy scan.”

View Post

Google·Software Engineer·Technical Phone Screen

May 2026
Google SWE interview with a pretty gnarly computational geometry question. One round, one problem, lots of follow-ups that kept branching in directions I didn't fully anticipate.
  • You have a 2D grid with n non-overlapping axis-aligned square cakes, each with a real-valued top-left corner and an integer side length. Design an algorithm to find a horizontal line y* such that the total cake area strictly above the line equals the total area strictly below it. Walk through the search interval, prove a solution exists, prove monotonicity, give time and space complexity in terms of n and precision epsilon, and discuss numerical stability and stopping criteria for floating-point coordinates. If multiple solutions exist, explain how you'd return one. Then extend your approach to handle (a) overlapping squares and (b) axis-aligned rectangles instead of squares.

“This one took me a minute to even parse.”

View Post

Google·Software Engineer·Technical Phone Screen

May 2026
Google SWE coding round, one problem, tree stuff. The question was harder than it looked and I definitely underestimated how much graph theory I'd need to actually nail it cleanly.
  • Given an undirected connected tree with n nodes (labeled 0 to n-1) and n-1 edges, return an array where each element is the sum of distances from that node to every other node in the tree. An O(n) solution is expected.

“I knew brute force was wrong the second I wrote it out.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

May 2026
Google PM product case focused on designing a connection product from scratch. Structured prompt with a lot of moving parts: segmentation, MVP scoping, metrics, risks, and iteration planning all in one go.
  • Design a product that helps users connect with people they want to know, like mentors, collaborators, or peers. Walk through your target user, the core problem, what you'd build first, and how you'd measure success.
  • Which user segment would you deliberately leave out of the first version, and what's your reasoning?
  • What's the riskiest assumption baked into your solution, and how would you test it without spending a lot?
  • If the business priority shifted from user acquisition to retention, how would your product design change?
  • What guardrail metric would cause you to stop or roll back the launch entirely?
  • How would you handle abuse, low-quality connections, or users gaming the matching system?
  • What would you build in version two, assuming the MVP showed positive results?

“Big open-ended one.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

May 2026
PM interview at Google, one question about YouTube metrics. Short and focused, nothing too wild, but these deceptively open-ended questions have a way of going sideways fast.
  • If you were the PM for YouTube, what metrics would you prioritize and why?

“I went straight for engagement metrics like watch time and DAU, which felt right, but I didn't spend enough time segmenting by user type or thinking about creator-side health.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

May 2026
Google PM interview with a metrics-heavy scenario question about a struggling internal BI tool. Pretty much one question the whole time, but it went deep fast.
  • You're the PM for a business intelligence system with an NPS of 25%. How do you get it to 75%?

“I jumped straight into diagnosing the NPS gap, which felt right, but I spent too long on the research phase and the interviewer kept nudging me toward actual solutions.”

View Post

Google·Product Manager·Technical Phone Screen

May 2026
Got a classic estimation question at Google, the kind where there's no right answer but you can absolutely give a wrong one. Short round, one question, left feeling like I either nailed the structure or completely missed what they were probing for.
  • Estimate the total time wasted in meetings across the US each year.

“My first instinct was to just start multiplying numbers, which is exactly the wrong move.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

May 2026
Google PM interview, got hit with a product ideation question that sounds breezy until you're actually sitting there trying to say something that isn't obvious.
  • What product should Google build next?

“I went in thinking I had a good answer prepped and then completely second-guessed myself mid-sentence.”

View Post

Google·Software Engineer·Onsite - Behavioral / Leadership

May 2026
Behavioral round at Google for a software engineer role. Just one question but it took the whole session.
  • How do you support a peer who isn't meeting expectations?

“I went straight into a story about giving feedback, which felt okay in the moment, but I think I undersold the part about actually following through with the person over time.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

May 2026
Google PM interview with a classic data-vs-intuition tension question. One round, product strategy focus, left me second-guessing my answer the whole ride home.
  • You've proposed changing Uber's driver incentive structure, but the data suggests this could reduce driver supply. How do you move forward?

“This one stung a little because I started too confident.”

View Post