Design a feature store with CI/CD and reliability

Quick Overview

This question evaluates a candidate's competencies in designing scalable, low-latency feature stores and end-to-end ML infrastructure, covering feature ingestion, point-in-time correctness, serving APIs, CI/CD for feature pipelines, metadata/lineage, and reliability engineering.

Design a feature store with CI/CD and reliability

Company: Reddit

Role: Software Engineer

Category: ML System Design

Difficulty: hard

Interview Round: Technical Screen

Design a feature store to serve ML models for both offline training and low-latency online inference. Specify requirements; feature ingestion (batch and streaming), computation and storage layers, feature serving APIs, point-in-time correctness, offline–online consistency, freshness and backfills, lineage/metadata, governance and access control. Detail deployment architecture and environments, CI/CD for feature definitions and pipelines, testing strategies (unit/integration/e2e, data validation), caching layers and eviction policies, reliability/SLOs and fault tolerance, monitoring/alerting and rollback, and cost/rate-limiting considerations. Provide component diagrams and justify technology choices.

Overview: This question evaluates a candidate's competencies in designing scalable, low-latency feature stores and end-to-end ML infrastructure, covering feature ingestion, point-in-time correctness, serving APIs, CI/CD for feature pipelines, metadata/lineage, and reliability engineering.

|Home/ML System Design/Reddit
Reddit logo
Reddit
Sep 6, 2025
hardSoftware EngineerTechnical ScreenML System Design
12
0

System Design: Feature Store for Offline Training and Low‑Latency Online Inference

Context

You are designing a feature store to support machine learning models that require:

  • Offline training on historical data.
  • Low-latency online inference at high QPS.

Assume an internet-scale social platform with entities such as user, item/content, and community. Models include recommendations, feed ranking, and abuse/spam detection.

Requirements

Specify and design the following:

  1. Functional and non-functional requirements (SLOs, scale assumptions).
  2. Feature ingestion for batch and streaming data.
  3. Computation and storage layers (offline/online) with point-in-time correctness.
  4. Feature serving APIs for training data generation and online inference.
  5. Offline–online consistency strategy.
  6. Freshness SLAs, backfills, and bootstrap flows.
  7. Lineage/metadata, governance, and access control.
  8. Deployment architecture and environments.
  9. CI/CD for feature definitions and pipelines.
  10. Testing strategies (unit, integration, end-to-end, data validation).
  11. Caching layers and eviction policies.
  12. Reliability/SLOs and fault tolerance.
  13. Monitoring/alerting and rollback processes.
  14. Cost and rate-limiting considerations.
  15. Component diagrams and justified technology choices.

Submit Your Answer to Earn 20XP

Sign in to leave a comment

Loading comments...