senior software engineer

Build Middleware for 3rd-Party Ticketing

Clarify · 5:00

Design middleware that ingests and normalizes ticket inventory and event updates from multiple third-party providers, then serves reliable internal and partner-facing interfaces.

Known Requirements

  • • Integrate multiple providers with different APIs and payload shapes
  • • Normalize external data into a stable canonical model
  • • Handle near-real-time updates with idempotent processing
  • • Expose dependable downstream interfaces with clear SLAs
  • • Support provider-specific operational controls and runbooks

Constraints

  • • Providers enforce strict rate limits and can degrade partially
  • • Schema and semantic drift is frequent across providers
  • • Duplicate and out-of-order updates are common
  • • Incorrect inventory state can cause user trust and revenue impact
  • • The system must isolate provider failures to reduce blast radius

Clarifying Questions

Ask up to five questions. Reveal constraints by being specific.

5 questions remaining

    Reveals

    • Ask a question to reveal more constraints.

    Phase Control

    Advance when ready or let the timer move you forward.