Object-oriented design interview questionHard

Design an Online Stock Brokerage System

Design a brokerage domain model covering accounts and portfolios, instruments, a cash ledger, market and limit orders, immutable fills, derived positions, order state transitions, and an external exchange gateway boundary — without building a matching engine.

1. Problem Statement

Design an online stock brokerage system: customers place market and limit orders to buy or sell instruments, orders are routed to an exchange and come back as fills (possibly partial), and the account's positions and cash update accordingly. The brokerage does not match orders itself. Start by clarifying scope and the core objects.

2. Live Coding Format

Work in the provided coding workspace while explaining your decisions to the live interviewer. Validation may use inline tests, examples, comments, or a verbal walkthrough.

3. Key Focus Areas

  • 1
    Order lifecycle with market/limit types and partial fills
  • 2
    Immutable fills and positions derived from fills
  • 3
    Cash ledger, reservation, and buying-power policy
  • 4
    ExchangeGateway boundary (no matching engine)

4. What Strong Candidates Should Demonstrate

  • Model accounts, portfolios, orders, fills, and positions with a clear external market boundary.
  • Derive positions and cash from immutable fills rather than editing them independently.
  • Handle partial fills, cancels of remaining quantity, and a buying-power check.
  • Represent money precisely and route orders to an exchange gateway without matching them.

Want interactive feedback?

Practice this problem in the live coding workspace while the interviewer probes your clarification, implementation, trade-offs, and validation.

Continue to Dashboard

Core Concepts

Hidden because they name the technique, which a real interviewer would not tell you.

Show core concepts
Object-Oriented DesignDomain ModelingState MachineFinancial Modeling

Continue preparing

Build a complete software engineer mock interview plan

Related Object-Oriented Design

Design a Two-Player Chess Game Engine

Design a chess engine that models a board and pieces, validates legal turns and moves, records move history, and detects check, checkmate, stalemate, resignation, and forfeit.

Related Object-Oriented Design

Design a Cricket Information Platform

Design a cricket scoring domain model covering teams and players, a match, innings, overs and deliveries, batting and bowling scorecards, extras and wickets, striker rotation, over completion, and match results for a configurable limited-overs format.

Related Object-Oriented Design

Design a Multi-Elevator Dispatch System

Design a controller for multiple elevators that accepts hall and cabin requests, schedules cars, models movement and doors safely, and supports replaceable dispatch policies.

Related Object-Oriented Design

Design a Vending Machine Controller

Design a vending machine that manages inventory, accepts money, supports product selection and cancellation, returns change, and enforces a clear transaction state machine.