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 a recruiter. The process took 4 weeks. I interviewed at Snap (Los Angeles, CA) in Jan 2016
Interview
Recruiter contacted me on LinkedIn. Talked with me over the phone for about 15 minutes, didn't even ask for my resume. Recruiter told me that all the communications will be done within 48 hours at each stage of the interview.
They set up a technical phone call interview.
The interviewer called about 15 minutes late. Asked a lot about my work, and kept stressing over what technical challenges I've faced. The coding question was straight forward, and I could complete it in 20-25 minutes. The remaining time, he asked me if I have any questions for him.
It has been 3 weeks, I still haven't heard from them, in spite of sending them a follow up email. Even if they're not moving forward, they should respond to candidate's email.
I have given interviews with Airbnb, Uber, Box and other good ones, but all the recruiters were very professional unlike Snapchat.
Interview questions [1]
Question 1
Basic graph traversal keeping track of visited nodes.
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.
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.
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