Snap Software Engineer interview questions

75 Software Engineers have shared notes from their Snap interviews, with the questions they were asked in each round. That is 63% of the 119 Snap interview notes on Screna AI.

75 Software Engineer interview notes

Snap·Software Engineer·Technical Phone Screen

Jun 2026
Snapchat SWE interview with a graph theory problem that sounds straightforward until you realize you need to actually know your cycle detection approaches cold.
  • Given a list of courses and their prerequisites, determine whether it's possible to complete all courses without getting stuck in a dependency cycle.

“Classic graph problem but I second-guessed myself on which traversal to use.”

View Post

Snap·Software Engineer·Onsite - System Design / Architecture

Jun 2026
System design round at Snapchat, focused entirely on building the core of a ride-hailing product. Pretty dense scope for one session and I left feeling like I only half-covered what they wanted.
  • Design the order and dispatch system for a ride-hailing service, covering the full rider request lifecycle from request through matching, trip, and completion.
  • How would you design the driver-side order acceptance flow, including how a driver receives, accepts, or rejects a trip request?
  • Design the user profile storage system for both riders and drivers, including payment info and user preferences.
  • How would you handle high read QPS on user profile data?
  • How would the system handle peak-hour load? Walk through your approach to caching, capacity scaling, request throttling, and surge pricing.
  • Briefly describe how you'd approach geo/map matching between riders and nearby drivers.

“I started with the state machine for a ride request which felt right, but I spent way too long on it and barely got to dispatch logic.”

View Post

Snap·Software Engineer·Technical Phone Screen

Jun 2026
Snapchat SWE interview that was basically a grid traversal problem with a twist. Nothing too wild but the follow-up about optimization tripped me up a bit.
  • Given a binary grid with multiple islands, find the maximum perimeter among all islands. Each island is a 4-connected group of land cells, and perimeter counts edges bordering water or the grid boundary.

“I knew LC 463 so the base logic wasn't the problem.”

View Post

Snap·Software Engineer·Technical Phone Screen

Jun 2026
Snapchat software engineer interview that leaned pretty hard into Swift fundamentals. One question, but it had a lot of surface area and I don't think I covered all of it as cleanly as I should have.
  • What are the key differences between class and struct in Swift? Think about things like how they handle memory, mutability, inheritance, and when you'd actually choose one over the other.

“I started with value vs reference semantics which was the right call, but then I kind of rambled through the rest without a clear order.”

View Post

Snap·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Snapchat system design round, one big question that sprawled across basically every infrastructure topic I'd ever read about. Felt like they wanted to see how far you could go before you started hand-waving, and I definitely hit that ceiling a few times.
  • Design a metrics platform that handles ingestion from many services, stores data efficiently for real-time and historical use, supports configurable alerting with low latency, and can answer product-level queries like daily active users alongside low-level system metrics. Walk through the ingestion pipeline, storage choices with rollups, alerting evaluation, and whether product and infrastructure metrics should share the same pipeline.

“This question kept growing.”

View Post

Snap·Software Engineer·Technical Phone Screen

Jun 2026
Snapchat software engineer interview that went deep on memory fundamentals. One meaty question about stack vs heap that felt straightforward at first but had a lot of surface area once they started poking at Swift specifics.
  • Walk me through the differences between stack and heap memory: how allocation and deallocation work, object lifetimes, performance, thread safety, what typically lives in each, and how Swift's value types and reference types map to each region.

“I started okay on the basics, allocation is fast on the stack because it's just a pointer bump, heap needs a runtime allocator and can fragment, stack is per-thread so inherently safe, heap is shared and needs synchronization.”

View Post

Snap·Software Engineer·Technical Phone Screen

Jun 2026
Snapchat SWE interview with a system design coding question that was heavier on data structures than I expected. The focus on trie internals caught me a little off guard since I'd been drilling more graph stuff.
  • Design a key-value store where keys are strings and values are integers. It should support inserting or updating a key, retrieving a value by key, and returning the sum of all values whose keys share a given prefix. How would you structure this, and how do you handle updates efficiently?

“I started with a hashmap and immediately knew that wasn't going to cut it for the prefix sum part.”

View Post

Snap·Software Engineer·Technical Phone Screen

Jun 2026
Snapchat SWE interview with a graph problem that looked straightforward but had enough edge cases to keep me honest. Single coding round, algorithm focused.
  • Given an undirected graph defined by a node count and two parallel edge arrays, find each connected component and compute the difference between the max and min node values within it. Return the largest such difference across all components.

“My first instinct was union-find but I went with DFS since I could code it faster under pressure.”

View Post

Snap·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Snapchat system design round for a software engineer role. The whole session was basically one big deep-dive into building a column-queryable key-value store, with follow-ups that kept branching into persistence, sharding, and consistency. Pretty intense for a single question.
  • Design a key-value database where each value is a structured record with multiple columns. The system needs to support column-level reads, predicate-based scans across all records, and projected column returns. Walk through your data model, in-memory structures, secondary indices, query API, range query support, and the read/write amplification trade-offs.
  • How would you add persistence to this key-value store?
  • How would you shard this database by key, and what complications does that introduce for column-based scans?
  • How do you maintain consistency in this system, especially across column updates for the same key?

“This is the kind of question where you think you're doing fine and then realize fifteen minutes in you've only covered like 20% of it.”

View Post

Snap·Software Engineer·Technical Phone Screen

Jun 2026
Snapchat software engineer interview, got a bit puzzles question that felt almost too easy at first glance but has a slick O(1) solution if you know your bitwise tricks.
  • Given an integer n, determine whether it is a power of two.

“I knew this one but still fumbled the explanation a bit.”

View Post