Software Engineer applicants have rated the interview process at Kraken with 2.8 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 50% positive. To compare, the company-average is 57.7% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 30 days to get hired, when considering 4 user submitted interviews for this role. To compare, the hiring process at Kraken overall takes an average of 25 days.
Common stages of the interview process at Kraken as a Software Engineer according to 4 Glassdoor interviews include:
Background check: 17%
Group panel interview: 17%
Phone interview: 17%
Personality test: 17%
One on one interview: 17%
Skills test: 17%
Here are the most commonly searched roles for interview reports -
I applied through a recruiter. The process took 8 weeks. I interviewed at Kraken (London, England) in Feb 2024
Interview
The interview process was extremely challenging; I don’t mean this in a bad way but there standards were obviously extremely high. The fact that it was this way though makes me feel extremely proud that I got an offer, and makes me feel like I deserved it. It is going to make me cherish the job all the more.
I was going in at entry level or Software Engineer I position. I had an initial screening interview. As well as being extremely kind, the recruiter was incredibly helpful at telling me what to prepare for the technical test, and was an incredible recruiter who saw the best in me, realised my potential, and was incredibly helpful, supportive and encouraging from the get go.
The next round was an interview with two engineers. I had a great time. The one thing that I would say is that the questions were very open ended. This requires incredible self-discipline. You have to be responsible for highlighting your strengths and make sure you don’t ramble. When there is less direction in the interview questions, you have to be more focused. I do think this is a good technique though as it allows the interviewers to get to know you. I like that the interviews are usually an hour; this gives you more time and as a neurodivergent person this gave me more time to express myself clearly and I loved that. I have found 30 minute interviews to be very intense.
The next stage was a 3 hour take home task. I spent a huge amount of time learning Python and Django for this. This paid off. I would say don’t underestimate how difficult it will be. I found it very very challenging, but that was okay.
The penultimate stages was an interview with two engineers to discuss my coding test. They were incredibly helpful and kind and supportive and I felt that they wanted me to succeed all the way through which was amazing. I came out of that interview feeling my absolute best. They asked me some tough technical which I just honestly said when I didn’t know something and then I worked my way through it and succeeded.
The final stage was with the Head of Engineering. It was an incredible conversation which left me feeling so inspired about the product and the mission. This one was just 30 minutes but that was fine because it was designed to be a shorter interview. Again I was asked some technical questions and I had no idea how I’d done. I was very very glad and grateful when I found out that I’d succeeded. Halfway through the process I changed recruiter as my application was moved to a different division (this was a decision both parties loved so it worked out amazing).
The new recruiter who took over was so great as well and has done an incredible job of getting me onboarded and so much more. Love both of the recruiters, and loved all of the engineers who interviewed me.
Lastly I want to say that this process was extremely challenging but don’t let that deter you, especially to any fellow women out there and anyone struggling with confidence. If I had read how hard it was then I might have been put off but I did it and I surprised myself - and maybe you can, too?
Interview questions [1]
Question 1
The interview questions were very open ended. I would advise to think about what you really want to tell them, make sure you incorporate that in, and maybe to stick to the point so you can avoid rambling. For the technical questions then just be honest if you don’t know something, and then do the best you can. It worked out really well for me!!! The interviewers are really kind, lovely and supportive. They want you to succeed!
The interview process was exceptionally smooth, well structured, and professionally managed. Communication was clear from the offset and throughout, expectations were transparent, and each stage felt organized, efficient, and respectful of my time.
I applied online. I interviewed at Kraken (Manchester, England) in Jun 2026
Interview
Four rounds long. 1st round was an introduction call. 2nd round was a take home coding task, which took me about an hour and a half. On this stage make sure to write code to production quality - they will read it and ask you about it in the next round. 3rd round was a basic technical interview, including a section going over your solution to the 2nd round task. The 4th round is a white board interview, where you’re given a task and asked to propose a solution, in conjunction with two other engineers.
Interview questions [1]
Question 1
What is the release process at your current employer, from ideation all the way to it being deployed in production, and how would you improve it?
I applied online. I interviewed at Kraken (London, England) in Feb 2026
Interview
Application
I applied through Indeed. The process took 1 month. I interviewed at Kraken (UK) in Feb 2025
Interview
1st stage: Had a chat with a wonderful recruiter, set the stage for the whole interview process. Discussions about the company structure, team I would be working it, salary expectations and general question regarding motivation for joining the team.
2nd stage: Take home test. A django command line app for parsing file(s). Here, they evaluate you on taking on an ambiguous task and providing a scalable solution. Document your assumptions properly.
3rd stage: Further technical discussion about the task. Discussing approach, decisions taken and tradeoffs. How can the app be extended.
4th stage: The final stage. Focuses on your technical skills and the wider Python/Django ecosystem—discussions around ways of working.
After the last interview, the offer came within 30 minutes.
I really enjoyed working with my recruiter (Brad). He was super supportive.
Interview questions [2]
Question 1
1st technical interview
Discuss your approach for taking on the technical task.
How do you approach testing?
How can we make this app more robust to handle more/large files?
You held data in memory before bulk creating. How would you handle OOM issues?
2nd technical interview(last stage)
They generally ran through my resume and asked questions.
Testing, App performance, CI/CD, Microservices (Advantages/Disadvantages)