← Akuna Capital Interview Insights

Akuna Capital·Software Engineer·Technical Phone Screen·Intermediate

IntermediatePrefer not to say
Apr 2026

Summary

Akuna Capital software engineering interview with a design-focused question that started simple and then got a lot more interesting in the follow-up. The memory optimization angle was the real test.

Questions Asked (1)

Q1

Design an Enemy factory for a multiplayer game that returns an enemy instance of a given color. Include both the factory class and the Enemy class hierarchy.

System DesignTechnical Trade-offsAlgorithms & Data Structures
Author's notes

The base question felt pretty approachable.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by clarifying requirements (e.g., enemy types, colors, extensibility) and then design a class hierarchy for enemies with a factory that creates instances based on color. Discuss trade-offs between simple switch-based factory and more extensible patterns like registry or abstract factory, considering multiplayer scalability.

Pro tip: Mention that in a multiplayer game, enemy creation might need to be synchronized across clients, so the factory could be used server-side to generate enemies and replicate them, or use a deterministic approach. Also, consider using an enum for colors to avoid string comparisons.

1. Clarify Requirements

Ask about enemy types, colors, and whether new types/colors will be added frequently. Determine if the factory needs to be thread-safe or support serialization for multiplayer.

2. Design Enemy Hierarchy

Create an abstract Enemy class with common attributes (health, damage) and a Color property. Derive concrete enemy classes (e.g., RedEnemy, BlueEnemy) or use a single Enemy class with a color field, depending on behavior differences.

3. Implement Factory

Design an EnemyFactory with a method createEnemy(color) that returns the appropriate enemy instance. Use a switch statement or a map from color to creation function for extensibility.

4. Discuss Trade-offs

Compare simple factory vs. abstract factory vs. prototype. Consider performance, maintainability, and how to handle new colors without modifying existing code (Open/Closed Principle).

5. Consider Multiplayer Aspects

Address how enemy creation is synchronized across clients, potential use of object pooling for performance, and ensuring deterministic behavior if needed.

Key Points to Mention

  • Factory Method pattern and its variations (Simple Factory, Abstract Factory)
  • Open/Closed Principle: extending with new colors without modifying factory logic
  • Use of enums for colors to avoid stringly-typed code
  • Thread safety and performance considerations in multiplayer context
  • Object pooling to reduce garbage collection overhead
  • Serialization and network replication of enemy instances

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