← Akuna Capital Interview Insights

Akuna Capital·Software Engineer·Technical Phone Screen·Intermediate

Intermediate
May 2026

Summary

Akuna Capital software engineer interview with a pretty meaty C++ design question. The whole thing revolved around building a market-making quoter class from scratch, and the state machine complexity was way more involved than I expected going in.

Questions Asked (1)

Q1

Design and implement an InstrumentQuoter class in C++ that manages quoting a single instrument on a BBO market supporting only order insertion and deletion. The class must enforce a minimum price offset from a theoretical price, align prices to exchange tick size, avoid crossing the exchange BBO, and ensure no overlapping in-flight orders per side using a per-side state machine.

System DesignTechnical Trade-offsAPI & Integrations
Author's notes

This was a lot to hold in your head at once.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by clarifying requirements and assumptions, then outline the class design with key components: state machine, price calculation, and order management. Walk through the implementation logic step-by-step, emphasizing how each constraint is enforced and potential edge cases.

Pro tip: Emphasize the importance of a robust state machine to prevent race conditions and ensure thread safety, as this is critical in low-latency trading systems. Also, discuss how you would test the class, including unit tests for price alignment and offset enforcement.

1. Clarify Requirements and Assumptions

Ask clarifying questions about the BBO market, tick size, theoretical price source, and concurrency requirements. State any assumptions you make.

2. Design Class Interface and Components

Define the public methods (e.g., quote, onOrderUpdate) and internal components: per-side state machine, price calculator, and order tracker.

3. Implement Price Calculation Logic

Detail how to compute quote prices: apply minimum offset from theoretical price, align to tick size, and adjust to avoid crossing the BBO.

4. Implement State Machine and Order Management

Describe the per-side state machine (e.g., IDLE, PENDING_NEW, ACTIVE, PENDING_DELETE) and how it prevents overlapping in-flight orders.

5. Discuss Edge Cases and Testing

Mention handling of partial fills, order rejections, and market data updates. Outline a testing strategy to validate constraints.

Key Points to Mention

  • Per-side state machine to manage order lifecycle and prevent overlapping in-flight orders
  • Price alignment to tick size using integer arithmetic to avoid floating-point errors
  • Minimum price offset from theoretical price, ensuring quotes are not too aggressive
  • Avoiding crossing the BBO by adjusting prices based on current best bid/offer
  • Thread safety and concurrency considerations for high-frequency trading environments
  • Handling of asynchronous order updates and market data events

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.