Snap Software Engineer interviews, as candidates describe them, run from a recruiter call and short coding screen to a multi-interview onsite. They mix medium-level coding, behavioral questions, some design and C++ or frontend topics.
$168K
Avg. Base Comp
$394K
Avg. Total Comp
2-7 rounds
Typical Rounds
Not reported
Process Length
Candidates describe Snap's software engineer interviews as a recruiter call, a short technical screen and then, for those who advance, an onsite of several back-to-back interviews. The common thread is medium-level, LeetCode-style coding with a behavioral component attached.
One candidate had a 60-minute screen split into about 15 minutes of behavioral questions and 45 minutes of coding. Their problem was a string task: reversing the words in a sentence. Another candidate described 45-minute technical rounds, each with roughly 15 minutes of behavioral discussion tied to Snap's values, and called the questions medium with follow-ups. A third described Snap's SAIL framework appearing alongside the technical questions.
Topics vary by team. Reports include graph traversal on a matrix, a Manhattan-distance location problem, and other graph and data-structure problems. One C++ candidate was asked about threading and std::forward versus std::move. Others mentioned designing a chat system, a frontend heatmap component, and a project deep dive with slides. Several candidates said interviewers were friendly, but one described a disengaged interviewer, so keep explaining your reasoning clearly.
Timing can be slow. One candidate applied in mid-December and heard a rejection in early April, with little recruiter follow-up between rounds. Most of the shared experiences ended without an offer, and one candidate reported accepting. Confirm the role's location early, since one candidate learned on the recruiter call that no roles existed in the city listed.
Synthesized from 8 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Snap Inc. process.
C++ Trivia followed by flood fill algorithm question. Trivia included RAII, exception handling etc. Flood fill algorithm was a modification where you identify the shape of the island and only count unique islands
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Snap Inc.
Given two sorted lists, write a function to merge them into one sorted list.
| Question | |
|---|---|
| Permutation Palindrome | |
| Liked Pages | |
| Hurdles In Data Projects | |
| Ad Comments | |
| Multi-Modal AI Tool | |
| Page Recommendations | |
| Matrix Multiplication | |
| Green Dot | |
| Optimal Host | |
| John's New Best Friend | |
| f(x,y) in Interval | |
| k-Means from Scratch | |
| Dropbox Database | |
| Employee Salaries | |
| 2nd Highest Salary | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Weighted Keys | |
| Top 3 Users | |
| Raining in Seattle | |
| Comments Histogram | |
| Like Tracker | |
| Random SQL Sample | |
| P-value to a Layman | |
| Flight Records | |
| Largest Salary by Department | |
| Google Maps Improvement |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report a short recruiter conversation that covers the role and the process. One candidate described it as a quick check on who they were and what to expect. Another learned that no roles existed in the city listed in the posting, so confirm location fit early.
Candidates typically describe a screen of about 45 to 60 minutes with a brief behavioral segment followed by a LeetCode-style problem. One reported example is reversing the words in a sentence. One C++ candidate had a one-hour manager call with theory questions on threading and std::forward versus std::move. Not fully solving the problem may end the process.
Candidates report loops of about four to five interviews, each 45 to 60 minutes. Reported topics include graph traversal on a matrix, Manhattan-distance problems and other graph and data-structure questions. Some candidates also described design work such as a chat system or a frontend heatmap component. Expect follow-up questions after a working solution.
Behavioral questions appear to be woven into the technical rounds rather than held separately. Candidates mention questions about past mistakes, challenges, and Snap's values or SAIL framework. Some also describe a project presentation or deep dive, so prepare concise stories that show your role and collaboration.
Most candidates in these reports did not receive offers, though one reported accepting. Communication varied. One candidate went from a mid-December application to an early-April rejection, with little recruiter contact between rounds, so you may need to follow up proactively with your recruiter.
