Software Engineer applicants have rated the interview process at Snorkel AI with 3.3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 33% positive. To compare, the company-average is 35.3% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 1 day to get hired, when considering 3 user submitted interviews for this role. To compare, the hiring process at Snorkel AI overall takes an average of 17 days.
Common stages of the interview process at Snorkel AI as a Software Engineer according to 3 Glassdoor interviews include:
Skills test: 40%
Group panel interview: 40%
Phone interview: 20%
Here are the most commonly searched roles for interview reports -
I applied through other source. I interviewed at Snorkel AI in Jan 2025
Interview
Interview process was not quite the most optimal or mutually beneficial. All interviews had a "tricky" part to it, whether trying to validate the person or the skills.
Few interviewers were quiet young with only a fewer years of experience and I could sense they wanted me to rush and quickly get to the solution.
During the coding round the girl interviewing me was getting impatient with me asking questions and even told me to just get to the implementation fast,
Interview questions [1]
Question 1
DSA, HashMaps, stacks, heaps, queues and basic system design questions. You just need to be able to read the mind of the interviewer pretty well
Manager conversation, phone screen, virtual onsite. Virtual onsite: 2 coding, 1 design, 1 manager interview, 1 vp. I was able to take interview over 2 days. After 1 week hr responded that they are not going to offer.
Interview questions [1]
Question 1
Phone screen: coding question. Best if you can use python. I used java and took some time. Onsite: coding: 2 medium level leetcode questions.
I applied in-person. The process took 1 day. I interviewed at Snorkel AI (San Francisco, CA) in Jan 2021
Interview
I did a coding challenge and 2 coding interviews. They didn't seem to care too much about thought process. Speed was very important. You have to know your coding language very well and the concurrency primitives well as well.
Interview questions [1]
Question 1
Not allowed to reveal coding questions. Used stacks, queues, for loops, and a lot of maps.