Snap interview notes, page 6 of 22

“I went straight into user pain points and started rattling off ideas before really anchoring on what Spotlight is even trying to do versus TikTok or Reels.” 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 with the classic disease-test setup because it's easy to plug numbers into, but I fumbled the denominator for a bit.” 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.

“I got the BFS/DFS part working fine but then they asked me to drop the visited set entirely and encode state directly into the input.” 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 is a meaty one.” 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.

“This started easy enough, MSE versus MAE, then they asked about Huber and I fumbled a bit explaining the transition point between the two regimes.” 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.

“I started with the functional requirements which felt like the right move, but I spent way too long on the rider-facing flows and barely got to the interesting stuff.” The rest of the author's notes on Software 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.

“This was the core question and it sprawled.” The rest of the author's notes on Technical Program Manager 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.

“I started with requirements and that part went okay.” The rest of the author's notes on Software 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.

“Knew this one but still fumbled the explanation a bit at first.” 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 actually enjoy this stuff so the derivation part went fine.” 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.