Adobe Program / Project Manager Interview Questions

1.Tell me about a time you pushed for a new approach to managing a project or program that your team or stakeholders were skeptical about. How did you get them on board?

2.Tell me about a time a team member or collaborator's perspective wasn't being heard in a planning or decision-making process. What did you do, and what changed as a result?

3.Describe a situation where a customer or end user was at risk of a bad experience because of how a program was being run. What did you personally do to fix it?

4.Walk me through a time you identified a recurring failure or bottleneck in a program or delivery process and drove a fix that stuck. What made it stick?

5.Describe a time you were running a program and the data told you something was wrong — even though the team thought things were on track. How did you convince them to change course?

6.Tell me about a time you proposed a fundamentally different way to structure or sequence a program — not just a process tweak — that required other teams to change how they worked. How did you make it happen?

7.Estimate how many Creative Cloud individual subscribers Adobe could convert to a family or team plan in the next 12 months. Walk me through how you'd size that opportunity.

8.Acrobat's weekly active users drop 8% week-over-week with no obvious product change deployed. How do you start diagnosing it, and what do you rule out first?

9.Adobe is planning to sunset a legacy Photoshop export feature that roughly 15% of desktop users still use regularly. How would you manage the migration program to minimize user disruption?

10.You're managing a program to roll out a new AI-assisted feature in Adobe Express to small business customers. Three months out from launch, usage research shows the target customer doesn't understand what the feature does. How do you assess whether this is a PM scope issue or something your program needs to fix?

11.Adobe is considering whether to build a new integration between Experience Cloud and Creative Cloud that would let marketing teams publish campaign assets directly from Photoshop. Estimate the annual engineering cost versus potential revenue impact, and tell me whether you'd recommend building it.

12.You're running a program with four dependent teams, and two weeks before a hard deadline, your resourcing model shows you're 30% under-staffed for the remaining work. Leadership says headcount is locked. How do you close the gap?

13.Walk me through how you build and maintain a program roadmap when you're coordinating across multiple teams with different sprint cadences.

14.How do you define 'done' for a program milestone, and what do you do when different teams have conflicting definitions?

15.You're managing a program with a hard external launch date — say, a major Firefly feature tied to Adobe MAX — and your critical path just slipped by two weeks. How do you respond in the first 48 hours?

16.How do you build and manage a risk register for a complex program — and how do you make sure it actually drives decisions rather than sitting in a spreadsheet no one reads?

17.You're running a program that touches three product lines — say, a cross-cloud integration between Creative Cloud, Document Cloud, and Experience Cloud — and each has its own GM with different quarterly priorities. Two of the three GMs want to cut the same feature. How do you proceed?

18.A program you own is consistently hitting its milestones on paper, but post-launch adoption metrics for the feature are significantly below target. How do you diagnose whether this is a program management problem, a product problem, or something else — and what do you do about it?

19.You're coordinating a program across three teams, and mid-sprint you realize one team's deliverable has a dependency on a tool license that hasn't been approved yet. The approval process takes two weeks and your milestone is in ten days. What do you do?

20.Your program's status dashboard shows green across the board, but you just got off a call with a lead engineer who casually mentioned the team has been carrying a known technical debt issue that could destabilize the feature in production. It's not on any risk register. What's your next move?

21.You're running a program to launch a new Adobe Express template feature for small business customers. Two weeks before launch, the marketing team tells you they need an additional four weeks to build out the go-to-market materials. Engineering is ready to ship. What do you do?

22.Halfway through a quarter, you're told that a senior executive wants a new high-visibility initiative added to your already full program backlog — and they want a delivery date for end of quarter. Your current commitments have no slack. How do you respond?

23.You're managing a cross-functional program to integrate an AI-powered feature into Acrobat. Four weeks before GA launch, your security review flags a potential data privacy concern with the AI model's training data. Legal says the risk is 'moderate,' engineering says it's 'unlikely to matter,' and the product lead is pushing to ship on time. What do you do?

24.You've just taken over a program mid-flight that was being run by a PM who left the company. The team seems to be moving, but there's no clear source of truth for scope, no updated RACI, and you've heard two different versions of what the launch actually includes from two different team leads. You have a stakeholder review in 72 hours. What do you do?

25.Think about a time you needed a team or partner to prioritize your program's work, but you had no authority over them. How did you get them moving?

26.Describe a time you had to brief an executive on a program and the news wasn't good. How did you prepare and how did the conversation go?

27.Tell me about a time you and a peer from another function — say, a finance partner or a marketing lead — had a fundamental disagreement about how a program should move forward. How did you resolve it?

28.You're running a program with a key enterprise customer stakeholder who keeps moving the goalposts on requirements — every check-in surfaces new asks. How do you handle it without damaging the relationship?

29.Tell me about a time you saw two stakeholder groups — say, a product team and a go-to-market team — operating on fundamentally different assumptions about what was being built. How did you surface it, and who had to be wrong?

30.You've been running a program for six months and you realize the executive sponsor has been telling their peers the program will deliver something materially different from what you've been building toward. You find out through a third party, not the sponsor directly. What do you do?