Snap

Snap Software Engineer Interview Questions

86+ questions from real Snap Software Engineer interviews, reported by candidates.

86
Questions
6
Round Types
8
Topic Areas
2016-2026
Year Range

Round Types

Coding 66 Phone Screen 11 Technical 3 System Design 1 Recruiter 1 Onsite 1

Top Topics

Questions

The interview started with around 10–15 minutes of background discussion, where the interviewer asked about my experience — especially around backend systems and ML-related work. After that, we moved

**Problem Statement** Implement Java's `Math.sin(x)` function using the Taylor Series expansion: $$x - \frac{x^3}{3!} + \frac{x^5}{5!} - \frac{x^7}{7!} \dots$$ **Challenges** 1. **Termination:** The T

**Problem Statement** You are given an array `rooms` where each element represents the capacity of a meeting room, and an integer `k` representing the number of people. The goal is to distribute all `

Hi, I had a phone screen with snap today. Here is the question i was asked. Image region with sum Write code which determines whether the sum of all elements in a...

Connect Pairs (from hacker rank) Input : [Ba, _a, cb, dc] output : _abcd Input : [El, ll, lo, _h, he] output : hello condition : the resultant string should begin with In...

Snap | Seattle | Phone

Phone Screen 2024

Interviewed with Snapchat a few days ago Phone Interview: Given a list of strings find if the word is prefix of any word Example: [\'world\', \'word\', \'would\', \'wont\', \'which\', \'hello\'] prefix : \'wo\' I started...

Given a mxn Binary matrix print the shortest path from start to end. Start can be any point in the first row and end can be any point in the...

One of the strangest experiences I\'ve had. Maybe I dogged a bullet. The interviewer was nice and helpful. It started with a behavioral question. Tell me about a time you had a disagreement...

How to system design a messenger with this feature? Auto delete/vanish of message/Photo after read

Given an R x C grid of letters "P", "F", and ".", you have one person "P" and his friends "F". The person will go visit all his friends and can...

Phone interview \t\tWhy snap? \t\tGiven grid of Babies and Toys, place Nanny at optimal distance from all babies \t\tBest Meeting Point - LeetCode 1. Manager round \tValue based questions \tDesign chess, discuss entities and modelling...

Snapchat Phone Screen

Phone Screen 2021

Question - Design a class/method AddAndGetTopK to add a number and get top K frequent elements. Eg - k = 3 4 4,5 4,5,4 => 4,5 4,5,4,6 => 4,5,6 4,5,4,6,5 => 4,5,6 4,5,4,6,5,7 => 4,5,6 4,5,4,6,5,7,7 => 4,5,7 I...

Behavioral: - Why Snap? - Talk about a past mistake Coding: https://leetcode.com/problems/palindrome-linked-list/ However, the ListNode was generic but based on the question requirement I used integer as value of each node. After clarifying questions, I explaned...

Status: 4 YOE Position: L4 SDE at Amazon Location: LA, CA Date: September 2021 Technical phone screen (1 hour): \t https://leetcode.com/problems/combination-sum/ \t* Follow-ups: \t\t https://leetcode.com/problems/combination-sum-ii/ \t\t https://leetcode.com/problems/combination-sum-iii/ * Virtual Onsite: \t Coding: \t\t https://leetcode.com/problems/letter-combinations-of-a-phone-number/ \t\t* https://leetcode.com/problems/decode-ways/ \t* Behavioral \t*...

Snap | NYC | Phone

Phone Screen 2020

Interviewed with Snapchat a few months ago Phone Interview: Given a list of strings and a regex like string return all strings that match Example: [\'world\', \'word\', \'would\', \'wont\', \'which\', \'hello\'] \'w3d\' Would return \'world\' and...

Three columns inside log file generated by single thread CPU, assuming input is Entry(String jobName, boolean start, int timeStamp), output is HashMap<String, List<Interval>> write a parse function to parse log file....

We are given a list of words that have both 'simple' and 'compound' words in them. Write an algorithm that prints out a list of words without the compound words...

We obtained a log file containing runtime information about all threads and mutex locks of a user program. The log file contains N lines of triplets about threads acquiring or...

LeetCode #347: Top K Frequent Elements. Difficulty: Medium. Topics: Array, Hash Table, Divide and Conquer, Sorting, Heap (Priority Queue), Bucket Sort, Counting, Quickselect. Asked at Snap in the last 6 months.

LeetCode #200: Number of Islands. Difficulty: Medium. Topics: Array, Depth-First Search, Breadth-First Search, Union-Find, Matrix. Asked at Snap in the last 6 months.

What Snap Looks for in Software Engineer Interviews

Snap Software Engineer interviews are calibrated against the level and scope expected of the role. Across 86+ verified candidate reports on LeakCode, the consistent signals interviewers look for: clear problem decomposition before coding, explicit complexity reasoning, structured handling of edge cases, and the ability to articulate trade-offs between two reasonable approaches.

The discriminator between candidates who advance and candidates who do not is rarely the final correctness of the solution. It is the path to the solution: did you ask clarifying questions, did you state your approach before coding, did you handle edge cases without prompting, and did you communicate your reasoning throughout. Reports tagged "no hire" frequently cite a working solution with poor communication; reports tagged "strong hire" cite clear thinking even when the final solution was incomplete.

How To Use This Question Set

Real interview reports are a calibration tool, not a memorization target. Companies update their question pools every 2-4 months; memorizing exact problems risks misleading you when the interviewer uses a variant. The high-leverage use: identify the patterns that appear repeatedly in Snap Software Engineer reports, practice those patterns on similar (not identical) problems, and use the reports to understand the interviewer's typical follow-up depth.

Filter the questions below by round type, difficulty, and recency. Focus first on reports from the past 6-12 months; older reports may reference questions that have since rotated out of Snap's pool. Reports tagged with quantified difficulty (e.g., "medium-hard") are higher-signal than reports without difficulty tags.

Round-by-Round Expectations

Snap Software Engineer loops typically span 4-6 rounds across phone screens and on-site or virtual on-site interviews. The structure varies by company: some run 1 recruiter screen + 1 technical phone + 3-4 on-site rounds; others run 1 recruiter screen + 1 OA + 4-5 on-site rounds. The recruiter screen is logistics and culture-light; the technical phone screen is medium-difficulty coding; the on-site loop covers coding, system design (at L4+ levels), and behavioral rounds.

Each round is designed to surface a specific signal. Coding rounds: correctness, code quality, complexity reasoning, communication. System design rounds: requirements clarification, design judgment, operational thinking. Behavioral rounds: ownership scope, leadership, ambiguity tolerance, conflict navigation. Strong candidates explicitly hit each signal dimension out loud during the round; weak candidates focus only on solving the prompt.

Common Interview Mistakes At This Combination

Reports tagged "no hire" at Snap Software Engineer commonly cite: jumping into code without clarifying requirements, coding silently for 10+ minutes without verbalizing approach, missing edge cases (empty input, single element, very large input, overflow), and producing a working solution that the candidate cannot explain or refactor when probed. Strong candidates avoid these patterns by following a consistent template: clarify, verbalize approach, code with narration, test with examples.

Behavioral and design rounds have their own failure modes. Behavioral: stories that use "we" instead of "I" diluting individual signal, stories with no quantified outcome, defensiveness when probed about failure. Design: not asking clarifying questions, not stating requirements out loud, designing for a single server when the prompt clearly implies scale, ignoring operational concerns (deployment, monitoring, rollback). These show up in roughly half of Snap Software Engineer interview retrospectives on LeakCode.

See All 86 Snap Software Engineer Questions

Full question text, answer context, and frequency data for subscribers.

Get Access