Real, anonymous reports from people who interviewed for Software Engineer at Kraken Digital Asset Exchange, newest first and distilled into what to expect across the loop.
I interviewed for a Software Engineer role at Kraken with a fairly steady, recruiter-led timeline, combining take-home work, technical follow-ups, and system design.
I interviewed for a frontend-focused Software Engineer role and found the process smooth, respectful, and relatively light overall.
The interview process typically begins with a recruiter-led screening call to discuss the candidate's background, expectations, and cultural fit. This step is generally described as straightforward and respectful.
Candidates are often required to complete a take-home coding assignment, which can vary in complexity and clarity. Some found the tasks to be more extensive than expected, with mixed experiences regarding follow-up discussions on the submissions.
The technical interview rounds focus on coding skills, system design, and language-specific depth, often including discussions about the take-home assignment. Candidates should prepare for both practical coding tasks and theoretical system design questions.
Behavioral interviews assess cultural fit and working style, often occurring towards the end of the process. Candidates should expect questions that explore past experiences and alignment with company values.
The final stages may include discussions with hiring managers and team leads, where fit and expectations are further evaluated. Candidates noted that even strong performances in earlier rounds could lead to unexpected outcomes, including rejections.
Candidates experienced varying levels of communication throughout the process, with some reporting delays and unclear feedback after interviews. Clear and timely communication is crucial for a positive experience.