Real, anonymous reports from people who interviewed for Software Engineer at Snap, newest first and distilled into what to expect across the loop.
I went through a very concentrated coding day they called “snapfest.” After the recruiter process that kicked everything off, I showed up for two back-to-back rounds, each about an hour, and the whole thing felt like a single block of interviews rather than separate stages spread out over days. Both rounds were LeetCode-style medium problems.
My process started with the kinds of prompts that quickly made it clear this wasn’t going to be purely “find the trick” coding. In the technical portion, I was given LeetCode-style questions and was expected to talk through my thinking as I went, including clarifying any parts of the prompt I wasn’t sure about before I jumped into code.
The interview process typically starts with a recruiter call, followed by a technical screen, and culminates in an onsite loop that can include multiple back-to-back rounds. The overall timeline can vary, with some candidates experiencing a swift process of less than four weeks, while others faced delays and communication issues.
Candidates can expect multiple coding rounds featuring LeetCode-style problems that range from medium to hard difficulty, often emphasizing clean code and problem-solving speed. Interviewers are generally supportive, guiding candidates through challenges rather than creating a combative atmosphere.
In addition to coding, candidates often face system design rounds that can be particularly challenging and require a deep understanding of architecture and operational realities. These rounds assess not only technical skills but also the ability to handle complex, real-world scenarios.
Behavioral interviews are integrated into the process, focusing on candidates' experiences and how they handle pressure, team dynamics, and real-world constraints. This component is treated seriously and is essential for assessing cultural fit within the company.
While many candidates report a positive and professional atmosphere during interviews, some express frustration over poor communication and lack of feedback post-interview. This inconsistency can impact the overall candidate experience, especially regarding closure after the process.
The overall difficulty of the interview process is perceived as high, with candidates often feeling challenged yet supported. Many express that the experience is structured and fair, though the pressure can be intense, particularly in technical and design rounds.