PracHub
QuestionsPremiumLearningGuidesCheatsheetNEWCoaches
|Home/System Design/Citadel

Design stock price time-series store and query

Last updated: Mar 29, 2026

Quick Overview

This question evaluates system design skills for time-series data storage and querying, covering scalability, partitioning, indexing, event-time handling, consistency, and read/write latency trade-offs for historical stock prices.

  • easy
  • Citadel
  • System Design
  • Software Engineer

Design stock price time-series store and query

Company: Citadel

Role: Software Engineer

Category: System Design

Difficulty: easy

Interview Round: Technical Screen

## Problem Design a platform that stores stock prices over time and can be queried later. ### Core functionalities 1. **Ingest price**: The system receives events of the form: - `ticker` (string, e.g., `AAPL`) - `price` (decimal) - `timestamp` (event time) 2. **Query price**: Given a `ticker` and a `timestamp`, return the price for that ticker at that time. ### Clarifications to address in your design (state assumptions) - If there is **no price exactly at that timestamp**, should the system return: - the most recent price **at or before** the timestamp (common), or - “not found” unless there is an exact match? - Expected scale: number of tickers, events/sec, retention (e.g., 1 day vs 10 years). - Latency targets for reads/writes. - Handling out-of-order events, duplicates, and clock skew. ## Deliverables - High-level architecture (write path + read path). - Data model and storage choice. - APIs. - Partitioning/indexing strategy. - Consistency, availability, and failure-handling tradeoffs.

Quick Answer: This question evaluates system design skills for time-series data storage and querying, covering scalability, partitioning, indexing, event-time handling, consistency, and read/write latency trade-offs for historical stock prices.

Related Interview Questions

  • Design alerting for application-to-exchange mappings - Citadel (medium)
  • Design a low-latency trading platform - Citadel (hard)
  • Discuss queues, NoSQL, and concurrency - Citadel (hard)
  • Design a low-latency trading system - Citadel (hard)
Citadel logo
Citadel
Jan 22, 2026, 12:00 AM
Software Engineer
Technical Screen
System Design
18
0
Loading...

Problem

Design a platform that stores stock prices over time and can be queried later.

Core functionalities

  1. Ingest price : The system receives events of the form:
    • ticker (string, e.g., AAPL )
    • price (decimal)
    • timestamp (event time)
  2. Query price : Given a ticker and a timestamp , return the price for that ticker at that time.

Clarifications to address in your design (state assumptions)

  • If there is no price exactly at that timestamp , should the system return:
    • the most recent price at or before the timestamp (common), or
    • “not found” unless there is an exact match?
  • Expected scale: number of tickers, events/sec, retention (e.g., 1 day vs 10 years).
  • Latency targets for reads/writes.
  • Handling out-of-order events, duplicates, and clock skew.

Deliverables

  • High-level architecture (write path + read path).
  • Data model and storage choice.
  • APIs.
  • Partitioning/indexing strategy.
  • Consistency, availability, and failure-handling tradeoffs.

Solution

Show

Comments (0)

Sign in to leave a comment

Loading comments...

Browse More Questions

More System Design•More Citadel•More Software Engineer•Citadel Software Engineer•Citadel System Design•Software Engineer System Design
PracHub

Master your tech interviews with 7,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.