
Kraken Digital Asset Exchange Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 97 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Kraken Digital Asset Exchange.
Software Engineer
It was a waste of time and effort. They gave me a big assessment to complete in 48 hours, which took much longer. After putting in a lot of effort, I was rejected with no explanation or code review. I asked the recruiter for feedback, and they gave some feedback based on their own perspective, but I wanted to discuss my approach and why I made certain decisions. Their judgment criteria were poor, and they didn't value my time and effort. I would avoid this if you don't want to waste time, or at least agree on an interview beforehand to discuss the assessment, whether they liked the code or not.
- Recruiter asked general questions about my experience and background before the assessment.
Software Engineer
My interview experience with Kraken was really positive. The process started with a simple HR screen, then a take-home assignment that was a bit bigger than most but super relevant and honestly fun to work on. After that, we reviewed my solution and talked about scalability and different approaches, which felt more like a collaboration than an interrogation. The behavioral interview felt like really a genuine conversation, no trick questions or stress. Communication was great throughout, the recruiter was super responsive and I got quick updates after every stage. The whole thing took about a month, and overall it left me with a really good impression of the company. Super excited to join!
- Do you have any experience in the crypto space?
Software Engineer
The process has 4 steps: 1. Intro call with Recruiter: They were surprisingly prepared and knowledgeable about the technical field. 2. Technical Coding: A one-hour live coding interview where you complete an exercise end-to-end in a pre-set environment. Challenging but doable. 3. Design and Architecture: A conversational interview covering topics from UI layout to backend performance. It was challenging with unexpected questions. 4. Hiring manager: This seemed like a cultural fit interview, but I didn't reach this stage. Throughout the process, I met great, prepared people. They emphasize their culture, so research it beforehand.
- What are your ideas for improving remote image rendering?
- How would you define an API for handling both list and detail views?
- Can you discuss the concept of optimistic updates?
Kraken Digital Asset Exchange Software Engineer Interview Questions
Quoted word for word from Kraken Digital Asset Exchange interview reports.
“Regarding Mutex::lock, what is its return value and the reason for it?”
Read reports →“What is the impact of the async keyword on generated machine code?”
Read reports →“Can you explain the execution flow of this async Rust code?”
Read reports →“Can you explain the components of an ethereum transaction and their respective functions?”
Read reports →“Can you explain the difference between symmetric and asymmetric encryption, and provide examples of how each is used in practice?”
Read report →“How would you allocate 100k between bonds and Bitcoin?”
Read report →“Can you build a REPL service based on a given prompt?”
Read report →“How would you design the backend to handle multiple requests with the identical payload when a user clicks a button repeatedly?”
Read report →“Build a basic trading system from the ground up in C++, including documentation, tests, and containerization.”
Read report →Formats, difficulty and experience
Across all 97 Kraken Digital Asset Exchange interview reports.