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%
Drug test: 1%
Personality test: 1%
IQ intelligence test: 1%
Other: 1%
Here are the most commonly searched roles for interview reports -
I interviewed at Snap (Los Angeles, CA) in Jun 2017
Interview
I was contacted by a Snapchat recruiter from their Los Angeles office. Following my phone conversation with him, I was scheduled for a technical phone interview.
The interview question had 2 parts. At first, my code was giving the wrong results due to a bug. I was able to fix it and finally all the tests passed.
Following that, I was so excited and I started preparing for the onsite. I was confident that they would invite me for an onsite. At my biggest surprise, I received an email saying that they decided not to move forward with my application. This was very shocking to me.
I then emailed the recruiter to ask if he didn't mind to tell me where I went wrong. I never heard back from him.
I wonder if they chose not to move forward with me due to cultural fit. Or may be they are looking for someone who can solve the question at first without a single bug.
Other than that, it was a great experience . Both the recruiter and the engineer who interviewed me were great and I enjoyed talking to both of them. I learned a lot about the company and I like what they do.
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