Google interview notes, page 34 of 215

“I had a story ready but mid-answer I realized it kind of made me look passive, like I just waited for the other person to come around.” 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.

“My first pass was pretty natural: read both files into memory, build a dict keyed by obj_id storing a set of client_ids and a flag for whether it appeared in each day.” 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 stared at the average condition for a bit too long before realizing you can just subtract S from every element and now you're looking for the longest subarray with sum zero.” The rest of the author's notes on Machine Learning 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 spent too long on the 'should they' part and not enough on the 'how'.” 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 got the basic structure down pretty fast, two pointers, drain the first list, then the second.” 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 question sounds almost philosophical at first.” 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 a framework about business impact vs user impact and kind of forgot to address the second half of the question, which is the harder part.” 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, data integrity checks, whether it was a logging issue before assuming real user behavior changed.” 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 rough answer ready but three felt like an arbitrary constraint and I kept second-guessing myself mid-answer.” The rest of the author's notes on Technical Program 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 had a decent story ready but halfway through I realized I was spending way too long on the backstory and not enough on what I actually did.” The rest of the author's notes on Machine Learning 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.