Google interview notes, page 184 of 215

“I started with the 30% cut Google takes and tried to build up from DAU estimates for Android users.” 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.

“My first instinct was to jump straight to car fleet costs and I almost forgot about the data processing side entirely.” 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.

“Felt solid here.” 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 brought up database sharding and he pushed back immediately, said something was wrong with how I described it.” The rest of the author's notes on Software Engineer interview at Google, Hiring Manager 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 engagement metrics and kind of stalled when they pushed back asking what 'successful' even means.” The rest of the author's notes on Software Engineer interview at Google, Hiring Manager Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Started by anchoring on total U.S.” 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 basics: logging runs, storing hyperparameters, tracking metrics over time.” The rest of the author's notes on Machine Learning 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.

“Took me longer than it should have to see this as a graph problem.” 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 started with a basic map from id to node and got addEmployee working pretty quickly.” 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 'increase traffic allocation' and 'shorten the test window' and the interviewer kind of waited like they expected more.” 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.