Meta Program / Project Manager Interview Questions

1.Tell me about a project you launched faster than anyone expected. How did you decide what to cut, and what did you fix after it shipped?

2.Tell me about a time you had to change course mid-project because early feedback showed your plan wasn't working. What specifically changed, and how fast did you move?

3.Walk me through a time you pushed for an approach your team or stakeholders thought was too risky or unconventional. How did you make the case, and what happened?

4.You've got five things on your plate and capacity for two. How do you actually decide which two? Give me a real example.

5.Tell me about a time you had to tell a senior stakeholder or a peer that their plan had a serious problem. What did you say, and when did you say it?

6.Has a program you managed ever had unintended negative effects on users or communities? How did you catch it, and what did you do?

7.Estimate the number of active advertisers running campaigns on Meta's platforms right now. Walk me through how you get there.

8.A metric you own — say, weekly active users on a new Messenger feature — has been flat for three straight weeks after a strong launch. No code changes shipped. How do you diagnose what's happening?

9.Meta is deciding whether to invest engineering resources in a program to reduce notification opt-out rates on Facebook versus a program to improve feed ranking for new users. How would you frame the tradeoff and make a recommendation?

10.You're the PM for a program to roll out a new privacy control feature across all Meta apps — Facebook, Instagram, WhatsApp, and Messenger. The legal team says you must ship by a hard regulatory deadline in 90 days. Engineering says the cross-app architecture work alone is 120 days. How do you close the gap?

11.You've just been told that a program you've been running for a year — a creator monetization initiative on Instagram — is being sunset because of a strategic pivot. You have 30 days to wind it down. How do you do it, and what does 'done' look like?

12.Meta is considering expanding WhatsApp's business messaging platform into a new market where SMS is still dominant and smartphone penetration is growing but only at 40%. How would you structure the go/no-go decision, and what would kill it for you?

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

14.How do you define 'done' for a program milestone, and what do you do when an engineering team says it's done but you don't agree?

15.You're running a program with five teams and your RAID log has three open blockers, two of which are marked 'owner TBD.' How do you resolve those, and what does your process look like for preventing TBD owners in the first place?

16.You're three weeks from a hard launch date for a new Instagram feature and QA just flagged that load testing is showing 15% higher latency than your SLA target at peak traffic. The engineering lead says they need two more weeks. What do you do?

17.You're asked to consolidate three overlapping programs — each owned by a different PM from a different org — into one coordinated roadmap. Two of the PMs are resistant because they're worried about losing visibility with leadership. How do you actually make this happen?

18.A senior stakeholder asks you to commit to a delivery date for a dependency you don't own — say, an API from the WhatsApp infra team. How do you respond, and what's your actual process for getting to a real date?

19.Your weekly status email to leadership goes out Friday. It's Thursday afternoon and you just realized two milestones you marked 'on track' last week are now slipping. What do you do?

20.You're running a cross-functional program and two engineering teams are each waiting on the other before they start their piece. Both team leads say the other team should go first. You're not the manager of either. How do you break the deadlock?

21.You're managing a Q3 roadmap commitment and halfway through the quarter you realize the scope is too large to ship by the deadline — but leadership has already announced this publicly in an earnings context. What's your move?

22.You've been handed a program that's been running for six months without a PM. There's a Jira board, a Slack channel, and a Google Doc with a roadmap from April — but no one can tell you what the current status actually is. How do you get oriented and establish control in the first two weeks?

23.You're running a high-priority program to launch a new monetization feature on Instagram. Three weeks before launch, your data science partner tells you the A/B test results look good on revenue but there's a statistically significant increase in user report rates on the surfaces where the feature appears. How do you handle it?

24.You're the PM for a global rollout across 15 markets — your US and EU launches went well, but a regional team in Southeast Asia is telling you the feature doesn't work for their use case and wants a two-month delay to build a localized variant. You're already behind schedule and your leadership is asking for full global coverage. What do you do?

25.Tell me about a time you had to get a team to adopt a new process or tool they didn't ask for. How did you get buy-in?

26.Describe a time a stakeholder kept pulling you into their priority at the expense of your program's top goal. How did you handle it?

27.Tell me about a time you had to align stakeholders from two very different functions — say, a product team and a finance or legal team — on a timeline that neither thought was realistic. How did you get to yes?

28.You're running a program and one of your key partners — say, a data science or engineering lead — goes quiet. They stop responding to pings, miss two syncs, and their deliverable is now on the critical path. What do you do?

29.Tell me about a time a major stakeholder — a VP, a key partner org, or a customer — was convinced your program was on track when you knew it wasn't. How did you handle that gap?

30.You've just found out that two senior stakeholders — say, a product VP and an ads monetization lead — have been telling their respective orgs completely different things about what your program will deliver. Both versions are wrong. How do you fix it?