Akuna Capital C++ Object Pool Coding Challenge Interview
Interview Experience
I learned C++ OOP two years ago, and I've almost forgotten everything, haha. They gave me an object pool class, did most of the work, and then I had to complete a function and fix a bunch of really st
Full Details
I learned C++ OOP two years ago, and I've almost forgotten everything, haha. They gave me an object pool class, did most of the work, and then I had to complete a function and fix a bunch of really stupid bugs—literally really stupid, because it explicitly stated that it couldn't be compiled yet and I had to debug. It had 45 minutes, and I didn't finish. I highly recommend thoroughly reviewing OOP and C++ syntax. The object pool has two private structs: template ObjectT struct node{ ObjectT object; node next} struct Batches{ Batches next; Node nodes; size_t size;} Node allocateBatch(size_t batchsize) Node& getnode() size_t capacity batches* batch (I don't quite remember this one) public: Several APIs capacity() You need to write numAllocated() Then there are a bunch of functions, the ultimate goal of which is to implement numAllocated().
About This Question
This is a candidate experience report from a akuna capital interview for a swe role during the take home round reported in 2026.
It covers the following topics: Oop .
Topics
More Akuna Capital Interview Questions
About Akuna Capital Interview Reports
This question was reported by a candidate who interviewed at Akuna Capital. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Akuna Capital are the higher-signal extractions to take from this report.
For broader preparation context, the Akuna Capital interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Akuna Capital reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Akuna Capital Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Akuna Capital reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.