Google interview notes, page 170 of 215

“I had a story ready but halfway through I realized I was spending way too long on the background and not enough on what I actually did to fix the breakdown.” 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 jumped straight into features without thinking about the actual user needs first, which felt sloppy in hindsight.” 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 drawing part threw me off more than the actual product thinking.” 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 rambled a bit.” 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 went straight into a story about deprioritizing a monetization feature to fix a pain point users kept complaining about.” 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 two stacks, one for undo and one for redo, and stored a full snapshot of the map at each endBatch() call.” 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 went top-down: estimated global smartphone users, split Android vs iOS share, then tried to reason about how many developers would bother publishing to Play vs App Store.” 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 for the recursive approach because it felt cleaner to think about, but partway through they pushed me toward an iterative stack solution.” 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.

“This is the kind of question where you think you have a good story ready and then halfway through you realize you're accidentally making yourself sound worse than you intended.” 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.

“Took me a while to even figure out what kind of problem this was.” 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.