← Back to Directory

Google interview notes, page 84 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 - Behavioral / Leadership

May 2026
Behavioral round at Google for a software engineer role, just the one conflict question as far as I can tell. Pretty standard stuff but it still made me sweat a little.
  • Tell me about a time you had a conflict at work with a peer, manager, or cross-functional partner. What was the disagreement, how did you handle it, and what happened in the end?

“I had a story ready but mid-answer I started second-guessing whether my example was too low-stakes.”

View Post

Google·Software Engineer·Onsite - Product Sense / Strategy

May 2026
Interviewed for a bizops role at Google and got hit with a strategy question about Android pretty early on. Not a lot of context to go on from what I remember.
  • Why is Android strategically important to Google?

“I knew this was coming in some form but still fumbled the structure a bit.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

May 2026
Google PM interview focused on predicting user app deletion. Single product analytics question, pretty open-ended, not a lot of scaffolding given.
  • How would you predict whether a user is about to delete an app?

“I went straight to behavioral signals like session frequency dropping or push notification opt-outs, which felt right, but I didn't spend enough time on the modeling side or how you'd actually act on the prediction once you had it.”

View Post

Google·Software Engineer·Onsite - System Design / Architecture

May 2026
System design round at Google focused entirely on distributed transactions, which sounds manageable until you realize they want you to compare three different coordination patterns and reason through failure modes in real time. Tough session, lots of follow-ups.
  • Design a distributed transactions protocol that coordinates updates across multiple services or databases. Walk through two-phase commit, three-phase commit, and the Saga pattern, including message flows, failure handling, idempotency, timeouts, and exactly-once vs at-least-once delivery guarantees.

“Started with 2PC because it felt safe, but the interviewer kept pushing on the coordinator failure scenario and I fumbled it.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

May 2026
Google product design interview, one question about designing an assistive device. Pretty open-ended, which I wasn't fully prepared for.
  • Design an alarm clock for blind people.

“I jumped straight into features without stopping to think about what a blind user actually struggles with in the morning.”

View Post

Google·Software Engineer·Technical Phone Screen

May 2026
Google SWE interview with a graph traversal problem involving horse pedigrees. Basically a DAG ancestry question dressed up in a fun theme, but don't let the theme fool you into thinking it's easy.
  • Given a set of parent-child relationships between horses and two horse identifiers, determine whether the two horses are biologically related. Two horses count as related if one is an ancestor of the other, or if they share any common ancestor.

“The horse theme threw me off for a second but once I drew it out it's just a DAG reachability problem.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

May 2026
Google PM interview, one question about accessible product design. Pretty open-ended and I wasn't sure how structured my answer needed to be.
  • How would you design a fire alarm system specifically for people who are deaf or hard of hearing?

“I jumped straight to strobe lights and kind of stalled there for a bit.”

View Post

Google·Software Engineer·Onsite - Product Sense / Strategy

May 2026
Google product design interview with a single open-ended prompt about self-driving cars. Not a lot of context given upfront, which made it feel pretty wide open in a slightly uncomfortable way.
  • Design a new feature for self-driving cars.

“I spent the first minute just trying to figure out what angle to take.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

May 2026
Google PM interview, one question about building a product for an underserved demographic. Pretty short session from what I can tell, felt more like a product sense screen than a full loop.
  • How would you persuade leadership to invest in building a smartwatch designed for elderly users?

“My first instinct was to jump straight into market size numbers, which in hindsight felt thin.”

View Post

Google·Software Engineer·Onsite - Behavioral / Leadership

May 2026
Three behavioral questions at Google, all structured around situation-action-outcome. Nothing too surprising but the bug one caught me a little flat-footed.
  • Tell me about a project you led and what made it challenging.
  • Describe a time you helped a new teammate get up to speed on your team.
  • You find a bug right before a delivery deadline and there's no time to fix it. What do you do? Walk through a specific situation.

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

View Post