I started with a recruiter screen and then moved quickly into a take-home assignment that I worked through over a few hours. The test itself was reasonable on paper, and I submitted it with the artifacts they requested. Where things went sideways was the follow-through and coordination afterward: communication slowed dramatically, and I ended up being essentially ghosted for weeks.
Even the logistics around sharing the solution became a sticking point. I was told to use a public Git setup at first, then later asked to make it private, but without the right collaborator information for how to access it. It took a long time to get the permissions details, and by the time I heard back, the feedback felt superficial and focused on whether it matched their senior-level expectations rather than on a fair review of what the assignment asked for.
> 1 year
Easy Neutral Berlin
My Kraken interview moved fast enough that the momentum carried me through. First, I applied and then got a recruiter and HR check-in where we covered my experience and why I wanted to join, plus Q&A. After that came a technical interview that was more about how I worked and how I’d approached past projects, before I got a home take-home.
The take-home was hands-on and built around developing something like a small product page or feature in a web framework. The technical interview after it was focused on walking through what I implemented and discussing it, rather than treating it like a mystery code-golf exercise. Even when the task required me to work with a technology I wasn’t as used to, it was still doable, and I could submit within a few days. The atmosphere across rounds felt friendly and professional, with interview scheduling that didn’t keep me waiting and HR responses coming quickly.
Share your interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
