DoorDash Program / Project Manager Interview Questions

1.Tell me about a project where improving one group's experience unintentionally hurt another group. How did you find out, and what did you do?

2.Tell me about a time you stepped in to help a teammate or cross-functional partner who was struggling — something that was clearly outside your job description. What made you do it?

3.Tell me about a time you had to compress a project timeline significantly — weeks into days, or days into hours. What specifically did you cut, defer, or parallelize to make it work?

4.Walk me through a time you had to make a product or program decision that genuinely required you to trade off one user group's experience against another's. What was the call, and how did you know it was the right one?

5.Tell me about a time you discovered that a program or initiative you were managing was creating a bad experience for a stakeholder group that wasn't in the original requirements. How did you surface it and what happened?

6.Your program is the critical path for a launch that's six days out, and you've just learned a key dependency — owned by a team in a different org — is two weeks behind. What do you do in the next 24 hours?

7.Estimate how many Dashers DoorDash would need to add in a mid-sized city like Denver to cut average delivery time by five minutes. Walk me through your math.

8.You're running a program to improve DashPass renewal rates and your weekly active orders metric is flat — no movement after four weeks of effort. Where do you start looking, and what would you actually do?

9.A new merchant onboarding program you manage has hit its 90-day activation target, but your ops team just flagged that support ticket volume from newly onboarded merchants is 3x higher than average. How do you think about whether this program is actually succeeding?

10.Estimate how much GMV DoorDash could unlock by reducing Dasher-to-restaurant wait time by three minutes. Assume you're focused on the top 20 markets.

11.You've been asked to own the rollout of a new Dasher pay feature across 15 markets in 10 weeks. Halfway through, two markets are ahead of schedule, ten are on track, and three are significantly behind — and those three markets represent 40% of total Dasher volume. How do you run the rest of the program?

12.You're running a program to expand DoorDash into five new suburban markets over six months. Three weeks before the first launch, your City Operations lead tells you the local restaurant sign-up rate is 30% below the threshold your consumer team requires to go live. You own the program but don't own either the merchant sales team or the consumer product team. What do you do?

13.Walk me through how you set up a project tracker for a multi-team initiative. What fields matter most and why?

14.How do you define 'done' for a program launch, and what does your standard post-launch checklist look like?

15.You're managing a program with three workstreams, each with a different owner, and the overall deadline is fixed. Two of the three workstreams are on track, but the third is consistently missing its weekly milestones. How do you diagnose what's happening and decide what to do about it?

16.How do you build and maintain a RACI for a program that keeps changing scope mid-flight? What breaks down and how do you fix it?

17.You're managing a program where the success metric is merchant activation rate on a new DoorDash Drive feature. Halfway through the rollout, activation is 40% below target. Walk me through how you diagnose the problem and what you'd actually do about it.

18.You're asked to run a quarterly business review for a program with five stakeholder groups who care about completely different metrics. How do you structure it so it's actually useful rather than a 90-minute slide deck no one reads?

19.You're running a new Dasher onboarding program and you realize that the weekly status report you've been sending to three VP stakeholders has different numbers in it — the data sources don't agree. What do you do?

20.A merchant success manager tells you informally that the merchant-facing rollout you're managing is causing confusion — merchants are calling in asking questions that your training materials were supposed to answer. You're mid-launch and not scheduled to do a formal retrospective for three weeks. What do you do?

21.You're six weeks into a DashPass subscriber engagement program and the one metric your VP cares about — weekly order frequency — is up 8%, but churn rate is also up 12%. Leadership is calling it a win. How do you handle that?

22.You've just been handed a program that was previously run by someone who left the company. The handoff doc is thin, there are four active workstreams, and the next stakeholder review is in nine days. How do you get yourself ready?

23.Two teams you depend on for a consumer-facing launch have just told you they each need the other team to finish first — it's a genuine circular dependency. The launch is four weeks out and neither team will move. What do you do?

24.You're three weeks from launching a new merchant tool to 5,000 restaurants on DoorDash. Your pilot data shows strong engagement, but you've just learned the pilot group was all large national chains — not the local independent restaurants that make up the majority of the launch target. What do you do?

25.Tell me about a time you had to get a team to commit to a deadline they didn't set and didn't agree with. How did you get there?

26.Tell me about a time you had to deliver bad news to a stakeholder — something meaningful was going to be late, cut, or changed. How did you do it and how did they react?

27.Describe a situation where two senior stakeholders had fundamentally different opinions about the direction of a program you owned. How did you drive alignment without being seen as picking a side?

28.Tell me about a time you were managing up to an exec sponsor who was disengaged — not showing up to reviews, slow to respond, and the program was starting to feel it. What did you do?

29.You're managing a cross-functional program and one of your key partners — someone you depend on but don't manage — starts consistently representing their team's position in stakeholder meetings before aligning with you privately. It's creating confusion and making the program look disorganized. How do you handle it?

30.Tell me about a time a senior stakeholder pushed you to commit to a plan you genuinely believed was wrong — not just uncomfortable, but actually likely to fail. What did you do?