Anthropic Program / Project Manager Interview Questions

1.Tell me about a project where you pushed back on a deadline because you were worried about reliability or safety risks. How did you make that call, and what happened?

2.Describe a time you were mid-project and new information forced you to fundamentally rethink your plan. What did you do once you realized the old approach was wrong?

3.Tell me about a time you had to coordinate a project that bridged research and engineering — where the researchers had a theoretical goal and your job was to turn it into something that shipped. What made that hard, and what did you do about it?

4.Walk me through a career or project decision you made where your personal values were a bigger factor than the obvious business case. What were you weighing, and how did you land?

5.Tell me about a time you were managing a project where a known risk materialized mid-flight and affected users or customers. How did you handle the response, and what did you change afterward?

6.Describe a project where you were tracking a key metric and the data started telling you something you didn't want to hear — it suggested your current approach wasn't working. Walk me through what you did.

7.Estimate how many enterprise customers Anthropic would need to add this year to double Claude for Enterprise revenue. Walk me through your assumptions.

8.Usage of Claude's API dropped 12% week-over-week and nothing in the changelog looks obviously related. How do you start diagnosing it?

9.You're planning a program to reduce the average time-to-value for new Claude API customers — right now it takes most developers about three weeks to get their first meaningful integration working. How do you figure out where the time is going and what to fix first?

10.Anthropic wants to run a pilot of Claude with five school districts before a broader education launch. How would you structure the pilot to actually tell you what you need to know before scaling?

11.You're the PM for a program to ship a significant Claude capability update — the research team says it's ready, but your internal evals show a 3% increase in a specific category of harmful outputs compared to the previous version. Leadership wants to ship on the original date. How do you think through this?

12.You've been asked to build a program operations dashboard that will be used by five different teams — research, engineering, product, safety, and go-to-market. Each team has different information needs and the data sources aren't all in one place. How do you approach this?

13.How do you structure a project kickoff for a cross-functional initiative — what does your standard setup look like and what do you make sure is in place before work starts?

14.Walk me through how you track project health week-to-week. What are the 3-4 signals you watch, and how do you decide when something needs escalation?

15.You're managing a program that has six teams contributing to a single launch — one of those teams tells you at week 8 of 12 that they need three more weeks. How do you respond, and what options do you evaluate before going to leadership?

16.Imagine you're managing a roadmap for a team building on top of the Claude API — engineering wants to build what they think users need, product is getting signal from enterprise customers, and safety research has flagged a constraint on one capability. How do you run the prioritization process?

17.You've just taken over a program that's been running for two months with no formal project plan, inconsistent status reporting, and three competing views on what 'done' means. What do you do in your first two weeks?

18.You're running a program to launch a new Claude for Enterprise feature with four partner organizations doing early access. Two weeks before GA, one partner reports a serious reliability issue that you can't reproduce internally. How do you manage the next 72 hours?

19.You've been asked to run a retrospective on a project that shipped on time but got negative feedback from users shortly after launch. How do you structure that conversation and what are you trying to learn?

20.You're coordinating a cross-functional initiative and two stakeholders send you conflicting written instructions about a key deliverable — both believe they're the decision-maker. What do you do before your next status meeting?

21.You're managing a program with a hard external deadline — a major enterprise customer has contractually committed to a go-live date. Three weeks out, your engineering lead tells you the feature will be ready, but it hasn't gone through the full safety review process yet. How do you handle this?

22.You're running a quarterly planning process for a product team and you realize halfway through that three of the five proposed initiatives are solving for the same underlying user problem in different ways — but nobody has named that conflict out loud. What do you do with that observation?

23.You're midway through a high-visibility program when a team member raises a concern to you privately — they believe a design decision the tech lead made will create a misleading user experience in an edge case, but they're junior and worried about speaking up. What do you do?

24.You're managing a program that depends on research output from a team working on a novel capability for Claude — they've hit an unexpected technical wall and their timeline has become genuinely uncertain. You have downstream commitments to product and enterprise partners that assumed a delivery date. Walk me through how you manage the next two weeks.

25.Tell me about a time you had to get buy-in from a partner team — sales, finance, recruiting — who had different incentives than yours. How did you get them aligned?

26.Think of a time you kept a senior executive informed on a program — not just upward reporting, but actually managing what they paid attention to. What did that look like?

27.Describe a time you needed something critical from a team you had no leverage over — no shared manager, no budget, no deadline they cared about. How did you get it done?

28.Tell me about the most uncomfortable message you've ever had to deliver to an external customer or partner — something they really didn't want to hear. How did you approach it and what happened?

29.You're running a cross-functional program and one of your key stakeholders — someone whose team is contributing to the work — starts quietly disengaging. They stop showing up to syncs, their team's deliverables are slipping, but they haven't told you anything is wrong. What do you do?

30.Tell me about a time you had to push back on a senior leader's decision — not a technical disagreement, but a strategic or prioritization call they made that you thought was wrong. How did you handle it, and what happened?