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%
IQ intelligence test: 1%
Drug test: 1%
Personality test: 1%
Other: 1%
Here are the most commonly searched roles for interview reports -
I applied through an employee referral. The process took 6 weeks. I interviewed at Snap (Venice, CA) in Nov 2015
Interview
The process consists of online code challenge, phone screen, full-day onsite. The process can move really quickly, but it was actually me who was slowing it down. Recruiters are prompt to respond and their communications are very concise and efficient. For all interviews, a candidate is expected to write code that actually compiles and works in a timely fashion, so speediness and accuracy are both important. There is a designated building only for interviews, so it is hard to feel the actual culture at Snapchat, but all interviewers seemed like kick-ass developers and pretty easy going. Also, they seemed very passionate about the company and the work they do. One of the interviewers described Snapchat as a rocket ship at this stage, which I believe many people (including me) can agree. The culture in the area around Snapchat (Venice beach) is quite interesting though.
Interview questions [1]
Question 1
Design and write code for a given practical scenario related to snaps.
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.