Google interview notes, page 80 of 215

“I went population-first, broke SF into commuter segments by distance, then tried to back into a dollar figure using average ride frequency and pricing.” The rest of the author's notes on Software Engineer 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.

“My first instinct was to jump straight to ML classifiers and I had to stop myself because that's just the engineering answer, not the PM answer.” 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.

“Seemed simple at first glance.” 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 a story prepped but the second I started telling it I could feel it going flat.” 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 started with device sales projections and worked down to average photo library size per user, which felt right.” 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.

“Went through the usual suspects: B-tree, hash, composite, partial.” 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.

“Classic Caesar cipher type problem.” 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.

“My first instinct was to just say 'keep a counter somewhere' which, yeah, not great.” The rest of the author's notes on Technical Program Manager interview at Google, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Went with the classic likelihood-times-impact framing and then broke it into buckets like operational, compliance, reputational.” 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 listed things like curiosity and communication and immediately felt like I was reciting a LinkedIn post.” 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.