← Back to Directory

Snap interview notes, page 10 of 22

Large Enterprises

Most of these Snap write-ups come from Software Engineers (117), then Machine Learning Engineers (65) and Data Scientists (18). The most reported rounds are the technical phone screen (149), the system design round (45), the behavioral / leadership round (11) and the product sense round (8).

216 interview notes · updated Jul 2026

Snap·Software Engineer·Onsite - System Design / Architecture

May 2026
Snapchat system design round focused entirely on the backend of a short-video feed, basically a TikTok-style recommendation pipeline. Pretty deep dive, they wanted real trade-off discussion not just a high-level sketch.
  • Design the backend feed-vending service for a short-video product like Snapchat Spotlight. The core API is getFeed(user_id, cursor, page_size) and it needs to return personalized, paginated video recommendations with metadata like CDN URLs, thumbnails, and captions.
  • How would you handle de-duplication so users don't see videos they've already watched, both within a single session and over a longer time window?
  • Walk through your CDN strategy for video delivery, including how you'd handle access control with signed URLs.
  • What are the trade-offs between a push-on-write feed (fan-out at upload time) versus a pull-on-read feed for this type of product?

“This is the main question and it ate the whole session.”

View Post

Snap·Software Engineer·Technical Phone Screen

May 2026
Snapchat SWE interview with a grid pathfinding problem. Pretty standard stuff if you've done BFS before, but they wanted the full complexity breakdown too which tripped me up a little.
  • Given an m x n grid where 0 is passable and 1 is blocked, and you can move in 4 directions, find the shortest path (in number of moves) from a start cell to a target cell. Return -1 if no path exists. Walk through your algorithm and give the time and space complexity.

“BFS was the right call and I knew it immediately, but I fumbled the complexity explanation.”

View Post

Snap·Software Engineer·Onsite - System Design / Architecture

May 2026
Snapchat system design round, one big open-ended question about building a news aggregator from scratch. Pretty intense scope for a single session, they wanted you to cover basically everything.
  • Design a news aggregation system that pulls articles from many external sources (no RSS, only APIs) on a schedule, deduplicates content, stores and ranks it, and serves a fresh unified feed to end users efficiently.

“This one sprawled fast.”

View Post

Snap·Machine Learning Engineer·Onsite - System Design / Architecture

May 2026
Snapchat ML Engineer interview that went deep into recommendation system design. The whole session was basically one big open-ended question about building something like Yelp, and they kept pushing on specifics whenever I tried to stay high-level.
  • Design a restaurant recommendation system similar to Yelp. Walk through your model architecture, how you'd structure the retrieval and ranking stages, and what features you'd use.
  • How would you handle cold-start for both new users and new restaurants in this system?
  • What offline and online metrics would you use to evaluate this recommendation system, and how do they connect to each other?
  • What training data would you use, and what are the key tradeoffs in how you collect and label it?

“I started with two-tower retrieval and they seemed fine with that, but then they drilled into why I'd separate retrieval from ranking at all.”

View Post

Snap·Machine Learning Engineer·Onsite - Behavioral / Leadership

May 2026
Behavioral round for an ML Engineer role at Snapchat, focused heavily on innovation and ownership. Just the one question but they went deep on it with follow-ups, so come prepared to actually defend your story.
  • Tell me about a time you drove innovation at work. Walk through the problem you identified, what you did, the trade-offs you navigated (technical risk, pushback, resource constraints), the outcome, and what you learned. Be ready to explain how you decided the idea was worth pursuing and how you got others on board.

“This one has a lot of surface area and the follow-ups are where it gets uncomfortable.”

View Post

Snap·Software Engineer·Onsite - System Design / Architecture

May 2026
Snapchat SWE interview that went deep into streaming data design. The question sounds straightforward until you're actually in it and realize how many edge cases they want you to think through.
  • Design a class that supports a live data stream and can return the top K elements efficiently at any point. Walk through your choice of data structures, the time and space complexity of your add and topK operations, how you handle ties, and what changes if the stream is arbitrarily large.

“I went straight to a min-heap of size K backed by a hash map for frequency counts, which is the right skeleton.”

View Post

Snap·Data Scientist·Technical Phone Screen

May 2026
Snapchat data scientist interview that went deep on A/B testing, and I mean really deep. One question, but it sprawled into six or seven distinct sub-problems covering everything from sample size math to bot filtering. Left feeling like I'd half-answered a take-home assignment out loud.
  • Walk through an end-to-end A/B test for adding a home-page banner: randomization unit, metric selection, sample size calculation, analysis approach, diagnostic checks, and launch decision criteria.

“This started as one question and quietly became six.”

View Post

Snap·Machine Learning Engineer·Technical Phone Screen

May 2026
Snapchat ML Engineer interview that leaned pretty heavily into probabilistic modeling fundamentals. The calibration question was the main technical focus and it went deeper than I expected for what felt like a screening round.
  • What is model calibration, how do you measure it, and how would you go about improving a poorly calibrated model?

“Started okay, said something about predicted probabilities matching actual frequencies, which is the right intuition.”

View Post

Snap·Software Engineer·Onsite - Behavioral / Leadership

May 2026
Behavioral round at Snapchat for a software engineer role, focused on how you handle pressure and tight timelines. Pretty much one meaty scenario question the whole time.
  • You're handed a project with an aggressive deadline and not enough time or resources. How do you make sure it still ships on time?

“I started rambling about milestones and the interviewer kind of waited me out, which told me I was probably too abstract.”

View Post

Snap·Software Engineer·Technical Phone Screen

May 2026
Snapchat coding interview, pretty much one big question about LRU cache design and implementation. Felt like a classic but they pushed hard on the internals.
  • Design and implement an LRU cache with get and put operations both running in O(1) average time. When capacity is hit, evict the least recently used entry. Walk through your data structure choices and explain how each operation keeps recency ordering correct.

“I knew the answer going in (hash map plus doubly linked list, classic combo) but fumbled explaining WHY the doubly linked list specifically.”

View Post