← Back to Directory

Google interview notes, page 16 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, a follow-up to a grid shortest-path problem with a twist that honestly blindsided me a bit. The base problem felt manageable but the added constraint pushed me into territory I wasn't fully prepared for.
  • Given an N×N grid with land and water cells, a start cell S, an end cell T, and one cell containing a cat, find a path from S to T (moving only on land, 4 directions) that maximizes the minimum Manhattan distance between any cell along the path and the cat's cell.

“I got the base BFS part fine but then just stared at the cat constraint for a bit.”

View Post

Google·Software Engineer·Onsite - System Design / Architecture

Apr 2026
Google system design round for what I'd call a senior mobile/backend role. One question, pretty open-ended, and I spent the first few minutes just trying to figure out where to even start.
  • Design the system architecture for a peer-to-peer chess mobile application.

“I went straight to the backend and started drawing out matchmaking queues before the interviewer even finished nodding.”

View Post

Google·Software Engineer·Onsite - Behavioral / Leadership

Apr 2026
Google behavioral round for a software engineering role. One question, pretty focused, and it was the kind that sounds easy until you're actually sitting there trying to pick the right story.
  • Tell me about a mistake you made, whether a bug, a bad design call, a miscommunication, or a missed deadline. Walk through the situation, your role, the impact, how you caught it and recovered, and specifically what you changed afterward so it wouldn't happen again.

“The 'what did you specifically change' part is where I stumbled.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
Got a market expansion question for Google, specifically about Cuba which threw me a bit since it's not your typical market. Single question, strategy-focused, no coding involved.
  • How would you grow the market share of Google's product portfolio in Cuba?

“Cuba is a weird one because the obvious playbook doesn't apply.”

View Post

Google·Software Engineer·Technical Phone Screen

Apr 2026
Google SWE interview with a graph traversal problem that had a time-constraint twist. The core challenge was modeling flights as directed edges and doing BFS/DFS while respecting departure/arrival ordering, which sounds straightforward until you're actually in the room.
  • Given a list of flights (origin, destination, departure time, arrival time), a start airport, an end airport, and an optional earliest start time, determine if you can travel from start to end using a valid sequence of flights where each flight departs no earlier than the previous flight's arrival time.

“I started with plain BFS and forgot the time constraint for the first few minutes, which was embarrassing.”

View Post

Google·Software Engineer·Onsite - Behavioral / Leadership

Apr 2026
Behavioral round at Google for a software engineering role, just one question but it took up the whole conversation. The focus was on how you handle pushback from someone above you, which sounds straightforward until you're actually in the room trying not to sound like you're complaining about a past manager.
  • Tell me about a time you disagreed with a more senior colleague, like a tech lead or engineering manager. How did you handle the power dynamic, make your case, and what happened in the end?

“I had a decent story ready but I fumbled the middle part where you explain how you actually navigated the dynamic without just caving or going rogue.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
Google PM interview with a single product design question about building a podcast platform. Pretty open-ended, which sounds fun until you're actually sitting there trying to figure out where to start.
  • How would you design a podcast platform?

“I went straight to users and use cases, which felt right, but I spent too long on the discovery side and barely got to monetization or creator tools before time was up.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
Google product design question, pretty open-ended, the kind where you can go a hundred directions and that's both the fun and the problem.
  • Design a cell phone specifically for families living in urban environments.

“I spent the first minute trying to clarify who exactly counts as a 'family' in a city context and that was probably the right call.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
PM interview at Google, one question about defining metrics for a very specific real-world scenario. Short but not easy.
  • What metrics would you define to measure the success and relevance of COVID-related search results on Google?

“My first instinct was to just list engagement metrics and call it a day, but the COVID angle makes that a trap you can walk into pretty easily.”

View Post

Google·Software Engineer·Onsite - Product Sense / Strategy

Apr 2026
Interviewed for a BA role at Google and got hit with a product metrics question about Gmail. Pretty open-ended, which I wasn't fully prepared for.
  • How would you measure and improve customer satisfaction for Gmail?

“I went straight to NPS and kind of stayed there too long.”

View Post