Glassdoor users rated their interview experience at Kraken as 33.3% positive with a difficulty rating score of 2.67 out of 5 (where 5 is the highest level of difficulty). Candidates interviewing for Account Manager and Client Delivery Lead rated their interviews as the hardest, whereas interviews for Account Manager and Client Delivery Lead roles were rated as the easiest.
The hiring process at Kraken takes an average of 7 days when considering 3 user submitted interviews across all job titles. Candidates applying for Client Delivery Lead had the quickest hiring process (on average 7 days), whereas Client Delivery Lead roles had the slowest hiring process (on average 7 days).
I applied online. I interviewed at Kraken (Londra, Inghilterra) in Sep 2025
Interview
Started with a recruiter call, followed by a SQL technical challenge of medium difficulty. There was a technical round to discuss the solution and some basic CV and data questions. It was followed by behavioural round of 1.5 hours with tech lead and product manager. Honestly, this is where I started losing the interest in the company. The interviewers’ inexperience was evident or maybe they’ve already accepted someone else. They frequently interrupt while you answer with unrelated questions. Finally, there was a final round with the head of analytics- some basic questions around competency and motivations. He was literally happy with how the interview went and agreed he was happy with all my answers. Yeah that was it, then the recruiter ghosted me for a few weeks even after multiple follow up emails. Finally, after almost a month, I was informed they have accepted someone else. At the least, if someone who has done all the rounds, they should be given detailed feedback irrespective of the outcome. It’s merely a 5 minute job for the recruiter to draft a feedback email, still they ignore it.
First call with a recruiter. Then a conversation with a manager to align on fit. Then a take home assignment to submit. A final interview with team members to discuss the take home assignment
Interview questions [1]
Question 1
Explain the implementation for the technical take home assignment
Le processus d’entretien est clair
1: RDV avec la RH + réception d'un devoir a faire a la maison (4-6h)
2: Examination du devoir avec 2 employés qui ne feront pas partie de votre équipe.
Dans mon cas j'ai été interviewé par des DEI employés qui clairement n'avaient pas de connaissance profonde en programmation mais cherchaient plus des mots clés (separation of concern, single responsability, DRY, ... ).
Les questions étaient vagues donc pour chacune de mes réponses je donnais un cadre pour donner une réponse précise mais avec du recul ça n'a pas dû leur plaire.
Quelques jours plus tard, j'ai reçu une réponse par mail avec une explication des raisons de mon refus. Pourtant les raisons mentionnées ont été expliquées durant l'interview.
Ex: "The commit history could have been clearer and more atomic."
Je pense que cette interview c'est plus joué sur le feeling qu'ils avaient de moi et non pas de mes capacités techniques.
(etre LGBT ou non blanc semble aider)
Interview questions [1]
Question 1
Quel est le lien entre ces 2 éléments ? (en parlant de modeles)