Intervu is in beta — feedback welcome at support@intervu.io

DoorDash Engineering Manager Interview Questions

15 real practice questions for the senior-level Engineering Manager role at DoorDash (Technology/Logistics), spanning behavioral. Lead engineering teams, manage people and processes, and drive technical strategy. The first 3 questions below include what DoorDash interviewers actually listen for, plus likely follow-ups.

Questions
15
Categories
Behavioral (15)
Difficulty mix
5 easy · 5 medium · 5 hard
Avg. answer time
~4 min

Behavioral Questions (15)

  1. 1.Tell me about a time when someone on your team or a partner was struggling, and you went beyond your normal responsibilities to help them succeed.

    easy~3 min

    What interviewers look for

    • Shows Hustle and Heart by demonstrating genuine care for team members or partners beyond just delivering results
    • Provides specific examples of extra effort or support that went above standard management duties
    • Demonstrates impact on both the individual's success and broader team dynamics or outcomes

    Likely follow-ups

    • What was the impact on that person's performance or career after you helped them?
    • How do you balance investing time in struggling team members with your other responsibilities?

    Company context

    DoorDash's Hustle and Heart principle emphasizes that intense work ethic must be combined with genuine care for people - teammates, Dashers, merchants, and consumers. Engineering managers are expected to show this care through actions, not just words, especially when team members are facing challenges.

  2. 2.Walk me through how you'd design the system architecture for batching multiple restaurant orders to a single Dasher, considering that each restaurant has different prep times and the Dasher needs to maintain food quality.

    easy~3 min

    What interviewers look for

    • Considers the three-sided marketplace impact - optimizing for consumer wait time, Dasher earnings efficiency, and merchant order fulfillment
    • Designs for real-time constraints with sub-minute decision making and discusses event-driven architecture using Kafka or similar
    • Addresses food quality concerns through temperature monitoring, time windows, and order routing logic

    Likely follow-ups

    • How would you handle the case where one restaurant is significantly delayed - would you reassign the batch or wait?
    • What metrics would you track to ensure this batching system is actually improving the experience for all three sides?

    Company context

    DoorDash's batching system is core to Dasher earnings optimization and consumer experience. This tests understanding of DoorDash's Three-Sided Marketplace Thinking principle and the operational complexity of real-time logistics decisions that affect food quality and delivery economics.

  3. 3.Design the ETA prediction system that powers delivery time estimates across DoorDash's consumer app and Dasher platform. This system needs to provide accurate estimates for millions of orders daily while accounting for real-time traffic, restaurant prep times, and Dasher location.

    easy~3 min

    What interviewers look for

    • Identifies the multi-sided marketplace challenge - ETA accuracy affects consumer expectations, Dasher route planning, and merchant operations
    • Proposes a microservices architecture with separate services for traffic data, restaurant prep time modeling, and Dasher location tracking
    • Discusses real-time data processing using Kafka and Apache Flink for continuous ETA updates as conditions change
    • Considers fallback mechanisms when ML models are unavailable, such as historical averages by time of day and geography

    Likely follow-ups

    • How would you handle the scenario where your ETA prediction is consistently off by 10+ minutes in a specific geographic area?
    • Walk me through how you'd validate that your ETA improvements are actually helping all three sides of the marketplace, not just consumers.

    Company context

    DoorDash's 'Three-Sided Marketplace Thinking' principle requires engineers to consider how ETA accuracy affects consumers (wait time expectations), Dashers (route efficiency and earnings), and merchants (order volume and customer satisfaction). The company's 'Operate at Speed' principle emphasizes the importance of real-time systems that can adapt to changing conditions across millions of daily deliveries.

  4. 4.Tell me about a time you had to coordinate multiple engineering teams to solve a problem that was hurting our operational partners - like merchants or Dashers. How did you align everyone around the solution?

    easy~4 min
  5. 5.We're seeing a 15% drop in merchant satisfaction scores, but order volume and revenue are actually up 8% month-over-month. How would you investigate what's driving this disconnect and prioritize which issues to tackle first?

    easy~3 min
  6. 6.Tell me about a time when you had to balance competing needs between different stakeholders - like improving one group's experience while potentially impacting another. How did you approach that decision?

    medium~4 min
  7. 7.Your team is migrating a critical pricing service from our legacy Python monolith to Kotlin microservices. The service handles dynamic pricing for millions of orders daily. How would you plan and execute this migration without disrupting live traffic?

    medium~4 min
  8. 8.Design a system to handle DashPass subscription billing and benefits management for millions of subscribers. The system needs to track subscription status, apply benefits in real-time during checkout, and handle edge cases like failed payments or subscription changes.

    medium~4 min
  9. 9.Your engineering team is responsible for a service that's experiencing latency spikes during peak dinner hours, affecting order assignment across three major cities. Walk me through how you'd diagnose this and mobilize your team to fix it while orders are still coming in.

    medium~5 min
  10. 10.Estimate how many additional Dashers DoorDash would need to hire if we expanded same-day grocery delivery from our current 20 cities to all 300+ cities where we operate. Walk me through your assumptions and calculation.

    medium~4 min
  11. 11.Describe a situation where you had to make a critical technical decision under tight time pressure. What was the decision, and how did you ensure quality while moving fast?

    hard~5 min
  12. 12.Design a real-time system that can detect and prevent fraudulent orders across DoorDash's marketplace while minimizing false positives that would hurt legitimate consumers and merchants. Consider that we process millions of orders daily across different geographies.

    hard~5 min
  13. 13.Design the dispatch system that assigns orders to Dashers for DoorDash Drive, our white-label API used by enterprise merchants. This system needs to respect merchant-specific preferences while maintaining delivery efficiency and Dasher earnings across multiple enterprise clients.

    hard~5 min
  14. 14.Describe a time when you had to convince senior leadership to invest engineering resources in platform work or technical improvements that wouldn't directly ship user-facing features. How did you build that business case?

    hard~5 min
  15. 15.Your team owns the pricing engine that sets delivery fees and service fees for consumers. A new PM wants to run an experiment reducing DashPass member fees by 50% in 10 cities to drive subscription growth. How would you evaluate whether your pricing infrastructure can handle this experiment and what risks you'd flag?

    hard~5 min

More DoorDash interview questions