Snap interview notes, page 21 of 22

“The O(n) constraint is what makes this interesting.” The rest of the author's notes on Software Engineer interview at Snap, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I fumbled the opening by jumping straight into features before even talking about the market.” The rest of the author's notes on Product Manager interview at Snap, 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 went straight to the model layer and spent too long talking about fine-tuning approaches before realizing they probably wanted to hear about data pipelines, privacy constraints, and how you'd handle unstructured clinical notes.” The rest of the author's notes on Machine Learning Engineer interview at Snap, 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 sort the list and do two binary searches, which gets you most of the way there.” The rest of the author's notes on Software Engineer interview at Snap, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“My first instinct was BFS and that was correct, but I wasted a few minutes mentally solving for shortest path length before re-reading and realizing they just wanted a boolean.” The rest of the author's notes on Software Engineer interview at Snap, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“The iterative part was fine, lower bound binary search, nothing too bad.” The rest of the author's notes on Software Engineer interview at Snap, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Classic BFS setup once you see it, but I spent an embarrassing amount of time trying to think about it as a graph problem before realizing it basically IS a graph problem and BFS just falls out naturally.” The rest of the author's notes on Software Engineer interview at Snap, 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 wide.” The rest of the author's notes on Machine Learning Engineer interview at Snap, 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 instinct was to just throw DP at it with floats and call it a day.” The rest of the author's notes on Machine Learning Engineer interview at Snap, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“This tripped me up more than I expected.” The rest of the author's notes on Data Scientist interview at Snap, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.