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 (Seattle, WA) in Apr 2018
Interview
The interview questions is a hard-level question in leetcode but not unsolvable. The interviewer almost not talkign the entire time showing no interest of the candidate. After solving the problem, the interviewer doesn't ask to run the code but instead asking if have any question for him so he can finish the interview even when there's still time left for the interview.
Get a response within two days saying they don't find a match for the position. This seems to be the same experience for many others in the last few months after Snap went to IPO, especially as they start the laying off process.
The advice is don't apply for snapchat if you have other opportunities. They intend to ask the hard-level question and not intend to really hire generic engineer unless you are a special need for them. I have heard from an internal engineer that their recruiter has asked them to make the question harder so they have a better reason to reject the candidate. Overall, an awful company to apply.
Interview questions [1]
Question 1
You don't have to run your code and you can stop now, do you have any question for me before we end this interview?
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.