Google interview notes, page 65 of 215

“This one took me a minute to even understand what they were asking.” 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 with the obvious stuff like caching and CDNs and the interviewer just kind of waited.” 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 had three stories prepped and somehow picked the weakest one in the moment.” 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.

“This one has a lot of surface area and I kind of rambled at first.” 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.

“This question is basically five questions stapled together, which I did not fully appreciate until I was already two minutes into talking about variance estimation and realized I hadn't touched Simpson's paradox yet.” 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.

“Pretty standard union-find setup once you see it.” 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.

“I went straight to hardware cost recovery and got stuck there for a bit.” 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 jumped straight to the split-on-underscore approach and it worked for the basic case.” 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 knew binary search had to be involved but my first instinct was just to test all pairs, which is O(N^2) and the interviewer's face said it all.” 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 unit economics and kind of forgot to anchor on the user side first.” 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.