I applied through an employee referral. I interviewed at Kraken (Londres, Inglaterra) in Dec 2024
Interview
Initial call with HR was fine. It's what one would expect from any SWE process at that point. Nothing particular to note.
Then there's a take home task. No option to avoid it. When I got the spec for it, it said that it would require about 6h of time to complete, which is IMO a pretty unreasonable amount of time to ask candidates to spend doing a take home.
The take home itself isn't too hard, but one thing that really tripped me is that they give you a fixture with some data. This fixture has a header and a footer. The take home doesn't really talk about the header and footer, and just points to some documentation about the body of the fixture. It's extremely hard to find documentation for the header and footer. I thought I'd show some attention to detail by finding the documentation for it, which took a while. At the end of the day, being good at finding and reading documentation is a big part of what it is to be a good engineer, and I do this daily at work.
In the end, I got some feedback saying that it looked like I spent too much time on the header and footer and that it wasn't required. Perhaps they should consider either removing the header and footer or telling candidates that they shouldn't focus on that, lest they waste time with it.
I'd personally avoid interviewing here, just from the take-home assignment I can see that the engineering culture is not great.
Interview questions [1]
Question 1
It's a Django app to parse some files and put them in a database.
I applied online. I interviewed at Kraken (Londres, Inglaterra) 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)
1. Screening call with recruiter to learn about the company, very chill
2. tech test
3. meeting with engineers who reviewed the test to discuss the solution and how you'd improve it
4. Culture fit and further technical discussion with head of engineering
Overall it's a *very* straight forward process with only a take-home test and 2 stages where you talk to people in the company. Compared to other companies that had 4+ stages not including the screening call it was very good to see someone still hiring sensibly. Offer came very quickly after the final call and I was delighted to accept. I was also treated very well by the recruitment team and it felt like the process was decisive and quick.
Interview questions [1]
Question 1
Write a django application to parse and view meter readings
I applied online. The process took 3 weeks. I interviewed at Kraken (París) in Nov 2025
Interview
Le processus d'embauche est très straightforward:
1. Un appel en visio RH
2. Un test technique à faire à la maison (3-4h) en Python, Django
3. Un appel en visio avec 2 ingénieurs pour discuter du test technique et des possibles améliorations
4. Un appel en visio avec 2 personnes de l'équipe (team fit)
Toutes les personnes que j'ai rencontrées lors de ces entretiens ont été très bienveillantes. Le processus est transparent et très rapide. J'ai eu des retours le lendemain de chaque entretien. Les retours peuvent prendre 1 semaine au maximum. J'ai aussi reçu un document qui expliquait tout ce processus, contrairement à d'autres entreprises où le processus peut être flou et long, donc c'était une agréable surprise. Franchement ce type de processus humain est très rafraîchissant, merci la team Talent Acquisition. De plus, la Talent Acquisition Specialist était au top, très à l'écoute et réactive.
Interview questions [2]
Question 1
"Quand est-ce que c'est compliqué de faire un git revert?"