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 -
The role is called "Software Engineer, ML CV". The first is recruiter screen, typical why snapchat, why change role etc. The second was a phone screen only on Computer Vision questions.
Interview questions [1]
Question 1
Tell me about your most challenging project and what you did in it?
How would you compare similarity between two images? (siamese network/one shot learning)
What are GANs? What are the losses involved in GANs for both discriminator and generator? How does backprop flow for GANs? (read google developers GAN intro)
Given an old model and you have a new model, and both models return the prob for each pixel that it is a human or not, how would you determine the quality of the two models? What if the test data is very hard or very easy, how would that change your test result? (IoU, Dice coefficient, Pixel accuracy)
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.