Google interview notes, page 99 of 215

“Two questions stapled together, which I didn't fully appreciate until I was halfway through the design portion and realized I'd burned most of my time.” 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 blanked for a second because it sounds deceptively simple.” The rest of the author's notes on Business Analyst 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 spent too long on the 'is it valuable' part and then had to rush through the experiment design, which is clearly the meat of the question.” 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 single-source BFS 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 knew the algorithm conceptually but fumbled the index range on the randint call.” 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.

“Spent way too long confused by the time-based aspect.” 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.

“My first instinct was to jump straight into features and I had to stop myself.” 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 was a lot to hold in your head at once.” The rest of the author's notes on Software Engineer 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.

“I went straight into storage costs because that felt obvious, but then realized I was ignoring compute, bandwidth, ML inference for things like face grouping, and the support infrastructure underneath all of it.” 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.

“The naive approach of just storing direct manager links breaks down fast once you introduce peers.” 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.