Snap interview notes, page 16 of 22

“I started with the pull scheduler and worked outward, which felt natural but I think I spent too long on rate limiting and auth per source before even touching dedup or ranking.” 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.

“The data model part I felt decent about.” The rest of the author's notes on Backend 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.

“I knew the punchline but fumbled the derivation.” 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 was basically five system design questions rolled into 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.

“I started with the repeated multiplication angle, which felt solid, then moved into saturating activations like sigmoid and tanh.” 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 aggregation part first because it felt easier, groupby story_type and sum views and likes, that was 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.

“I had a version of this answer ready but I think I leaned too hard into the technical side and not enough on the product judgment angle.” The rest of the author's notes on Data Scientist 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.

“Big open-ended question and I spent probably too long on candidate generation before they nudged me toward ranking.” 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 sounds like a softball until you realize they want all five layers: context, your role, the hard parts, the outcome with numbers, and what you took away from it.” The rest of the author's notes on Software 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.

“The follow-ups are where this question gets real.” The rest of the author's notes on Software 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.