Google interview notes, page 100 of 215

“This one took me a second to find the right entry point.” 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 LRU cache cold going in.” 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.

“Took me a minute to stop thinking brute force.” 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.

“This one has more layers than it looks.” 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 had a decent story ready but I spent too long on the setup and rushed the outcome part, which is probably the whole point of the question.” 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 screen size and touch targets, which felt a bit surface-level in retrospect.” 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.

“Spent the first few minutes thinking about routing and coverage, which felt right, but I underweighted the data pipeline side.” The rest of the author's notes on Technical Program Manager 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 blanked for a second because I kept thinking 'why are they asking me this, I'm a SWE candidate.' Once I got past that I tried to think about what Doodles actually does: it's not a revenue product, it's more about brand and engagement.” 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 straight to ads and then kind of stalled.” 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 textbook answer, a model at 0.5 is basically guessing randomly, no better than a coin flip.” 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.