Snap software engineer candidates report a recruiter conversation, a coding-focused technical screen, and in some cases a multi-interviewer final loop. Prepare for behavioral discussion alongside coding, plus possible design or frontend work.
$200K
Avg. Base Comp
$522K
Avg. Total Comp
5-6 rounds
Typical Rounds
4 months
Process Length
Snap software engineer reports point to a process that begins with recruiter contact and moves quickly into technical evaluation. One candidate described a 60-minute screen split between roughly 15 minutes of behavioral discussion and 45 minutes of coding; the reported prompt involved reversing word order, while another candidate mentioned merging sorted arrays. Be ready to explain projects, a mistake, or how you handle challenges before coding begins.
Coding is the most consistently reported technical theme. Candidates described LeetCode-style questions with follow-ups, including UTF-8 string iteration in C/C++, matrix-represented graph traversal, Manhattan-distance optimization, and file-system arrangement. Reports differ on difficulty: one candidate characterized coding as easy to medium, while another described medium problems with follow-ups. Practice reaching a correct implementation while narrating edge cases, complexity, and tradeoffs.
Several reports also describe a longer final loop. One Software Engineer - Display Test candidate reported four onsite sessions over about six hours, including system design, a project deep dive with slides, and a frontend heatmap component. Another SDE candidate reported multiple technical conversations and a behavioral discussion tied to prior experience and company values. Treat those format details as role- and team-dependent rather than universal. The only explicit end-to-end timeline in these reports ran from a mid-December application to an early-April decision.
Synthesized from 4 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.
The hardest part of my Snap interview was realizing the process was a lot more conversational than I expected. I went in thinking I’d be facing leet code hard problems, but the interviews were mostly medium-level coding questions with follow-ups, and the interviewers were friendly and chatty throughout. My process started with a recruiter call, and that was where I learned something important: even though my city was listed in the job description, there actually weren’t any roles there. After that, I had a technical screen, and the rest of the loop was structured as one 45-minute tech round with about 15 minutes of behavioral, followed by a final onsite that had three more 45-minute technical rounds and another 15-minute behavioral conversation.
The coding questions were all in the usual leetcode style, but each one had follow-ups, so it wasn’t enough to just get to a working solution. One question I remember was about finding the best place for a shop using Manhattan distance, which felt more like a medium than anything truly brutal. The system design portion was also part of the process, and I was asked about my years of experience with system design early on, so that came up as a screening topic rather than a deep architecture exercise. The behavioral questions were tied to prior experience and Snap’s values, so I made sure to have concrete examples ready. Overall, the interviews felt fair and manageable if you were prepared for medium-level coding, some design discussion, and a lot of follow-up questions. In the end I was accepted, but the recruiter call was a reminder to confirm location fit before getting too far in.
Prep tip from this candidate
Expect medium-level LeetCode-style coding with follow-ups, not true hard problems, and be ready for a Manhattan-distance location problem. Also prepare a concise system design summary of your experience and examples that map to company values for the behavioral rounds.
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 | |
| Empty Neighborhoods | |
| Subscription Overlap | |
| 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 | |
| Largest Salary by Department | |
| Google Maps Improvement | |
| User Experience Percentage |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an initial recruiter call or screen. One report described this as brief and focused on confirming candidacy and process understanding; another raised location fit during that conversation. Prepare a concise overview of your background and role preferences.
Candidates report a coding-focused screen, sometimes with behavioral questions at the start. Reported examples include reversing words in a sentence, merging sorted arrays, and a Manhattan-distance problem. Expect follow-up questions and communicate edge cases and complexity as you work.
Some candidates report a multi-interviewer final loop with technical rounds, behavioral discussion, and possible system-design, project-deep-dive, or frontend work. One report described four onsite sessions across roughly six hours, so format may vary by team and specialty.
