Akuna Capital Software Engineer candidates report an online assessment with LeetCode-style coding, sometimes alongside C++ and OS multiple choice. Some also report a C++ phone screen, a Zoom interview, or slow scheduling.
$157K
Avg. Base Comp
$264K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Candidates describe the Akuna Capital Software Engineer process as assessment-first. Several accounts begin with an online assessment, and for some it was the stage where the process ended. One candidate describes two OA rounds, each with 10-12 multiple choice questions and 2-3 coding problems. Those questions leaned on C++ and operating-systems fundamentals. Another describes three algorithmic questions, including a hard palindrome partitioning problem, and a rejection after the assessment with no follow-up round. A trainee-track candidate describes C++ multiple choice questions plus three coding problems, including a card game simulation where the deck flips whenever a card is a multiple of three.
After the assessment, the reports diverge. One candidate had a phone screen on thread-safe LRU cache design in C++. Another had a Zoom interview with a scripted interviewer who seemed to expect specific answers. The trainee-track candidate reported back-to-back technical rounds on currency arbitrage as a graph problem and an elevator system design, followed by an object-oriented design interview. A quant developer intern reported a one-way video round of brain teasers, a live OOP coding session and a final round on expected value, game theory and options trading. These are individual accounts, so prepare for variation rather than one fixed loop.
For preparation, practice timed medium-to-hard algorithm problems, especially graphs, dynamic programming and union-find. Brush up on C++ concurrency, mutexes and OS basics. Practice explaining trade-offs aloud, since candidates mention both live explanation and recorded answers. One candidate lost an opportunity to a competing deadline after slow scheduling, so tell the recruiter about any deadlines early. Outcomes in these reports were rejections or a withdrawal.
Synthesized from 7 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Akuna Capital process.
It was a very slow process. It was supposed to be 4 total rounds, with the technical assessment being the first. I applied, and two weeks later I received a coding assessment. The assessment was one question that tested how you would implement a specific system. Then you get a result. I passed, and a week later I received another interview, this time by video. I had to record answers to a question that was more behavioral (though technical-leaning). I was surprised with how long everything took. The questions themselves were not difficult, which surprised me. If you can code you should be fine. LeetCode medium level. I did struggle with the video portion because I only had 2 minutes to answer. I got no response afterward.
Questions asked: Explain a time you had to make a tough technical decision and how you weighed the tradeoffs
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Akuna Capital
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Employee Salaries | |
| Merge Sorted Lists | |
| Subscription Overlap | |
| Closest SAT Scores | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Find the Missing Number | |
| Maximum Profit | |
| Bagging vs Boosting | |
| String Shift | |
| Prime to N | |
| Comments Histogram | |
| Top 5 Turnover Risk | |
| Like Tracker | |
| Find the First Non-Repeating Character in a String | |
| Size of Joins | |
| Total Spent on Products | |
| Google Maps Improvement | |
| Rectangle Overlap | |
| P-value to a Layman | |
| Cumulative Distribution | |
| Top 3 Users | |
| Over-Budget Projects | |
| Slacking Employees Salaries | |
| Hurdles In Data Projects | |
| Sum to N | |
| Over 100 Dollars |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an online assessment as the first stage. Formats vary: one describes two OAs with 10-12 multiple choice questions on C++ and OS concepts plus 2-3 coding problems, while another describes three algorithmic problems, including a hard palindrome partitioning question. Time pressure is a common theme.
Some candidates report a technical screen after the assessment. One was asked to implement a thread-safe LRU cache in C++ and described the interviewer as supportive. Another had a Zoom interview with a scripted interviewer who expected specific answers, so explaining your reasoning and trade-offs clearly may help.
A quantitative developer intern reported a one-way video round with three brain teasers and about five minutes to explain each approach. This comes from one intern account and may not be part of every Software Engineer process.
Candidates on other tracks report live technical rounds. These included currency arbitrage as a graph problem, an elevator system design and an object-oriented design interview, plus a pair-programming OOP session in the intern account. Expect class hierarchies and data-structure choices to matter, though the exact mix may differ by role.
A quantitative developer intern reported a final round with a quant covering expected value in dice games, game theory, options trading simulation and market-making. This comes from one intern account, so treat it as possible exposure for trading-adjacent roles rather than a standard Software Engineer round.
