Snap Interview Questions — Page 18

Snap·Software Engineer·Onsite - System Design / Architecture

Jun 2026

Snapchat system design round, one big question about building a metrics and alerting platform from scratch. Pretty dense for a single session and I left feeling like I'd only half-answered it.

Design a metrics ingestion and storage platform that supports real-time monitoring, historical analysis, configurable alerting, and product-level analytics like DAU. Walk through the ingestion pipeline, your choice of time-series storage, rollup strategy, alert evaluation latency, and whether product metrics and infrastructure metrics should share the same pipeline and storage.

“This was basically four questions wrapped in one and I didn't pace myself well.”

View Post

Snap·Software Engineer·Technical Phone Screen

Jun 2026

Snapchat SWE interview with a card-flipping string formation problem. Pretty niche problem, not your typical LeetCode grind fare, and the backtracking angle took me a minute to see clearly.

You're given a set of cards where each card has a letter on each side. Given a target string, can you form it using the cards, where each card can only contribute one of its two letters and each card can only be used once?

“I stared at this for a bit before the constraint clicked: if 'a' and 'b' are on the same card, you can't use both.”

View Post

Snap·Backend Engineer·Technical Phone Screen

Jun 2026

Snapchat backend screen, one algorithmic problem the whole time. Pretty standard union-find territory but I fumbled the counting step at the end and had to backtrack.

Given n employees and a list of pairs indicating which employees belong to the same group (with transitivity), count the total number of unordered pairs of employees that come from different groups.

“I recognized the connected components angle pretty fast and went with union-find.”

View Post

Snap·Machine Learning Engineer·Technical Phone Screen

Jun 2026

Snapchat ML Engineer interview that leaned hard into architecture fundamentals. The main question was a deep comparison between CNNs and transformers, which sounds straightforward until you're actually in the room trying to articulate inductive bias trade-offs on the spot.

Walk through the key differences between convolutional neural networks and transformer architectures, covering inductive biases, data and compute needs, long-range dependencies, typical use cases, and how modern hybrid models try to get the best of both.

“This question is broader than it looks.”

View Post

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

Jun 2026

Snapchat ML Engineer system design round, basically a single massive question about building a trustworthy ranking system end to end. Dense, no warmup, they went straight into the hardest parts. Felt like they really wanted to see if you'd thought about the messy real-world stuff, not just the textbook pipeline.

Design a ranking system (recommendation, search, or feed) where model trustworthiness is critical and ground-truth labels like conversions or retention only arrive days or weeks after the fact. Walk through the full system: feature pipeline, feature store, candidate generation, ranker model, online serving, and how you handle delayed labels in training.
How do you use surrogate or proxy labels to get fast feedback when your real labels are delayed, and how do you prevent those proxies from leaking future information into your training data?
How would you run A/B tests for a ranking model when your primary success metric depends on outcomes that take days or weeks to observe?
How do you handle position bias and selection bias in a learned ranking model, and what does your debiasing approach look like in practice?
What does your monitoring setup look like for a ranking system, specifically around data drift, model drift, and fairness across different user segments?
If a deployed ranking model starts behaving badly, what's your rollback strategy and how quickly can you execute it?
How do you calibrate model output scores and handle uncertainty estimation in a ranking context where you need the scores to be meaningful, not just relatively ordered?

“This is basically five questions rolled into one.”

View Post

Snap·Machine Learning Engineer·Technical Phone Screen

Jun 2026

Snapchat ML Engineer interview with a graph traversal coding question. Pretty standard BFS stuff but the follow-ups pushed into territory I hadn't fully thought through beforehand.

Given an n x n binary grid where 0 is open and 1 is blocked, find the length of the shortest clear path from the top-left to the bottom-right cell. You can move in all 8 directions. Return -1 if no path exists or either endpoint is blocked.
How would your solution change if different moves had different costs?
How would you return the actual path taken, not just the length?
How would you adapt the solution for a rectangular grid instead of a square one?
How would you handle the case where diagonal corner-cutting is disallowed, meaning you can only move diagonally if the two adjacent orthogonal cells are also open?

“I knew it was BFS immediately, which felt good, but I fumbled the setup a bit.”

View Post

Snap·Software Engineer·Technical Phone Screen

Jun 2026

Two coding problems back to back for a Snapchat SWE screen. The LRU cache is a classic but the prime subsets question was a nice change of pace, less rote than I expected.

Implement an LRU cache with get and put operations, both running in O(1) average time.
Given an array of distinct prime numbers, return a sorted list of all unique products that can be formed from any non-empty subset of those primes.

“I knew this one cold so I jumped straight to doubly linked list plus hashmap.”

View Post

Snap·Software Engineer·Technical Phone Screen

Jun 2026

Snapchat coding interview with a classic grid traversal problem. Pretty standard stuff if you've done any graph prep, but the follow-up questions about complexity and representation kept it from being a total freebie.

Given a grid with a start cell, an end cell, and some blocked cells, determine if there's a valid path from start to end moving in four directions without crossing blocked cells.

“Went with BFS pretty quickly, which felt right.”

View Post

Snap·Software Engineer·Technical Phone Screen

Jun 2026

Snapchat software engineer interview that went deep into data structures fundamentals. The main ask was building a generic hash map from scratch in Swift, which sounds manageable until you're live-coding rehashing logic and justifying every design decision out loud.

Implement a generic Dictionary<Key: Hashable, Value> from scratch in Swift, without using the built-in Dictionary as backing storage. Your implementation should support subscript get/set, insertion, deletion, lookup, and iteration. Walk through your collision-resolution strategy, load factor choice, and resize/rehashing policy, and analyze the amortized time complexity of each operation.

“I went with separate chaining because it felt safer to reason about under pressure, but the interviewer pushed back pretty hard asking why not open addressing, what the cache behavior difference is, and whether I'd change my answer for a memory-constrained environment.”

View Post

Snap·Machine Learning Engineer·Technical Phone Screen

Jun 2026

Snapchat ML engineer interview that leaned hard into normalization fundamentals. The question sounds textbooky but the comparison piece is where they actually push you.

Explain how Layer Normalization works, including how mean and variance are computed, the learnable parameters, and the normalization formula. Then compare it to Batch Normalization and explain why LayerNorm is preferred in Transformers.

“Started fine on the mechanics: mean and variance computed across the feature dimension for each sample independently, then you normalize and apply the learnable scale and shift.”

View Post