Software Engineer applicants have rated the interview process at Snap with 3.3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 45% positive. To compare, the company-average is 46.1% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 19 days to get hired, when considering 156 user submitted interviews for this role. To compare, the hiring process at Snap overall takes an average of 26 days.
Common stages of the interview process at Snap as a Software Engineer according to 156 Glassdoor interviews include:
Phone interview: 41%
One on one interview: 23%
Skills test: 15%
Presentation: 9%
Group panel interview: 4%
Background check: 3%
Personality test: 1%
Drug test: 1%
IQ intelligence test: 1%
Other: 1%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 2 weeks. I interviewed at Snap (New York, NY) in Sep 2017
Interview
1. Call with recruiter: This was a pretty standard call with one of the recruiters. The conversation I had was very pleasant and the recruiter actually seemed to want to know more about me and my experiences. Nothing technical
2. Technical Google Hangout Interview: This was a pretty standard technical video screen with one of the engineers. We first discussed previous and projects I had worked on and what I was looking for in a role. Then had around thirty minutes to answer a coding problem. It was one I've never heard of before, but it wasn't too difficult. The question wasn't your average Cracking the Coding interview type question but it was definitely doable.
3. New York Office Project: The New York office does something different than in other locations so for this part of the interview it was project based rather than the typical superday. I was given a project right when I got to the office and was essentially given 5 hours to complete all of the tasks. Employees would come discuss my work with me every hour or so and there was a longer coffee break about half way through. I got 4/5 tasks of the projects complete, but I believe that you need to get all of them to get the job.
Overall awesome experience and great people!
Interview questions [1]
Question 1
Coding question that required a fundamental understanding of bit manipulation
One initial screening call. Then 1 coding screen. Then an on-site with 3 coding rounds and 1 system design round. All the rounds were pretty straightforward DSA patterns and SD was also a common question you read about in SD interview prep books.
Hard but interesting. Had to go through 1 HM round, 2 coding rounds and 2 systems design rounds. Coding round was hit counter, and message recommendation system. The System design rounds were a bit challenging.
Interview questions [1]
Question 1
Design a recommendation system for messaging to predict the next word while typing
For the technical rounds, I was asked leetcode style questions. Need to practice Data structures and algorithms in order to do well on the interviews. It's important to explain the code as you go along and clarfiy any questions with the interviewer.