PracHub
QuestionsPremiumCoachesLearningGuidesInterview Prep
|Home/System Design/Databricks

Design a stock order manager

Last updated: Apr 16, 2026

Quick Overview

This question evaluates competency in designing reliable order lifecycle management, external API integration, consistency and idempotency under retries, fault tolerance, and scalability for trading/order systems.

  • medium
  • Databricks
  • System Design
  • Software Engineer

Design a stock order manager

Company: Databricks

Role: Software Engineer

Category: System Design

Difficulty: medium

Interview Round: Technical Screen

Design an order management service for stock buy and sell requests. The system does not match trades itself. Instead, it integrates with a third-party brokerage API: - `POST /orders` -> submits an order and returns a unique external order ID - `GET /orders/{id}` -> returns the latest order details and status - `DELETE /orders/{id}` -> requests cancellation of an existing order Your design should support: - Placing buy and sell orders - Tracking order status over time - Canceling orders - Handling orders that remain in a `pending` state for a long time - Handling orders that expire before being filled - Identifying likely system bottlenecks and explaining how to mitigate them Focus especially on order lifecycle management, correctness under retries or partial failures, and how the system stays consistent with the third-party brokerage.

Quick Answer: This question evaluates competency in designing reliable order lifecycle management, external API integration, consistency and idempotency under retries, fault tolerance, and scalability for trading/order systems.

Related Interview Questions

  • Design a Slack-Like Messaging System - Databricks (medium)
  • Design a Book Price Aggregator - Databricks (medium)
  • Design a Distributed File System - Databricks (medium)
  • Design an Online Bookstore - Databricks (hard)
  • Design a Hierarchical File System - Databricks (hard)
Databricks logo
Databricks
Apr 12, 2026, 12:00 AM
Software Engineer
Technical Screen
System Design
76
0
Loading...

Design an order management service for stock buy and sell requests.

The system does not match trades itself. Instead, it integrates with a third-party brokerage API:

  • POST /orders -> submits an order and returns a unique external order ID
  • GET /orders/{id} -> returns the latest order details and status
  • DELETE /orders/{id} -> requests cancellation of an existing order

Your design should support:

  • Placing buy and sell orders
  • Tracking order status over time
  • Canceling orders
  • Handling orders that remain in a pending state for a long time
  • Handling orders that expire before being filled
  • Identifying likely system bottlenecks and explaining how to mitigate them

Focus especially on order lifecycle management, correctness under retries or partial failures, and how the system stays consistent with the third-party brokerage.

Solution

Show

Submit Your Answer

Sign in to leave a comment

Loading comments...

Browse More Questions

More System Design•More Databricks•More Software Engineer•Databricks Software Engineer•Databricks System Design•Software Engineer System Design
PracHub

Master your tech interviews with 8,500+ real questions from top companies.

Product

  • Questions
  • Learning Tracks
  • Interview Guides
  • Resources
  • Premium
  • For Universities
  • Student Access

Browse

  • By Company
  • By Role
  • By Category
  • Topic Hubs
  • SQL Questions
  • Compare Platforms
  • Discord Community

Support

  • support@prachub.com
  • (916) 541-4762

Legal

  • Privacy Policy
  • Terms of Service
  • About Us

© 2026 PracHub. All rights reserved.