Software Engineer applicants have rated the interview process at Snyk with 2.9 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 42% positive. To compare, the company-average is 60% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 21 days to get hired, when considering 19 user submitted interviews for this role. To compare, the hiring process at Snyk overall takes an average of 24 days.
Common stages of the interview process at Snyk as a Software Engineer according to 19 Glassdoor interviews include:
Phone interview: 21%
One on one interview: 21%
Skills test: 21%
Background check: 8%
Other: 8%
Presentation: 8%
Group panel interview: 5%
Personality test: 5%
IQ intelligence test: 3%
Here are the most commonly searched roles for interview reports -
I applied through a staffing agency. The process took 3 weeks. I interviewed at Snyk (London, England) in Oct 2020
Interview
Recruiter reached out to me on hired.com, we organised initial phone screen calls which were fine. They sounded genuine and interested.
Reaching the technical interview stage... the communication was poor. The recruiters took an age to respond back and when they did organise the interviews for the review, the reviewers didn't even turn up!!!
Had to keep asking emailing them and asking them for clarification on things and the communication was so appalling.
They rescheduled for 2 interviews; 1st one didn't go so well. They did not message me about the 2nd interview until 5 minutes AFTER the interview was scheduled to start.
Waste of time, no respect for other people's time and the lack of communication in this company was very evident. Bullet dodged.
Interview questions [1]
Question 1
Dependency technical interview, asking about web application, tests, asynchronous calls and caching methods
The interviews in theory are a goof structure but as others have said the interviewers suck.
One was a basic pr review, finished it early they had no notes because I had touched upon everything plus bugs they didn't even realise existed.
Second interview was a small leetcode style problem involving encryption. When I started the interview I had my shell open and was previously using poetry to run my scripts and tried to do this from muscle memory then literally straight after I ran the correct python command to run a script, the feedback: "you did not know that you could run a python file using the command: "python ".", literally marked down because of muscle memory and typing a standard command to run python. They also turned it into a math test when I couldn't figure out the remainder of 13/90 (not the real numbers but a valid representation) WITHOUT A CALCULATOR, I asked if I could just run my function to get the answer and he said it would be CHEATING, since when is running your own code to see output cheating, their feedback: "There were some issues with basic math", I asked a friend who solely studied math and works as a data scientist this question and he got it wrong. These interviewers clearly have just looked at this problem before and know the answers. My code worked in the alotted time but apparently this was a math test. The interviewers from the pr review were nice though and the structure in theory is good, just engineers who expect perfection no typing errors, no math mistakes, not important if the code works.
Initial HR Interview (Half Completed):
Had a brief conversation with HR as part of the initial screening.
Technical Interview (PR Review Task):
The expected process included receiving a pull request (PR) to review ahead of a 45-minute technical discussion. Unfortunately, I wasn’t sent the PR in advance and assumed it would be done live. As a result, the interview was not conducted, and I was told it would be rescheduled. However, HR did not follow up, and the process stalled unexpectedly — suggesting a miscommunication or issue in the recruitment process.
Interview questions [1]
Question 1
what is your experience, why do you want to work here.
One interview with hr and one technical interview. The technical interview didn't include a live coding section. At the time they were looking for people in a certain location to work hybrid, so I didn't match the requirement