Snap interview notes, page 17 of 22

“I went straight to the short-term vs long-term split and talked about vector stores for retrieval.” 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 sounds like a warm-up but it sprawls fast.” 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 knew Manhattan distance problems lean on medians pretty quickly, so I jumped to projecting rows and columns separately.” 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 a full system design compressed into one question.” 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.

“I started with static analysis, file type checks, hashing against known malware databases, then moved into dynamic analysis in a sandbox.” 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 to just sort the timestamps and do binary search on both ends, which works fine.” 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 started with the storage schema and probably should've asked more clarifying questions first.” 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.

“Started with BFS which felt natural to me, got through it fine, but then they asked me to redo it with Union-Find.” 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 Taylor series and I went with that, which is fine for small x but I didn't think about range reduction until they pushed back.” 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 started with BFS because it felt safer.” 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.