← Back to Directory

Google interview notes, page 19 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·Onsite - Coding / Algorithms

Apr 2026
Google SWE coding round, one problem the whole session. Linked list ancestry traversal, which sounds straightforward until you're actually in it and second-guessing your pointer logic.
  • Given two singly-linked chains representing ancestor paths (each node has an id and a parent pointer), determine whether the two chains share any common node.

“The core insight is just traversal and a hash set, collect all nodes from one chain then walk the other and check for membership.”

View Post

Google·Software Engineer·Technical Phone Screen

Apr 2026
Google SWE technical phone screen with a board game optimization problem. The question looked deceptively simple at first glance but the constraint interactions made it way harder than expected.
  • You have a 1D board where each cell is empty, holds a token, or holds a coin. Each turn you pick one token and move it exactly 3 cells to the right. Landing on a coin collects it (each coin collected at most once), landing on another token is illegal, landing on an empty cell does nothing. You can play as many turns as you want until no token can legally move. What's the maximum number of coins you can collect?

“Spent the first few minutes just trying to restate the problem back correctly because the three-state cell thing plus the blocking rule felt like a lot to hold at once.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
Interviewed for a PM role at Google and got hit with a YouTube recommendation question. Pretty open-ended, which sounds fun until you're actually sitting there trying to figure out where to start.
  • How would you improve YouTube's recommendation algorithm?

“I went straight to user satisfaction metrics and started talking about watch time, which I think was the wrong instinct.”

View Post

Google·Data Analyst·Technical Phone Screen

Apr 2026
Google data interview, one question about outliers. Short and to the point, nothing too crazy but I definitely could have structured my answer better.
  • What are outliers, and how do you detect and handle them?

“Fumbled the detection part a bit.”

View Post

Google·Software Engineer·Onsite - Multi Round

Apr 2026
Four months into the Google Data Center Technician 3 process and I'm still not done. Multiple no-shows, weeks of silence after being told I passed, watching people who interviewed after me start their jobs, and now they want me to redo a hardware interview because the original interviewer didn't ask enough questions. Not my fault, but somehow my problem.
  • Basic Linux commands and directory structure: what are some fundamental commands you use and how do you navigate the filesystem?
  • Hardware fundamentals for a data center environment: what do you know about the physical components and how they're managed?

“Was told ahead of time it wouldn't be heavily Linux focused, so I didn't go deep on prep there.”

View Post

Google·Software Engineer·Onsite - Behavioral / Leadership

Apr 2026
Behavioral round at Google for a software engineering role. One question, but it had some real teeth to it.
  • Describe a situation where you were asked to do something you considered unreasonable, like an impossible deadline, a pointless feature, or being pressured to skip a process. How did you decide it was actually unreasonable, push back on it, suggest something different, and still keep the relationship intact?

“This one is sneaky because the obvious instinct is to just tell a story where you heroically said no and everyone thanked you later.”

View Post

Google·Machine Learning Engineer·Technical Phone Screen

Apr 2026
Google ML engineer interview with a question that sounds easy but actually trips you up if you haven't thought carefully about how to talk to non-technical people.
  • How would you explain Deep Learning to someone with no technical background?

“I went straight into neurons and layers and immediately saw the glazed-over expression forming.”

View Post

Google·Software Engineer·Hiring Manager Screen

Apr 2026
Interviewed for a business analyst role at Google, got a case-style question about diagnosing a marketing campaign that missed its targets. Pretty standard for this type of role but it still tripped me up a bit.
  • A marketing campaign underperformed against its goals. Walk me through how you'd investigate and respond.

“I went straight to metrics without really scoping the problem first, which I think was the wrong move.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
Google PM interview focused on an internal product design problem, specifically reimagining the on-campus bike system. Pretty niche prompt but actually a decent test of whether you can think about real user needs versus just feature-dumping.
  • You're the PM for Google's on-campus bike system. What user needs would you focus on, and how would those translate into design decisions?

“I went straight to segmenting users by commute patterns, which felt right, but I spent too long on the obvious stuff like availability and bike condition before getting to anything interesting.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
Google PM interview with a product strategy question about Hangouts. One question, product-heavy, the kind where they want you to think like you already own the thing.
  • You're the PM for Hangouts right after its 2013 launch. Reviews are mixed and the average rating is sitting at 3 stars. What do you do next?

“This one tripped me up because I jumped straight into fixes before actually diagnosing what was driving the bad reviews.”

View Post