Amazon Program / Project Manager Interview Questions

1.Tell me about a time a program you were managing wasn't delivering what customers actually needed. How did you figure that out, and what did you change?

2.Walk me through a time you inherited a process that was overly complicated and managed to simplify it. What specifically did you cut or change?

3.Describe a situation where a critical problem fell outside your program's scope, but you stepped in anyway. What was the risk and what did you do?

4.Tell me about a time something you thought you understood well turned out to be wrong — and how that changed how you ran your program.

5.Tell me about a time you had to make a go or no-go call on a program with significant data gaps. What did you decide and how did you defend it?

6.Tell me about someone on your team or a cross-functional partner you invested in developing. What specifically did you do, and where are they now?

7.Estimate how many active third-party sellers are currently on Amazon Marketplace. Walk me through your assumptions.

8.A key fulfillment metric — say, on-time delivery rate for Prime — drops 3 percentage points in a single week with no obvious external cause. How do you diagnose it?

9.You're asked to cut 20% of the scope from a program without moving the launch date. How do you decide what goes and what stays?

10.Estimate the annual cost to Amazon of a 1% increase in Prime package damage rates. Walk me through how you'd build that model.

11.You're the PM for an AWS cost optimization feature that would save enterprise customers millions, but the engineering team tells you it'll require six months of platform work — and your VP wants it shipped in three. How do you resolve that gap?

12.You're running a program to improve delivery speed for Amazon Fresh in three new metro markets. Four weeks before launch, internal data shows projected unit economics are 15% worse than the business case assumed. Leadership hasn't seen it yet. What do you do?

13.Walk me through how you build and maintain a program status dashboard — what metrics do you track, and how do you decide what's worth surfacing to leadership?

14.How do you scope a new program from scratch? Take me through the first two weeks — what do you do, in what order, and what are you trying to lock down before anything else?

15.You're running a cross-functional program with six teams contributing, and you notice two teams are consistently missing their weekly commitments — but neither is flagging it as a risk. How do you diagnose what's actually going on and get it back on track?

16.You're managing a program with a fixed launch date tied to an Amazon Prime event — the timeline is non-negotiable. Three weeks out, your critical path has slipped by two weeks. Walk me through exactly what you do.

17.You've been asked to lead a program that requires coordinating teams across AWS, Amazon retail, and a third-party partner — all with different planning cycles, toolsets, and incentives. How do you design the operating model so it doesn't collapse under its own weight?

18.Halfway through a major program, your data shows you're on track to deliver on time, but a deep dive reveals the success metrics you locked at kickoff are no longer aligned with what the business actually needs. How do you handle it — do you redefine the metrics, or do you hold the line?

19.You're running a program and a stakeholder from a senior team asks you to add a last-minute deliverable that's clearly out of scope — but they frame it as a small ask. How do you handle it?

20.You've just taken over a program that's six weeks from launch and you discover the RACI hasn't been agreed to — three different teams think they own the same decision. What do you do in the next 48 hours?

21.Your program is greenlit, but two weeks in, you realize the resourcing commitment from a key engineering team was based on capacity estimates that are now clearly wrong — they're 50% under-staffed for what you need. The VP sponsor hasn't been told yet. What do you do?

22.You're managing a high-visibility program and your weekly metrics show green across the board — but you've just heard through informal channels that one of your downstream customers is actually frustrated with how the program is rolling out. The data doesn't show it yet. What do you do?

23.You're running a cross-functional program and you discover that two teams have been doing redundant work for four weeks — each built a separate solution to the same problem without knowing about each other. Now one team's work will have to be thrown away, and they're not happy. How do you handle the immediate fallout and prevent it from derailing the program?

24.Three days before a major customer-facing launch, a security review flags a potential vulnerability in one of your program's components. The security team says they need two more weeks to validate it. Your business sponsor is pushing hard to launch on time. How do you make the call?

25.Tell me about a time you had to get a team or partner to commit to something when you had no authority over them. What was your approach?

26.Describe a time you had to give a stakeholder or senior leader an update they didn't want to hear. How did you frame it and how did they react?

27.Tell me about a time different stakeholder groups wanted different things from your program — and you couldn't fully satisfy all of them. How did you decide who got what?

28.You're running a program that depends on a finance or legal partner who's consistently slow to review and approve — and it's threatening your timeline. You have no authority over them. What do you do?

29.Tell me about the most senior stakeholder you've pushed back on. What was the situation, how did you make your case, and what happened?

30.You've delivered everything your internal stakeholders asked for, on time, but the end customer — an Amazon seller, an AWS account, or an internal business team — is still dissatisfied. How do you handle it, and who owns the problem?