Kraken Software Engineer Interview Guide

The whole process moved pretty quickly—I heard back from the recruiter within a week of applying through their careers page. The first call was a standard screening with the recruiter to confirm basics and gauge interest. Nothing fancy there, just a chance to ask questions about the role and team.

Then came the take-home coding exercise. It was intentionally vague, which I think was deliberate—you could solve it at a surface level as a novice, but the deeper you dug, the more nuance and complexity emerged. I spent time thinking about edge cases and different approaches, which I think paid off in the next round. The technical interview was all about that take-home: walking through my solution, defending my choices, and then getting hit with some deeper Rust questions to probe my understanding. They asked things like what Mutex::lock returns and why, and how async Rust code actually executes under the hood. The questions weren't gotchas, but they definitely separated someone who's memorized syntax from someone who understands the runtime.

The systems design round felt more conversational. We talked about architecture decisions and how you'd scale systems—less about textbook patterns, more about trade-offs and real-world constraints. The final conversation was with an engineering manager and sometimes another engineer on the team. It was genuinely about fit: would we work well together, do you care about the problems we're solving, that kind of thing. Everyone was candid and friendly throughout, which made the whole experience feel respectful and low-pressure even though they were clearly evaluating carefully.

I got the offer. The process itself was well-designed—the take-home forced you to show your actual problem-solving, the technical deep-dive validated you understand what you built, and the systems design and team conversations made sure you're not just technically competent but actually a good fit for how they work.