Akuna Capital · Phone screen → Onsite
In processAkuna Capital QR Screens and Coding: 77 Experiences (Part 1 of 6)
Akuna Capital quant researcher interviews, 2022–2025: technical phones on math, probability and coding, then math and Python finals for interns.
At a glance
- Process: a technical phone of about 45 minutes with a quant or senior researcher → for interns, finals in mathematics, Python whiteboard coding and a senior-manager talk (P01, 02).
- Asked recently: math or statistics in 3 of 4 current reports (a variance question, integration); probability and an algorithm or Python task in 2 (02, 03).
- Difficulty: two current candidates stopped at the first technical round after a basic variance question (01) or an integral and an algorithm (03); one intern declined an offer (02).
- Practise first: Merge Sorted Lists and the other Akuna coding tasks linked in History.
Coverage: 16 Akuna Capital quantitative research reports: 4 current (December 2023 to the 2025 intern cycle; Singapore and Chicago where stated) and 12 from March 2022 to October 2023 in History. QR, QR intern and junior QR roles.
In this series
- Part 1 (current): 2022–2025 screens, coding and the newest reports.
- Part 2: 2021–2022: coding, simulation and probability.
- Part 3: 2020: root finding, regression and shuffles.
- Part 4: 2019–2020: ML and final rounds.
- Part 5: 2018–2019: probability and SVMs.
- Part 6: 2017–2018: JQR, ML and projects.
Newer reports: Akuna quant technical interviews, 2025–2026.
What came up
Across all 16 reports in this part, coding and data structures came up in 11, probability in 9 and statistics or regression in 9. The newest reports are thin on specific prompts, so the History entries below hold most of the named questions.
Current reports (since late 2023)
Four reports fall in the last three years. They describe a technical phone with math or probability, then, for one intern, finals in mathematics and Python coding.
| Topic | Reports | Last seen |
|---|---|---|
| Math, statistics or integration in the phone | 3 of 4 | Feb 2025 (report date) |
| Probability questions | 2 of 4 | Nov 2024 |
| Coding (algorithm or Python whiteboard) | 2 of 4 | Nov 2024 |
| Optimization problem worked with the interviewer | 1 of 4 | 2025 cycle |
Questions we found
| Question | Reports | Last seen |
|---|---|---|
| A basic variance question | 1 | Feb 2025 (report date) |
| Probability, mental arithmetic and data structures (phone) | 1 | Nov 2024 |
| Python algorithm on a whiteboard (final) | 1 | Nov 2024 |
| An integration problem and an algorithm question | 1 | Dec 2023 (report date) |
P01: A 45-minute internship phone with collaborative optimization
Recruiting cycle: Summer 2025 internship · Role: Quantitative Research Intern
The technical phone lasted 45 minutes. A quant interviewer worked with the candidate on mathematics and an optimization problem. The candidate later said they were not selected for further rounds.
Technical phone
- The phone interview included mathematical questions, without specific examples in the account.
- The candidate worked through an optimization problem with the interviewer. They described a collaborative discussion but did not give the objective, variables or solution.
01: Singapore: a variance question with the APAC quant head
Report date: 2025-02-26 · Role: Quantitative Researcher; seniority not stated · Location: Singapore
The first interview for the Singapore role was directly with the APAC Head of Quant. They discussed the candidate's background before the variance question.
Technical phone
- The interviewer asked a basic variance question. The candidate could not answer it; the random variables and calculation were not recorded.
02: Chicago: a researcher screen and math/Python finals
Report date: 2025-10-31 · Interview month: 2024-11 · Role: Quantitative Research Intern · Location: Chicago
A senior researcher led the phone screen. Separate final interviews covered mathematics, Python whiteboard coding and a senior-manager conversation. The process took about six to seven weeks, and the candidate declined the offer.
Phone screen
- The phone screen included probability problems.
- There were mental-arithmetic questions too.
- The interviewer also asked about data structures.
Final: mathematics
- One final interview covered more advanced mathematics and statistics, including linear algebra and probability.
Final: Python coding
- Another final interview involved writing an algorithm in Python on a whiteboard. The task itself was not described.
03: Integration and an algorithm in the first live round
Report date: 2023-12-17 · Role: Quantitative Researcher; seniority not stated
The first live interview began with the resume, then moved into mathematics and algorithms. The candidate struggled with integration and the algorithm question and did not advance.
Technical phone
- The live interview included an integration problem. The candidate did not give its expression or bounds.
- There was a probability question associated with the familiar green quant-interview book, but no particular problem was identified.
- An algorithm question followed. The candidate struggled with both the integral and the algorithm and did not progress.
Common questions
What is the Akuna quant researcher phone screen?
A technical phone of about 45 minutes on math and probability, sometimes with an optimization problem or data structures (P01, 02); one candidate got a basic variance question (01).
Does Akuna ask coding for quant research interns?
Yes: a Python algorithm on a whiteboard in the 2024 finals (02), and coding tasks such as merging sorted lists and searching a shifted array in 2022–2023 reports (H04, H05).
How long does the Akuna QR intern process take?
About six to seven weeks from phone screen to offer in one Chicago report (02).
History (before late 2023)
HP02: A later update confirms a data-structure phone
Report update: 2022-11-16 · Role: Quantitative Research Intern
In a November 16, 2022 update, the research-internship candidate described a later phone interview that ended unsuccessfully.
Technical phone
- A later phone interview required implementing a common data structure. The candidate said they failed because they could not write it, but did not name the structure or operations.
H04: A binomial estimate, correlated normals and a merge
Report date: 2023-10-02 · Role: Quantitative Researcher; seniority not stated
The candidate described a phone conversation with three technical questions. A later reply leaves their phone-versus-assessment attribution unclear.
Technical phone
- Toss 100 fair coins and estimate the probability of getting more than 60 heads.
- X and Y have standard-normal marginal distributions and correlation ρ. Find E[min(X,Y)]. The account does not specify joint normality.
- Merge a list of sorted lists into one new sorted list.
The narrative places these three questions in the phone interview, but a later reply also confirms an OA description. Their stage attribution remains unclear.
H05: Correlation bounds and searching a shifted array
Report date: 2022-11-08 · Role: Quantitative Research Intern · Location: Shanghai
The Shanghai internship phone combined mathematics and CodePair. The candidate interviewed on a Friday and received the rejection on Monday morning.
Technical phone
- If corr(A,B) = corr(A,C) = 0.8, what values can corr(B,C) take?
- Compare three games: one die pays its face value squared; two dice pay the product of their values; three dice pay the square of their median. Find and compare their expected payouts. The dice's faces and fairness were not specified in the account.
- Choose two random points on a rope of length L. What is the probability that the distance between them is less than x?
- Search for an element in a sorted array after a cyclic shift. The example changed [1,2,3,4,5,6] into [5,6,1,2,3,4].
H06: Projects revisited across the phone and final interviews
Report date: 2022-10-19 · Role: Quantitative Research Intern
A phone was followed by three virtual final interviews with researchers. HR replied within one to three business days between rounds in this candidate's process. Projects came up repeatedly, and the third final interview ran beyond its announced time.
Technical phone
- The first interviewer went into the candidate's project and related ML knowledge.
- There were three mathematics questions: two on probability and one on statistics. The candidate did not remember their setups.
- The coding problem was identified as Search in Rotated Sorted Array.
Final interview 1
- A final-round interviewer asked about the candidate's most technically challenging project, then explored another project's background, features and implementation.
- Why do you want to work in quantitative research?
- There was also a C++ task with many edge cases. The candidate described it as easy but did not identify it.
Final interview 2
- Another interviewer asked for technical details after finding the candidate's project overview too general.
- Write C++ code to solve x^n = a. The candidate's implementation broke for large a and n. They later thought a smaller step size might help; the account does not say that gradient descent was mandatory.
Final interview 3
- Two projects came up again, with deeper technical questions.
- Explain R². How does it compare with corr(Y, predicted Y)? When can R² be negative, and how could you generate data that produces a negative value? The comparison was written as correlation, without a square.
- The ML discussion also touched on nonlinear models.
- Rank correlation was another topic.
- The interviewers supplied further modeling scenarios, but the candidate did not retain their details.
H07: Bias–variance, a broken stick and Monte Carlo
Report date: 2022-09-30 · Role: Quantitative Research Intern
The candidate had recently completed a research-internship phone.
Technical phone
- Why quant?
- Explain the bias–variance tradeoff.
- Break a stick at random into three pieces. What is the probability that they can form a triangle?
- Monte Carlo also came up. The candidate did not say whether it was a follow-up to the stick problem.
H08: A Boston-to-Chicago transfer before Junior QR finals
Report date: 2022-09-01 · Role: Junior Quantitative Researcher · Location: Boston → Chicago
The candidate first applied to Boston, then agreed to transfer to Chicago when Boston filled its places. After 15 minutes with HR, the final schedule contained one planned hour with a trader. That interviewer arrived 20 minutes late and spent about 40 minutes on options.
Final interview
- A trader spent about 40 minutes asking options questions. The candidate, a physics PhD applying for Junior QR, found some terminology unfamiliar and did not record the individual questions.
H09: Project metrics followed by a Python simulation
Report date: 2022-09-17 · Interview period: late August 2022 · Role: Quantitative Research Intern
The candidate applied in late July and had the first phone in late August 2022. The 30-minute interview moved from a project discussion into related ML concepts and probability.
Technical phone
- Introduce yourself.
- Describe the project you are most proud of.
- A project discussion led to sensitivity and specificity.
- The interviewer asked about ROC curves.
- Compare K-means with KNN.
- PCA was another project follow-up.
- Cut a rope at two random points and find the probability that its pieces form a triangle. When the candidate could not find an analytical solution, the interviewer asked them to simulate it in Python.
H10: One CodePair problem in roughly half an hour
Report date: 2022-07-07 · Role: Quantitative Researcher; seniority not stated
The candidate was invited directly to about 30 minutes of CodePair. There was one coding question. They fixed small bugs, got the tests to pass and later received a rejection.
Technical phone
- Use CodePair to find the first and last positions of a target in a sorted array. The candidate later confirmed the question as First and Last Position in a Sorted Array.
H11: Two phones: betting policies and a random circle arc
Report date: 2022-05-17 · Interview dates: 2022-04-25 and 2022-05-06 · Role: Quantitative Research Intern · Location: Chicago
The Chicago summer-internship process had two phones, on April 25 and May 6, 2022. The second phone was the final interview. The application had been submitted in late 2021.
First phone
- Explain the bias–variance tradeoff.
- Explain R².
- Start with a balance of 100 and aim for 500. Compare betting everything, half the current balance (described as larger than 10), or a fixed 10 at a time. The initial win/loss probabilities were 0.6 and 0.4; the interviewer then reversed them. The candidate offered preferred policies, without a verified general derivation.
- Search in Rotated Sorted Array was the coding task.
Second phone
- Place N random points on a unit circle. Find the expected length of the arc containing (1,0). The candidate used order statistics and reported 4π/(N+1), although their written intermediate calculation was inconsistent.
H12: An arithmetic evaluator without parentheses
Report date: 2022-04-19 · Role: Quantitative Research Intern
The interviewer used a Zoom call without requiring the candidate's camera. The candidate reported a rejection one business day later.
Technical phone
- Explain the bias–variance tradeoff.
- A second question asked for an ML term the candidate did not know and could not later recall.
- Implement an arithmetic evaluator in Python 3. The candidate clarified that they reached addition, subtraction, multiplication and division with the usual precedence, without parentheses, using loops and conditionals.
H13: Ropes, coin generation and when to stop rolling
Report date: 2022-04-02 · Role: Quantitative Research Intern
The phone interview contained four questions.
Technical phone
- Choose two random points on a rope and find the expected distance between them.
- Use a fair coin to generate an outcome in {0,1,2}, then find the expected number of flips. The account does not explicitly state the target probabilities.
- Find upper and lower bounds for Var(A+B).
- You may roll a six-sided die up to three times. You can keep the first or second result or roll again. Find the best stopping rule and its expected payoff.
H14: A QR phone described as a coding interview
Report date: 2022-03-21 · Role: Quantitative Researcher
The candidate described the Akuna QR phone as a coding interview.
QR technical phone
- The candidate described the Akuna QR phone coding as manageable but did not identify the exercise.
Keep practicing
- From these reports: merge sorted lists (H04), search rotated sorted array (H05), solve x^n = a (H06), first last position (H10), Implement an arithmetic evaluator in Python 3 (H12).
- Akuna Capital question banks: algorithms (sign-in needed).
- Everything Akuna Capital in one place: the Akuna Capital interview page.
- More firsthand reports: the Experience feed.
In this series
Sources: Anywhere useful interview info can be found.
Comments
0No comments yet — be the first to share what you know.