PracHub
QuestionsPremiumCoachesLearningGuidesInterview Prep
|Home/Software Engineering Fundamentals/DoorDash

Handle payment-service outages

Last updated: Mar 29, 2026

Quick Overview

This question evaluates a candidate's competence in designing fault-tolerant payment workflows and operational resilience, covering concepts such as idempotency, retry strategies, queuing and dead-letter handling, circuit breaking, reconciliation, and monitoring.

  • easy
  • DoorDash
  • Software Engineering Fundamentals
  • Software Engineer

Handle payment-service outages

Company: DoorDash

Role: Software Engineer

Category: Software Engineering Fundamentals

Difficulty: easy

Interview Round: Onsite

You own a service that computes courier payouts and then submits payout requests to a downstream payment processor. What should your system do if the payment service is temporarily unavailable, timing out, or returning intermittent errors? Discuss how to preserve correctness and a good user experience, including: - idempotency for payout requests - retries with exponential backoff and jitter - when to retry synchronously vs. asynchronously - circuit breaking and fallback behavior - queue-based recovery and dead-letter handling - reconciliation after the payment service recovers - monitoring and alerting

Quick Answer: This question evaluates a candidate's competence in designing fault-tolerant payment workflows and operational resilience, covering concepts such as idempotency, retry strategies, queuing and dead-letter handling, circuit breaking, reconciliation, and monitoring.

Related Interview Questions

  • How to prepare for AI-assisted coding interviews? - DoorDash (hard)
  • Build Resilient Aggregation and Debug Routing - DoorDash (medium)
  • Investigate High Memory Usage - DoorDash (medium)
  • Design an API for pay computation with retries - DoorDash (medium)
  • Debug and harden a driver-selection component - DoorDash (medium)
DoorDash logo
DoorDash
Jan 28, 2026, 12:00 AM
Software Engineer
Onsite
Software Engineering Fundamentals
8
0

You own a service that computes courier payouts and then submits payout requests to a downstream payment processor. What should your system do if the payment service is temporarily unavailable, timing out, or returning intermittent errors?

Discuss how to preserve correctness and a good user experience, including:

  • idempotency for payout requests
  • retries with exponential backoff and jitter
  • when to retry synchronously vs. asynchronously
  • circuit breaking and fallback behavior
  • queue-based recovery and dead-letter handling
  • reconciliation after the payment service recovers
  • monitoring and alerting

Solution

Show

Submit Your Answer to Earn 20XP

Sign in to leave a comment

Loading comments...

Browse More Questions

More Software Engineering Fundamentals•More DoorDash•More Software Engineer•DoorDash Software Engineer•DoorDash Software Engineering Fundamentals•Software Engineer Software Engineering Fundamentals
PracHub

Master your tech interviews with 8,000+ 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.