Real, anonymous reports from people who interviewed for Software Engineer at AkunaCapital, newest first and distilled into what to expect across the loop.
After applying, I received HackerRank online assessments to complete in a short window, and the questions felt more like practical simulation than quick LeetCode-style coding. I remember spending real time reading what the problem was asking before I even started coding, because the prompts were wordy and the details you actually needed weren’t always obvious at first glance. There were also multiple C++-leaning expectations, and the whole thing was timed tightly enough that it required focus.
My process started with an online assessment on HackerRank where the statements were oddly long and seemed to bury the key details I needed to solve the actual task. I ended up having to rely on specific patterns I’d practiced before, like sliding-window style approaches, rather than just reasoning my way through from scratch.
The interview process begins with a challenging online assessment on HackerRank, which includes multiple-choice questions and coding problems that emphasize C++ and OOP concepts. Candidates often find the questions to be lengthy and time-constrained, requiring careful reading and efficient problem-solving under pressure.
Following the OA, candidates typically participate in a technical screen that may involve coding on a platform like CoderPad, focusing on C++ fundamentals and problem-solving skills. Interviewers often expect precise answers and may ask for detailed explanations of concepts, which can create a high-pressure environment.
Candidates usually face multiple rounds of technical interviews that assess both coding skills and system design capabilities, with a notable emphasis on C++ and data structures. The interviews can include algorithm-heavy questions, system design prompts, and discussions about lower-level programming concepts.
In addition to technical evaluations, candidates encounter behavioral interviews that assess cultural fit and situational responses. These rounds often focus on how candidates communicate their thought processes and decisions during technical challenges.
Candidates report that the pacing of the interview process can feel slow, with delays in feedback and scheduling impacting their experience. Many express frustration over how decisions seem influenced more by process mechanics than by their technical performance.
The overall difficulty of the interview process is perceived as high, with candidates often feeling unprepared for the level of technical depth required, particularly in C++. Many candidates wish they had focused more on specific language features and practical applications of their knowledge.