Microsoft interview notes, page 31 of 60

“Picked Teams because I use it every day and figured I'd have plenty to say.” The rest of the author's notes on Product Manager interview at Microsoft, Onsite - Product Sense / Strategy round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“This one had layers I didn't fully anticipate.” The rest of the author's notes on Software Engineer interview at Microsoft, Onsite - System Design / Architecture 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 just say 'run an A/B test' and I basically did say that, but then they kept probing and I realized I hadn't thought through the setup at all.” The rest of the author's notes on Product Manager interview at Microsoft, Onsite - Product Sense / Strategy round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Prepared a story about a deadline crunch with a half-broken codebase.” The rest of the author's notes on Software Engineer interview at Microsoft, Onsite - Behavioral / Leadership round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Easy opener, or so I thought.” The rest of the author's notes on Software Engineer interview at Microsoft, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“This question is deceptively open.” The rest of the author's notes on Software Engineer interview at Microsoft, 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 kept second-guessing whether it was senior enough.” The rest of the author's notes on Software Engineer interview at Microsoft, Hiring Manager Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Recursive solution came to me pretty quick but I fumbled on the edge cases, empty dicts, values that are themselves empty nested dicts, that kind of thing.” The rest of the author's notes on Software Engineer interview at Microsoft, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“The actual implementation took maybe 15 minutes, just a dict with some wrapper methods.” The rest of the author's notes on Software Engineer interview at Microsoft, Onsite - Coding / Algorithms 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 write the naive triple loop and I almost did before catching myself.” The rest of the author's notes on Software Engineer interview at Microsoft, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.