Google interview notes, page 175 of 215

“I jumped straight into features without anchoring on who the user actually is.” 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 knew the answer is the mean but they wanted the actual derivation, not just the punchline.” 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.

“The part that tripped me up was 'what would you do differently.' I had a solid story ready but kind of fumbled the hindsight piece, gave some generic answer about communicating earlier.” 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.

“The overfitting part came naturally.” 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.

“Two questions in one, which I didn't clock fast enough.” 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 in thinking strengths were obvious (distribution, Android install base, billing infrastructure) but the challenges side is where I stumbled.” 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.

“The base implementation wasn't bad, two hashmaps, one for start times one for end times, pretty straightforward.” 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 regex and I almost went that route before catching myself.” 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 fumbled the opener a bit, started talking about 'explaining my rationale' which felt thin even as I was saying it.” The rest of the author's notes on Software Engineer interview at Google, Onsite - Cross-functional / Panel round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I went straight to 'set up a meeting and align' which felt too safe in hindsight.” 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.