Real, anonymous reports from people who interviewed for Software Engineer at Snyk, newest first and distilled into what to expect across the loop.
I went through the early steps with a recruiter and the process felt oddly mismatched to what the role needed. After an initial recruiter conversation, I later re-engaged with a different recruiter who walked me through what the journey would look like. The explanation sounded patterned after bigger-company interview styles, with a team-matching step that felt excessive for a growth-stage environment.
My rounds were heavy on engineering assessments and felt more exacting than I expected. I started with a PR review task and a technical discussion. In my case, I’d covered what was needed so thoroughly that the reviewer wrapped up early with little to add, which made it feel like I was already past the stage they wanted from me. The next round went into a LeetCode-style problem with an encryption theme.
The interview process typically begins with a recruiter screen, followed by a hiring manager discussion, and then moves into technical evaluations including PR reviews and coding challenges. Candidates noted that the overall structure felt clear and organized, though some experienced delays and inconsistent communication.
Candidates faced a variety of technical rounds, including PR reviews, coding challenges, and system design interviews, with a strong focus on problem-solving and execution details. The difficulty level was generally perceived as demanding, with some candidates feeling judged harshly on minor mistakes.
Several candidates highlighted the importance of understanding Snyk's products and being able to communicate their value effectively, particularly during product demos and presentations. The interviews often included scenarios that required candidates to demonstrate customer-facing skills.
Interviews included behavioral questions aimed at assessing cultural fit, with emphasis on collaboration and communication styles. Candidates reported that these discussions were often framed around the company's values and expectations for teamwork.
The candidate experience varied significantly, with some reporting a supportive and respectful process, while others faced communication breakdowns and a lack of constructive feedback after interviews. Many candidates expressed disappointment over unclear outcomes and delays.
Logistical aspects of the interview process were noted as a potential source of frustration, with some candidates experiencing scheduling issues and delays that impacted their overall impression of the process. Consistency in communication was a recurring theme.