Google interview notes, page 102 of 215

“I picked something I knew cold but rambled way too much on the discovery phase and ran out of time before getting to launch and results.” 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 straight to market sizing and kind of stalled 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 started with the obvious stuff, DNS failure, CDN issues, and then tried to work my way into the less obvious layers like quota exhaustion or a bad config push.” 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 ready but I rambled too much on the setup and not enough on what the data actually showed.” 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.

“I had a decent story ready for this but I rambled.” 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 jumped straight to solutions which was a mistake.” 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 straight to revenue upside and kind of forgot to anchor on what Google Flights is actually for.” 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.

“I thought shared goals meant the hard part was done, so I started talking about OKRs and got maybe two sentences in before I realized I was describing the problem, not solving it.” The rest of the author's notes on Product 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.

“I started with relevance signals and went into purchase history, ratings, seller reliability, that kind of thing.” 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 straight into use cases and kind of skipped the 'should we even do this' part, which I think hurt me.” 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.