PracHub
QuestionsPremiumCoachesLearningGuidesInterview Prep
|Home/System Design/OpenAI

Design multi-tenant CI/CD workflow system

Last updated: Mar 29, 2026

Quick Overview

This question evaluates design skills for multi-tenant CI/CD platforms, covering event intake, workflow parsing and planning, orchestration and scheduling, runner isolation, live log streaming, and durable storage for runs, logs, and artifacts.

  • hard
  • OpenAI
  • System Design
  • Software Engineer

Design multi-tenant CI/CD workflow system

Company: OpenAI

Role: Software Engineer

Category: System Design

Difficulty: hard

Interview Round: Technical Screen

Design a multi-tenant CI/CD system that triggers on Git pushes. The system receives push information via an internal service API, including the repository ID and the current repository state. Workflows are defined as a sequence of jobs specified in a single YAML file located at a fixed path within each repository. Users must be able to view job output and execution status while runs are in progress. Describe the overall architecture, components for event intake, workflow parsing and execution, job scheduling, log/status streaming, and storage of run metadata. Explain how you would ensure tenant isolation, fairness, and fault tolerance.

Quick Answer: This question evaluates design skills for multi-tenant CI/CD platforms, covering event intake, workflow parsing and planning, orchestration and scheduling, runner isolation, live log streaming, and durable storage for runs, logs, and artifacts.

Related Interview Questions

  • Design an Instagram-like Feed System - OpenAI (medium)
  • Design Online Chess Matchmaking - OpenAI (hard)
  • Design a Distributed Crossword Solver - OpenAI (hard)
  • Design a Distributed Rate Limiter - OpenAI
  • Design a Distributed Crossword Solver - OpenAI (medium)
OpenAI logo
OpenAI
Aug 8, 2025, 12:00 AM
Software Engineer
Technical Screen
System Design
8
0

Design a Multi-Tenant CI/CD System Triggered by Git Pushes

Context and Assumptions

  • An internal service sends a push event for each Git push containing: tenant ID, repository ID, and repository state (e.g., commit SHA, branch).
  • Each repository defines a workflow in a single YAML file at a fixed path (for example, .ci/workflow.yaml).
  • A workflow is a sequence (or DAG) of jobs; each job has steps/commands and may depend on others.
  • Users must be able to see live job logs and execution status while runs are in progress.

Requirements

Describe the overall architecture and these components:

  1. Event intake and trigger handling.
  2. Workflow YAML retrieval, parsing, and execution planning.
  3. Orchestration and job scheduling.
  4. Execution/runners and isolation model.
  5. Live log and status streaming to users.
  6. Storage of run metadata, logs, and artifacts.
  7. Cross-cutting: tenant isolation, fairness, and fault tolerance.

State design choices, key data flows, and how the system scales.

Solution

Show

Comments (0)

Sign in to leave a comment

Loading comments...

Browse More Questions

More System Design•More OpenAI•More Software Engineer•OpenAI Software Engineer•OpenAI 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.