Snap Inc. Software Engineer interview typically runs 4 rounds: recruiter call, technical screen, hiring manager/team interviews, and onsite. The process usually takes a few weeks to months and is conversational, with behavioral mixed into technical rounds.
$118K
Avg. Base Comp
$262K
Avg. Total Comp
4-6
Typical Rounds
3-12 weeks
Process Length
We’ve seen Snap evaluate software engineers less like pure algorithm grinders and more like builders who can reason about a consumer product. Multiple candidates described the interviews as conversational, with interviewers probing how they think through tradeoffs for a Snap feature, how they’d approach the broader app ecosystem, and whether they can connect their work to real user behavior. That pattern shows up even when the coding is straightforward: the bar is often about clear reasoning under pressure and whether you can explain why your approach fits the product, not just whether you can land on an answer.
Another recurring theme is that Snap seems comfortable using medium-level coding as a filter, but it expects follow-up depth. Our candidates report string manipulation, graph traversal, file-system style design, and even a Manhattan-distance placement problem — none of them were described as brutal, but several had edge cases or follow-ups that separated a clean pass from a shaky one. We also noticed that behavioral prompts are woven into technical conversations, often around mistakes, challenges, or prior projects, so the strongest candidates came prepared with concrete examples rather than polished talking points.
The non-obvious make-or-break factor is fit for the actual role and team context. One candidate learned late that the listed city had no open roles, and another was asked to prepare slides for a project deep dive, which made the process feel more formal and cross-functional than expected. Taken together, our candidates’ experiences suggest Snap is looking for engineers who can code competently, but also communicate crisply, stay product-aware, and handle a process where context matters as much as correctness.
Synthetized from 4 candidates 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 | |
| Page Recommendations | |
| 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 | |
| Weighted Keys | |
| Comments Histogram | |
| Raining in Seattle | |
| Top 3 Users | |
| Random SQL Sample | |
| Like Tracker | |
| P-value to a Layman | |
| Largest Salary by Department | |
| User Experience Percentage | |
| Over-Budget Projects | |
| Job Recommendation | |
| Scrambled Tickets | |
| Last Transaction |
Synthesized from candidate reports. Individual experiences may vary.
An initial recruiter call to confirm basic fit, location availability, and that you understand the interview process. In some cases this call was very quick and mostly logistical, while in others it also included early discussion of experience and system design background.
A short technical interview that typically starts with about 15 minutes of behavioral questions followed by 45 minutes of coding. The coding problems were usually LeetCode-style and ranged from easy to medium, with follow-ups and edge cases mattering a lot.
Virtual conversations with a hiring manager or team members that mix technical discussion with behavioral and product-thinking questions. Candidates were asked about tradeoffs for Snap features, prior projects, and how they handle challenges, mistakes, and collaboration.
A final loop made up of multiple back-to-back interviews, usually around four rounds of 45 minutes to an hour each. The loop included coding, system design, and sometimes frontend-style or project deep-dive work, with behavioral questions woven into every technical round.
After the onsite loop, recruiting followed up with the outcome. Some candidates heard back quickly, while others experienced a much longer delay between rounds and the final decision.