Snap Software Engineer Phone Screen Questions
11+ questions from real Snap Software Engineer Phone Screen rounds, reported by candidates who interviewed there.
What does the Snap Phone Screen round test?
The Snap phone screen typically lasts 45-60 minutes and evaluates core Software Engineer fundamentals. Candidates should expect 1-2 algorithmic problems, basic system design discussion at senior levels, and questions about relevant experience. The goal is to confirm technical competence before bringing candidates onsite.
Top Topics in This Round
Snap Software Engineer Phone Screen Questions
**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 `
Snap phone screen | L5 | Reject
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...
Snap | Seattle | Phone
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...
Snapchat | Phone Screen | Senior SDE
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...
Snap | Onsite | Multiple questions
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
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...
Snapchat - Phone Interview - Reject
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...
Snap | SWE | LA | September 2021 [Reject]
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
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...
Snapchat | Phone screen | Detect deadlock
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...
What to Expect in the Snap Phone Screen Round
The Snap Software Engineer Phone Screen round has a specific calibration purpose distinct from other rounds in the loop. Across 11+ verified reports on LeakCode for this exact round type, the consistent expectations: clear scoping of the problem before diving into a solution, explicit reasoning about complexity, structured handling of edge cases, and the ability to discuss trade-offs between two reasonable approaches.
Reports tagged with the Phone Screen round at Snap show recurring patterns in difficulty and topic distribution. The Phone Screen round is typically 45-60 minutes; the interviewer is calibrated against a specific rubric. The discriminator between candidates who advance and candidates who do not is rarely the final correctness of the answer. It is the path: did you clarify, did you verbalize your approach, did you handle edge cases, and did you communicate throughout.
How To Prepare for This Specific Round
Filter the questions below to the most recent reports (past 6-12 months). Questions tagged for this exact round type from this exact company at this exact role level are the highest-signal data available. Older reports may reference questions that have since rotated out of the company's pool.
Practice 4-6 representative problems from this set under timed conditions. The goal is not memorization (companies rotate questions); the goal is to internalize the patterns the interviewer typically reaches for and the depth of follow-up to expect. Reports on LeakCode also tag the typical follow-up depth at this round type, which is the discriminating signal between hire and no-hire calibration.
Phone Screen Round Timing and Format
The Phone Screen round at Snap typically runs 45-60 minutes. Use the first 2-3 minutes to clarify requirements; you should never start coding or designing without verifying the input/output format, constraints, and edge cases out loud. Use the next 5-7 minutes to verbalize your approach before writing any code. The middle 20-30 minutes are implementation. Reserve the final 10 minutes for testing with concrete examples and discussing optimization or trade-offs.
Time budget discipline is one of the most reliable senior-vs-junior discriminators in this round. Strong candidates verbalize where they are in their budget out loud ("I've used about 20 minutes, I have 15 minutes left for testing and one optimization"). This signals engineering maturity to the interviewer and creates positive feedback they can capture in writing.
Common Failure Modes in This Round
Reports tagged "no hire" at Snap Software Engineer Phone Screen commonly cite: coding silently without verbalizing approach, jumping to implementation before clarifying requirements, missing edge cases (empty input, single element, very large input), producing working code that the candidate cannot refactor when asked, and failing to test their solution with concrete examples before declaring done.
The single most predictive failure mode in 2025-2026 reports: not asking clarifying questions. Interviewers at all FAANG companies are explicitly trained to weight this dimension. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's notes.
See All 11 Questions from This Round
Full question text, answer context, and frequency data for subscribers.
Get Access