Snap interview notes, page 15 of 22

“I started with feature categories (recency, frequency, engagement decay) and mentioned handling class imbalance with SMOTE vs just reweighting the loss.” 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 knew this was DFS with memoization pretty fast, the tricky part is realizing you don't need visited tracking because the strictly increasing constraint already prevents cycles.” 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 jumped straight into the case-sensitive version without asking, which they let me do, but then they asked about case-insensitivity and I had to basically rewrite the logic.” 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 went okay until they pushed on the inference behavior.” 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.

“My first instinct was shortest path and I almost reached for Bellman-Ford out of habit.” 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.

“Spent the first minute going too broad, talking about user surveys and stuff before they nudged me toward instrumentation data.” 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 one threw me a bit because you have to think about it from two angles at once: the distributed systems side and the adversarial/security side.” 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 question is doing a lot of work at once and I underestimated the last part.” 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 was the whole interview basically.” 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.

“My first instinct was union-find but I defaulted to BFS since I could code it faster under pressure.” 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.