← Back to Directory

Snap interview notes, page 2 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·Technical Phone Screen

Apr 2026
Snapchat software engineer technical screen, 30 minutes, mostly CS and networking fundamentals plus a dig into past projects. Nothing crazy hard but you need to actually know your stuff on the protocol side, surface-level answers won't cut it.
  • When would you choose WebSockets over Server-Sent Events, and what are the trade-offs in terms of directionality, reconnect behavior, and back-pressure?
  • Walk me through the OSI model. What does each layer handle?
  • What problems does QUIC solve compared to TCP with TLS, and where is it being used today?
  • Tell me about a past project. What were the technical decisions you made and why?

“This is the kind of question where you can talk for five minutes and still feel like you only scratched it.”

View Post

Snap·Machine Learning Engineer·Technical Phone Screen

Apr 2026
Snapchat ML Engineer interview had at least one coding round with a classic recursion problem. Nothing too wild but the backtracking angle is easy to fumble if you haven't thought about it carefully beforehand.
  • Given an integer n, generate all combinations of n pairs of well-formed parentheses and return them as a list of strings.

“The recursive backtracking approach is what they're looking for: track how many open and close parens you've placed, and only add a closing paren when the close count is less than the open count.”

View Post

Snap·Software Engineer·Onsite - System Design / Architecture

Apr 2026
Snapchat system design round for a software engineer role. The whole session was one deep-dive question about building a columnar key-value store, with follow-ups that kept coming for the full duration. Pretty intense if you haven't thought carefully about storage layouts before.
  • Design a key-value database where each value is a structured record with multiple columns. The system needs to support not just basic get/set by key, but also column-level reads, full-table scans filtered by a column predicate, and returning only a projected subset of columns.
  • How would you design the query API for this system, specifically the signatures for set, get, and scan operations including column predicates and projection?
  • How would you support range queries on a column, and what secondary index structures would you use?
  • What are the tradeoffs between read and write amplification in this kind of system, and how does your design handle query latency under different access patterns?
  • Follow-up: how would you add persistence, shard the data by key, and handle consistency across shards?

“This is a meaty one.”

View Post

Snap·Machine Learning Engineer·Technical Phone Screen

Apr 2026
Snapchat ML engineer interview that came down to a classic data structure design problem. Pretty standard coding round but the follow-up discussion on tradeoffs between implementations took more time than I expected.
  • Design a data structure that supports O(1) average time for both inserting an item and retrieving a specific or representative element (such as a random one). Walk through your implementation choices and justify the time complexity.

“I went with the hash map plus dynamic array approach for the random-get variant, which worked, but I fumbled a bit explaining the index swap-and-pop trick for deletion.”

View Post

Snap·Software Engineer·Onsite - System Design / Architecture

Apr 2026
Snapchat system design round, backend-flavored, focused entirely on building a price tracking and alert service from scratch. Pretty thorough scope, they wanted the full stack from ingestion to notification fanout.
  • Design a price tracking service where users can monitor product prices across e-commerce sites and get notified when prices drop below a threshold they set.
  • How would you store price history for millions of products, and what kind of data model supports efficient threshold evaluation?
  • Walk through how you'd fan out notifications to millions of users simultaneously when a price drop event triggers.

“This one sprawled fast.”

View Post

Snap·Software Engineer·Technical Phone Screen

Apr 2026
Snapchat coding screen, one algorithmic problem the whole time. The question was cleaner than I expected but I still fumbled the explanation of why the approach works.
  • Given an array of distinct prime numbers, return all distinct products formed by multiplying any non-empty subset of them, sorted in ascending order.

“My first instinct was to just brute-force enumerate subsets and collect products into a set, but the interviewer pushed me on why I didn't need the set at all.”

View Post

Snap·Software Engineer·Onsite - System Design / Architecture

Apr 2026
Interviewed for a security engineer role at Snap and got a system design question about building a secret management service similar to Kubernetes Vault. Pretty deep dive into security architecture territory.
  • Design a secret management service similar to Kubernetes Vault. Walk through the architecture, storage, access control, and how secrets get distributed to services.

“This one took me a minute to get my footing.”

View Post

Snap·Software Engineer·Onsite - System Design / Architecture

Apr 2026
System design round at Snapchat for a software engineer role, centered entirely on designing something like Instagram Stories. Lots of ground to cover and the breadth of it caught me off guard a bit.
  • Design a Stories feature where users can post short photo or video content that disappears after 24 hours, and followers can see a feed of unread stories per user.
  • How would you handle media upload and delivery at scale, including the CDN strategy?
  • How would you track which stories a user has already viewed, and what storage approach would you use?
  • How would you rank or order stories in a follower's feed?

“This is a big one and I underestimated the scope early on.”

View Post

Snap·Software Engineer·Technical Phone Screen

Apr 2026
Snapchat SWE interview with a system design coding problem around a custom key-value store. The core challenge was figuring out the right data structure and then handling updates correctly, which is where things got interesting.
  • Design a key-value store that supports put(key, value), get(key), and sumByPrefix(prefix), where sumByPrefix returns the sum of all values whose keys start with the given prefix. How would you implement this efficiently, and how do you handle updates to existing keys?

“I jumped to a trie pretty fast which felt right, but then the update case tripped me up.”

View Post

Snap·Software Engineer·Technical Phone Screen

Apr 2026
Snapchat iOS coding round, basically a live Xcode session where you build on top of a parameterized grid and wire up navigation to a detail view. More of a product-flavored coding exercise than a pure algorithms grind, which I wasn't fully expecting.
  • You're given a scrollable grid where rows and columns are passed in as parameters and tapping a cell changes it to a random color. Extend this so that tapping a cell also navigates to a detail page showing that color as a full-screen view with its hex or RGB value displayed.
  • Walk through your approach to navigation: would you use NavigationStack with NavigationLink or push a view controller manually, and why?
  • How does view lifecycle work when the user navigates back from the detail view, and what are the implications for state in the parent grid?

“I went with SwiftUI and NavigationStack since that felt cleaner for passing the color as a route value.”

View Post