Google interview notes, page 23 of 215

“This tripped me up because my brain kept wanting to go to software solutions.” 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 celebrate the comments and explain away the watch time drop, which in hindsight was exactly the wrong direction.” 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 spent the first minute just trying to figure out who exactly we were designing for, a server, a host, kitchen staff, the owner?” 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 interviewer literally said at some point that the question was too open-ended, which was both reassuring and kind of unsettling.” 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 resource reallocation and I think that was the wrong move to lead with.” The rest of the author's notes on Technical Program Manager 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 'longest subsequence' part threw me off more than I expected.” 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.

“The brute force answer comes out naturally but you have to get to the HashMap solution on your own.” 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.

“The minimum cars part I got pretty fast, it's basically an interval scheduling problem with a min-heap tracking when each car becomes free.” 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 froze for a second because picking something too obscure feels like a cop-out but picking something big feels risky.” 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 it was stack-related pretty fast but fumbled the parentheses logic for a minute.” 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.