A Stripe REST API ingestion job paginates by stopping at the first empty response, burns its rate bu
A medium Pipeline Design mock interview question on DataDriven. Practice with AI-powered feedback, real code execution, and a hire/no-hire decision.
- Domain
- Pipeline Design
- Difficulty
- medium
Interview Prompt
A Stripe REST API ingestion job paginates by stopping at the first empty response, burns its rate budget in the first five minutes of every run, and lets the OAuth token expire mid-pagination with no refresh. Three Stripe outages a month show up in the pipeline as silent partial loads. The section names four concerns of API ingestion: pagination (cursor-based is the strongest), rate limits (respect Retry-After), auth (refresh before expiry), and reliability (retry with backoff on 429 and 5xx). Add the rate limiter by replacing the API ingest transform with one whose name states cursor-based pagination, a rate-limiter that respects Retry-After, an OAuth refresh policy, and retry-with-backoff on 429 and 5xx.
How This Interview Works
- Read the vague prompt (just like a real interview)
- Ask clarifying questions to the AI interviewer
- Write your pipeline design solution with real code execution
- Get instant feedback and a hire/no-hire decision