Amazon interview notes, page 61 of 159

“My first instinct was to split on dots and then handle brackets separately, which got messy fast.” The rest of the author's notes on Software Engineer interview at Amazon, Onsite - Coding / Algorithms round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Went okay.” The rest of the author's notes on Data Scientist interview at Amazon, 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 tripped me up a little because I kept wanting to make it a story about the AI being wrong, but they seemed more interested in the process of deciding what even needed checking.” The rest of the author's notes on Software Engineer interview at Amazon, Onsite - Behavioral / Leadership round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“The rolling part is where I fumbled.” The rest of the author's notes on Data Scientist interview at Amazon, 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 in thinking a broad background summary would land well.” The rest of the author's notes on Product Manager interview at Amazon, Hiring Manager Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“The scope feels manageable until they start pulling on specific threads.” The rest of the author's notes on Software Engineer interview at Amazon, 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 went with a story about a roadmap call where engineering pushed back hard on a feature I was championing.” The rest of the author's notes on Product Manager interview at Amazon, Onsite - Behavioral / Leadership round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I picked a project I knew well but ended up spending too long on the problem setup and barely had time to talk about results.” The rest of the author's notes on Machine Learning Engineer interview at Amazon, 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 with imputation pretty quickly, mean for numerical stuff, mode for categoricals, but they pushed back and asked when that might actually hurt you.” The rest of the author's notes on Data Scientist interview at Amazon, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“The part that tripped me up was 'measurable change.' I had a decent story about code review feedback but I'd never thought to quantify the outcome.” The rest of the author's notes on Software Engineer interview at Amazon, Onsite - Behavioral / Leadership round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.