Kraken Interview Guide
Everything we know about interviewing at Kraken: the process stage by stage, what each round tests, compensation by level, and reports from candidates who interviewed.
Interviewing at Kraken
What the process looks like, and what Kraken is really testing for.
Kraken’s interviews are built around practical technical work plus conversations that force you to explain decisions. The strongest signals in the data are Problem Solving and Communication (explaining technical decisions), alongside Python and system design topics.
Across roles, you can expect evaluation that maps to Python, Django, take-home work, and system design. The topic set also heavily includes Security Engineering and product-style thinking, plus Data Analysis and Data Engineering in the roles where those are relevant, with documentation and trade-offs showing up as explicit evaluation themes.
The process you experience will typically include recruiter screening and then one or more technical stages where you either complete an assignment and defend it, or go through a scenario and discuss your approach. Candidate reports show time windows often described as a few hours for take-home, and multiple reports describe timelines that span weeks with sometimes unclear next steps after submission.
Your output is evaluated heavily on your ability to explain trade-offs and document assumptions, not just on making the code work. Multiple candidate reports describe frustration when written requirements and feedback did not match what they delivered, so make your assumptions and scope boundaries very explicit.
The Kraken interview process
5 stages, based on 129 candidate reports.
Recruiter screening
Varies by candidateYou start with a recruiter call or recruiter screen to clarify your background and the role, and in some cases visa sponsorship requirements. Prepare a crisp summary of what you have done, why you are interested, and your motivations, since this is part of the early screening themes.
Practical assessments: coding or take-home
A few hours, often described as 3-6 hoursYou complete a practical technical evaluation, commonly a Python coding challenge and or a take-home assignment. Candidate reports frequently describe work that uses Python and Django, includes ambiguity, and expects you to document assumptions and scope boundaries.
Technical defense and discussion
Varies by candidateAfter submission, you typically discuss your solution with technical interviewers and may have a panel review where you present and defend the work. Expect questions about your implementation choices, trade-offs, and how the solution could be extended, plus the ability to explain clearly.
Manager or leadership and culture fit conversations
Varies by candidateYou meet with hiring managers or senior management for a mix of behavioral and technical context. Some reports and steps indicate final leadership and culture fit evaluation, and there are also mentions of product and long-term alignment conversations such as a final conversation with a Head of Analytics in at least one reported path.
Offer stage
After successful completion of all interview stagesIf you pass the prior stages, there is a final offer stage discussion. The dataset here reports an offer rate of 0.0%, so treat the rest of your preparation as about maximizing your ability to match the expectations you will be asked to defend.
What Kraken evaluates
How often each skill shows up across reported interview loops.
Interview guides by role
Each guide has the questions Kraken interviewers actually ask, the loop structure, and total compensation by level.
What Kraken pays, by level
Estimated total compensation: base salary plus stock and annual cash bonus.
Insider tips
Patterns from candidates who got offers, and the mistakes that most often sink a loop.
Real interview experiences by role
Read what candidates said about interviewing at Kraken: the loop, difficulty, and outcomes, straight from recent reports for each role.
Kraken interview FAQ
Answered from real candidate and workplace data, marked up for rich results.
What people say about Kraken
Verbatim snippets pulled from employee and candidate reviews.
Leadership communication needs improvement, as it can often be poorly handled.
Colleagues are kind and compassionate, creating a supportive work environment.
Decision-making in the UK lacks transparency, and those outside Europe may miss critical updates as the company navigates asynchronous remote work.
Increased transparency is essential; the culture should return to open discussions rather than secretive decision-making that fosters a toxic atmosphere.
Given the current market, London remains the hub for key decisions.
Kraken offers significant autonomy and freedom in problem-solving, along with strong support for technical learning and collaboration with talented individuals from around the globe.
Related company guides
Companies that hire for the same data roles, with the same depth of prep.
