Snap interview notes, page 14 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

Jun 2026

Snapchat SWE interview that went deep on custom data structures and functional programming patterns. One question but it had a lot of layers and I was not fully prepared for the generics conversation that followed the coding part.

You have a hand-built List backed by a dynamic array with standard operations (add, get, set, remove, size) and an Iterator (hasNext, next). Implement a map(fn) method that applies a given function to each element and returns a new List of the results, using only the Iterator and not touching the backing array directly. Then discuss generic typing where input and output types can differ, eager vs. lazy evaluation, and how laziness interacts with source list mutation.

“The coding part was fine.”

View Post

Snap·Software Engineer·Technical Phone Screen

Jun 2026

Snapchat software engineering interview focused on a rate limiter design problem with a solid concurrency follow-up that I didn't feel fully prepared for. The coding portion was manageable but the discussion around locking strategies went deeper than I expected.

Design and implement a per-user API rate limiter with a method `boolean allow(String userId, long nowMillis)` that enforces a maximum of N requests per W milliseconds per user.
How would you make the rate limiter thread-safe when multiple threads are calling `allow` for the same user concurrently? What are the tradeoffs between using locks versus lock-free approaches like atomics or ConcurrentHashMap?

“I went with a sliding window approach using a deque to track timestamps per user.”

View Post

Snap·Data Scientist·Technical Phone Screen

Jun 2026

Snapchat data scientist interview with a meaty A/B testing design question. The whole session was basically one long scenario, but it went several layers deep, so there was a lot to keep track of.

Design an A/B test to measure the impact of a new recommendation algorithm on GMV. What primary and guardrail metrics would you track, and why?
How would you calculate the required sample size for this test, given a 3% baseline conversion rate, a 7% relative lift target, alpha of 0.05, and 80% power?
How would you handle the novelty effect and potential seasonality imbalances between test and control groups?
If the primary metric shows no significant change but secondary engagement metrics improve, how do you interpret and communicate those results?

“I went with GMV per user as primary and latency plus user retention as guardrails.”

View Post

Snap·Data Scientist·Onsite - Behavioral / Leadership

Jun 2026

Snapchat data scientist behavioral round, pretty much one big meaty question about influencing a senior stakeholder when your A/B test data isn't giving you clean answers. Left feeling like I either nailed it or completely overexplained everything.

Tell me about a time you had to convince a senior leader from another team to change a launch plan when your A/B test results were ambiguous. Walk through the stakes, your hypothesis, how you set success metrics and guardrails, how you navigated disagreement, what artifacts you produced, the trade-offs you surfaced, the outcome, and what you'd do differently.

“This question is basically five questions stapled together and they want all of it.”

View Post

Snap·Software Engineer·Hiring Manager Screen

Jun 2026

Snapchat software engineer interview that had at least one business-context question, which felt more product-y than I expected for an engineering role.

Walk me through your current or most recent company's business model. Who are the customers, what does the product actually do for them, how does the company make money, and where does your team's work fit into all of that?

“I wasn't ready for this in a software engineering screen.”

View Post

Snap·Software Engineer·Technical Phone Screen

Jun 2026

Snapchat SWE interview with a classic LRU cache design question. Pretty standard for this type of role but the O(1) constraint is where things get interesting if you haven't thought it through before.

Design and implement an LRU cache data structure with get and put operations, both running in O(1) average time complexity.

“The get and put interface is straightforward but the O(1) requirement forces you toward a specific combo of a hashmap and a doubly linked list.”

View Post

Snap·Software Engineer·Technical Phone Screen

Jun 2026

Snapchat software engineer interview that was basically one big coding question: build a dynamic list from scratch, no standard library allowed. Straightforward premise but the discussion portion caught me more off guard than the actual coding.

Implement a dynamic List data structure from scratch using a fixed-size backing array, supporting add, get, set, remove, size, and contains operations, with automatic resizing when the array fills up.

“The coding part was fine, I got the basic structure down pretty quickly.”

View Post

Snap·Software Engineer·Technical Phone Screen

Jun 2026

Snapchat SWE interview with a coding round that put a spin on the classic LRU cache problem. Not the hardest interview I've done but the twist tripped me up more than I expected.

Design an LRU cache where each item has its own size and the cache has a fixed total capacity. Evict least-recently-used items one by one until there's enough room to insert. Support get (marks as recently used) and put (reject if item size alone exceeds capacity).

“I knew LRU cache cold, hashmap plus doubly linked list, move to front on access, evict from the tail.”

View Post

Snap·Technical Program Manager·Onsite - Behavioral / Leadership

Jun 2026

Onsite TPM loop at Snapchat focused on a full end-to-end project presentation with behavioral follow-ups around stakeholder conflict and lessons learned. Pretty standard for the role but the follow-up questions got specific fast.

Tell me about a time you worked with a difficult stakeholder.
Share a counterintuitive lesson you learned from a project you led.
What made the stakeholder difficult from their perspective, not yours?
How did you know the project was actually successful?
What mechanism did you put in place so the same stakeholder conflict wouldn't happen again?
If you ran that project again from scratch, what would you do differently?

“The part I fumbled was resisting the urge to frame the stakeholder as the problem.”

View Post

Snap·Software Engineer·Technical Phone Screen

Jun 2026

Snapchat software engineer interview with a short project deep-dive at the top. Pretty standard format but the 15-minute time box is tighter than it sounds when you're trying to cover problem, role, decisions, and results without rambling.

Walk me through a recent project you worked on: what was the problem, what was your specific role, what design decisions and trade-offs did you make, what were the technical challenges, and what were the results?

“15 minutes sounds like plenty until you're actually in it.”

View Post