← Back to Directory

Snap

Large Enterprises

Most of these Snap write-ups come from Software Engineers (75), then Machine Learning Engineers (39) and Backend Engineers (4). The most reported rounds are the technical phone screen (81), the system design round (30), the behavioral / leadership round (4) and the hiring manager screen (1).

119 interview notes · updated Jun 2026

Snap·Backend Engineer·Technical Phone Screen

Jun 2026
Phone screen for a backend role at Snapchat with two behavioral questions back to back. Pretty standard stuff but the pairing felt deliberate, like they wanted to see both your communication instincts and how you hold up when things go sideways.
  • Describe a time you had to explain a technical concept, decision, or trade-off to someone non-technical, like a PM, executive, or business partner. How did you simplify it, confirm they understood, and use it to move a decision forward?
  • Tell me about a time something unexpected hit you mid-project or in production. How did you figure out what was happening, keep the right people informed, and get things back on track?

“I went with a story about explaining why we couldn't just 'add a cache' to fix latency without talking about consistency trade-offs.”

View Post

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·Machine Learning Engineer·Onsite - System Design / Architecture

Jun 2026
System design round for an MLE role, centered entirely on one massive open-ended problem about building a product tagging pipeline from scratch. Felt more like a staff-level architecture session than a typical ML interview. Walked away unsure if I covered enough ground or just rambled for an hour.
  • Design an end-to-end pipeline that automatically assigns category, attribute, and quality tags to products listed on a short-video commerce platform, starting from raw seller inputs like titles, descriptions, images, and video.
  • How would you design the taxonomy and label space for product tags, and how do you decide between training separate models per tag type versus a single joint model?
  • Walk through how you'd handle weak supervision and human-in-the-loop labeling when you don't have enough ground truth data to train a reliable tagger.
  • How do you monitor tag quality in production, and what signals would you track to detect model drift or degradation over time?
  • How do the product tags you generate get consumed by downstream systems like search, recommendations, and ads, and does that change how you design the tagging pipeline?
  • How would you handle multilingual product catalogs and adversarial sellers who try to manipulate tags to game search or recommendations?

“This was the whole interview.”

View Post

Snap·Machine Learning Engineer·Technical Phone Screen

Jun 2026
Interviewed for an MLE role at Snapchat and got hit pretty hard on normalization fundamentals. Not a bad experience overall but I clearly needed to sharpen up on the theory side before walking in.
  • Walk me through how Layer Normalization works, including how statistics are computed, what the learnable parameters do, and how it compares to Batch Normalization. Why do Transformers use LayerNorm instead of BatchNorm?

“I started okay on the mechanics: mean and variance computed per sample across the feature dimension, then you normalize and apply the learned scale and shift.”

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 interview FAQ

What rounds are in the Snap interview?

Candidates most often report a technical phone screen (81 write-ups), a system design round (30), a behavioral / leadership round (4) and a hiring manager screen (1).

What does the Snap technical phone screen cover?

Across 81 technical phone screen write-ups, the most tagged question topics are Technical Trade-offs (86 questions), Algorithms & Data Structures (71) and System Design (48).

What is asked in the Snap system design round?

Across 30 system design write-ups, the most tagged question topics are System Design (108 questions), Technical Trade-offs (88) and Data Modeling (23).

Snap interview guides by role

75 notes

Snap Software Engineer interview questions

39 notes

Snap Machine Learning Engineer interview questions