Google interview notes, page 95 of 215

“Tricky one because you can't just say 'I confronted them' without sounding combative, but you also can't say nothing or you look like a pushover.” The rest of the author's notes on Software Engineer interview at Google, Onsite - Behavioral / Leadership round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I went straight to population size and tried to build up from there, which was fine, but I kept second-guessing my assumptions out loud and it made the whole thing feel shaky.” The rest of the author's notes on Product Manager interview at Google, Onsite - Product Sense / Strategy round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I started with total number of cars sold globally, then tried to estimate what fraction might be autonomous by 2025.” The rest of the author's notes on Software Engineer interview at Google, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“This was a lot packed into one question and I kind of answered it in a scattered order.” The rest of the author's notes on Data Scientist interview at Google, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I went straight to driver supply density in the area, which felt obvious in retrospect.” The rest of the author's notes on Product Manager interview at Google, Onsite - Product Sense / Strategy round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I went with DFS immediately and it was fine.” The rest of the author's notes on Software Engineer interview at Google, Onsite - Coding / Algorithms round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Started with a queue of timestamps, which works fine but I fumbled explaining the space complexity when hits pile up.” The rest of the author's notes on Software Engineer interview at Google, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I started talking about a right-skewed distribution pretty quickly, which felt right, but then I kind of stumbled when thinking about how to actually characterize it precisely.” The rest of the author's notes on Software Engineer interview at Google, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I went straight to user pain points which felt right but I spent way too long on the obvious stuff like wait times and accessibility.” The rest of the author's notes on Product Manager interview at Google, Onsite - Product Sense / Strategy round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I started rambling about wait times before I even defined who I was designing for.” The rest of the author's notes on Product Manager interview at Google, Onsite - Product Sense / Strategy round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.