
Snyk Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 160 interview experiences · FREE TO READ
Which role are you interviewing for?
30 roles · 160 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Snyk.
Technical Support Engineer
The interview process started with a recruiter call to discuss my interest in the company, salary expectations, and past employment. This was followed by a take-home exam where I had to use their product on a sample project and document my findings. Then, there were several interviews: one with the Technical Support Director, followed by two interviews with the Technical Support Manager, the second of which focused more on technical questions and problem-solving skills. The process concluded with a background check/referral and an offer. The interviews were all conducted over Zoom, but everyone was really nice and professional, making it feel more like a conversation. They provided a lot of detail about the role and the company, highlighting why it's a great place to work, and everyone seemed genuinely passionate. The recruiter was also very professional, following up and scheduling the next interview within 2-4 days.
- Given three switches controlling three bulbs in another room, and you can only enter the bulb room once without external equipment, how would you determine which switch controls which bulb?
Senior Software Engineer
The process felt progressive on paper, starting with a talent partner chat, followed by a take-home PR review focused on dependency trees, which was a good challenge. Then, two engineers reviewed the PR, discussed comments, and had me implement something related to it, which was described as a pair programming interview. However, the feedback was contradictory; despite things going well and discussing an edge case during the session, I was rejected for not including it initially within the 30 minutes. We also ran over time due to system design questions, which should be saved for a dedicated interview. The 'pair programming' felt more like an exam requiring perfection. Rejecting candidates for a single edge case seems counterproductive. There was also a disconnect between the TA partner emphasizing testing and the engineers not prioritizing it, each wanting different fixes. While the foundation for a good process exists, the engineering team seems unmotivated and looking for reasons to reject candidates. Internal training for engineers on interviewing could improve the experience.
- Can you review this PR regarding dependency trees?
- Following my feedback, which is the most critical issue you'd address and fix?
- What are the subsequent steps you'd take to deploy this to production?
Demand Marketing Manager
The Snyk hiring process lacked integrity, structure, and professionalism, making it one of the most disappointing interview experiences I’ve had. The entire process—from application to formal rejection—took 52 days, filled with poor communication, disorganization, and a clear lack of respect for candidates’ time and expertise. I initially applied through the company website after seeing the role on LinkedIn. The recruiter reached out with a generic scheduling link, offering no personalization or meaningful engagement. During the Zoom interview, it became clear that the recruiter was not engaged, lacked depth in technical recruiting, and had not reviewed my resume in detail. The questions were generic and uninspired, making it feel like a check-the-box exercise rather than a real attempt to assess my fit for the role. One notable red flag: despite the role being advertised as remote, the recruiter explicitly stated they would always prioritize candidates local to Boston—a contradiction that called into question the company’s transparency. A week later, I interviewed with the hiring manager, which only reinforced my concerns. The conversation felt more like an attempt to extract free marketing strategy and industry insights rather than a legitimate interview. It became evident that my expertise exceeded their expectations and, in some cases, even the hiring manager’s experience. Up to that point, I was told they were still in the early stages of interviewing, yet my two follow-ups over the next few weeks were completely ignored. The silence confirmed my instincts—this company was either using the hiring process to collect competitive insights or was so disorganized that they failed to manage basic candidate communication. Weeks later, completely out of the blue, I received a cold and impersonal rejection email from a senior recruiter, stating that while they were impressed with my background, they had moved forward with a candidate much further along in the process—which directly contradicted what I had been told earlier. Overall, this experience was a waste of time and a display of poor hiring ethics. If you are considering applying to Snyk, be prepared for disorganization, ghosting, and the possibility that your interview is just a thinly veiled attempt to mine free consulting work. Proceed with caution.
- Could you describe an instance where you executed a 1:1 ABM strategy?
- Can you provide an example of a successful program you have led?
- Please discuss the webinar strategy overhaul that you implemented.
Senior Manager, User Documentation
I started with a 30-minute call with the recruiter, then had a 45-minute session with the hiring manager. After that, there was a panel interview with 8 people. The panel interview was a bit messy because the main contact was late, which made things awkward at the start. I suggested we begin to save time, but it was disruptive when the main person finally joined. The recruiter had mentioned in the agenda that after a presentation, I'd speak with two Sr. Tech Writers. But instead, everyone stayed on the call and started a Q&A with me. It was tough handling questions from 8 people, with each asking 2-3 questions. We ran over time, and I didn't get to ask any questions, which was a bummer. Some questions felt a bit off, like the one about my knowledge of 'docs as code'. I see it as a technical authoring thing, not knowledge management, so it was unexpected. Also, one interviewer made me uncomfortable by bragging about her consultancy and how she was asked to stay on at Snyk because she was 'so good'. It felt unnecessary and egotistical. The first two stages were good, but the third one soured the experience. I haven't heard back, so I guess I'm being ghosted. Really disappointing.
- What are your views on the 'docs as code' approach?
- Can you describe how to build a successful team?
Snyk Interview Questions
Quoted word for word from Snyk interview reports.
“Implement a recursive function to print all Fibonacci elements up to two given consecutive elements (an-1, an).”
Read reports →“Can you explain what FileVault is and how to enable or disable it?”
Read reports →“Given three switches controlling three bulbs in another room, and you can only enter the bulb room once without external equipment, how would you determine which switch controls which bulb?”
Read reports →“Could you write a program to display the npm package dependency tree?”
Read reports →“Could you review the provided PR that constructs an NPM dependency tree?”
Read report →“Could you build an API that takes a package from a common package manager, traverses its dependency graph, and outputs it in a readable format?”
Read report →“Could you review this pull request for a project that builds an NPM dependency tree, and then suggest improvements or fix it?”
Read report →“Given a repository with code vulnerabilities, identify them and propose solutions for fixing them.”
Read report →“How would you approach designing an ingestion pipeline for vulnerability databases, considering merging and compaction?”
Read report →Formats, difficulty and experience
Across all 160 Snyk interview reports.