← Back to Directory

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

May 2026
Google PM interview with a classic Fermi-style estimation question. Pretty short experience to report but the question itself was a trip.
  • Estimate the bandwidth in bits per second of a Boeing 747 flying across the Atlantic Ocean with its cargo hold filled with CD-ROMs.

“I stared at this for a second because it sounds like a joke but they were completely serious.”

View Post

Google·Software Engineer·Onsite - Behavioral / Leadership

May 2026
Interviewed for an EM role at Google, got a behavioral round focused on people management. One question, pretty standard for the level, but it still made me think harder than I expected.
  • Can you walk me through a time you helped develop someone on your team and kept them engaged enough to stick around?

“I had a decent story ready but I think I leaned too hard into the 'retention' angle and undersold the actual development part.”

View Post

Google·Software Engineer·Technical Phone Screen

May 2026
Interviewed for a security engineer role at Google and got asked about incident response fundamentals. Pretty short interaction, not much to report.
  • What is incident response?

“Pretty broad question.”

View Post

Google·Software Engineer·Technical Phone Screen

May 2026
Google SWE interview with a classic hard linked list problem. Not much to say about the setup but the question itself took me a while to get right.
  • Given k sorted linked lists, merge them all into a single sorted linked list.

“My first instinct was to just repeatedly merge two lists at a time, which works but is not great on complexity.”

View Post

Google·Data Scientist·Technical Phone Screen

May 2026
A/B testing design question for a DS role at Google. The whole thing was one big open-ended case about search ranking experiments, and they expected you to cover a lot of ground without much hand-holding.
  • Design an A/B test to compare two search ranking algorithms. Walk through your hypothesis, primary and guardrail metrics, randomization unit, sample size and statistical power, test duration, segmentation strategy, novelty effects, and how you'd decide whether to ship.

“This question has a lot of moving parts and I think I underestimated how much structure they wanted upfront.”

View Post

Google·Product Manager·Onsite - Product Sense / Strategy

May 2026
Google PM interview with a single product design question about shared laundry. Pretty open-ended, which I wasn't fully prepared for.
  • How would you design a shared laundry experience?

“I went straight into features without anchoring on who the user actually is.”

View Post

Google·Product Manager·Onsite - Behavioral / Leadership

May 2026
Went through a behavioral round for a PM role at Google. Just the one question but it took up most of the time, lots of follow-ups.
  • Describe a situation where you had to re-energize a team after something went badly.

“I had a decent story ready but the follow-ups pushed me into territory I hadn't thought through.”

View Post

Google·Software Engineer·Onsite - Behavioral / Leadership

May 2026
Behavioral screen for a SWE role at Google. Just one question but it's the kind that sounds easy until you're actually in it trying to explain your reasoning without sounding like you're reciting a framework.
  • If you were juggling five different projects at once, how would you decide which ones to prioritize?

“I rambled a bit about deadlines and stakeholder impact and it felt like I was just listing things rather than actually showing a thought process.”

View Post

Google·Software Engineer·Onsite - Coding / Algorithms

May 2026
Google SWE coding round with a tricky scheduling problem that had a cyclic twist I didn't see coming. The core concept wasn't hard but the wrap-around time constraint added enough complexity to make me second-guess my whole approach mid-interview.
  • Given a list of meetings with start and end times in a single day, find the minimum number of meeting rooms needed. Meetings can wrap around midnight (e.g. 10 PM to 2 AM), so the schedule is cyclic.

“The standard meeting rooms problem I'd done before, but the cyclic part broke my initial solution completely.”

View Post

Google·Software Engineer·Technical Phone Screen

May 2026
Google SWE coding round with a grid traversal problem that sounds deceptively simple but has a few layers to it once you start thinking about the cost function.
  • Given a 2D grid where each cell has a height value, find a path from the top-left to the bottom-right such that the maximum cell value along the path is minimized. You can only traverse a cell if the current 'water level' is at least as high as that cell's height. Return the minimum possible maximum value across all valid paths.

“My first instinct was to just do a BFS and track the path sum, which was completely wrong.”

View Post