Design cron scheduler and reward/review system

Quick Overview

This question evaluates system design competencies including distributed scheduling and workflow orchestration, multi-tenant isolation, scalability, reliability, operational observability, data modeling, and privacy/compliance for employee review and rewards.

Design cron scheduler and reward/review system

Company: DoorDash

Role: Software Engineer

Category: System Design

Difficulty: hard

Interview Round: Onsite

Design a company-wide scheduled job platform (cron-like) to run workflows across services. Requirements: schedule management (crontab, calendars, time zones), dependency graphs, retries/backoff, idempotency, backfills, concurrency control, access control, multi-tenant isolation, observability (logs/metrics/traces), failure alerting, and horizontal scalability. Discuss storage schemas, coordinator/worker architecture, and disaster recovery. Also design an employee review and rewards system that supports performance reviews, peer feedback, reward points/grants, approval flows, audit trails, and privacy; cover service boundaries, data models, integrations with HRIS/payroll, and abuse/fraud prevention.

Quick Answer: This question evaluates system design competencies including distributed scheduling and workflow orchestration, multi-tenant isolation, scalability, reliability, operational observability, data modeling, and privacy/compliance for employee review and rewards.

|Home/System Design/DoorDash
DoorDash logo
DoorDash
Sep 6, 2025, 12:00 AM
hardSoftware EngineerOnsiteSystem Design
11
0

System Design: Company-Wide Scheduler Platform and Employee Review & Rewards System

You are designing two platforms for a fast-growing, multi-tenant technology company. Address each part independently, but note any shared building blocks if relevant.

Part A — Company-Wide Scheduled Job Platform (Cron-like)

Design a horizontally scalable platform to run scheduled workflows across services.

Include:

  1. Scheduling and execution
    • Schedule management: crontab expressions, calendar/holiday exceptions, and time zones (DST-safe)
    • Workflow DAGs and task dependencies
    • Retries with exponential backoff and idempotency guarantees
    • Backfills for missed/retroactive runs
    • Concurrency control: global, per-tenant, per-workflow limits
    • Access control and multi-tenant isolation
  2. Reliability and operations
    • Observability: logs, metrics, traces; failure alerting
    • Horizontal scalability: sharding and stateless workers
    • Storage schemas for schedules, DAGs, runs, leases/locks, and audit
    • Coordinator/worker architecture: leader election, queues, heartbeats
    • Disaster recovery and operational runbooks

Discuss trade-offs (e.g., at-least-once vs exactly-once), and provide concrete storage schemas and component interactions.

Part B — Employee Review & Rewards System

Design a system that supports performance reviews and employee rewards with strong privacy and compliance.

Include:

  1. Core features
    • Performance review cycles (self/manager/peer), calibration, and peer feedback
    • Reward points/grants, redemption, policies, and approval workflows
    • Privacy/visibility controls and audit trails
  2. Architecture and integrations
    • Service boundaries and data models
    • Integrations with HRIS (org, titles, managers), SSO, and payroll/stock systems
    • Abuse/fraud prevention, rate-limiting, and anomaly detection
  3. Operations
    • Observability, SLAs, and disaster recovery
    • Data retention, legal holds, and regional data residency

Provide data schemas, state machines, and key workflows. Call out edge cases, safeguards, and scale assumptions.

Submit Your Answer to Earn 20XP

Sign in to leave a comment

Loading comments...