Figma Program / Project Manager Interview Questions

1.Tell me about a project process you redesigned specifically because non-technical stakeholders couldn't follow the original one. What did you change and how did you know it worked?

2.Tell me about a deliverable you shipped — a roadmap, a tracker, a status doc — where you went significantly beyond 'good enough.' What made you decide it was worth the extra investment?

3.Describe a time you had to coordinate multiple teams working toward a shared deadline where information was changing faster than your normal update cadence could handle. How did you keep everyone aligned?

4.Tell me about a time you gave someone direct feedback they clearly didn't want to hear. How did you approach it, and what happened to the relationship afterward?

5.You're running a program that involves five teams, and you realize the process you designed is creating more overhead than it's eliminating — teams are spending more time on your updates than doing actual work. How do you fix it without losing the coordination you need?

6.Tell me about a time you were managing a program toward a critical launch and discovered midway through that a key dependency — a decision, a resource, or an output from another team — wasn't going to arrive on time. Walk me through exactly what you did.

7.Estimate how many active Figma organizations have more than 50 seats. Walk me through how you'd get to a number.

8.You're tracking a program in Figma and notice that one team consistently marks their tasks 'complete' on Friday afternoon but the dependent team always reports blockers on Monday morning. How do you investigate what's actually happening?

9.FigJam's weekly active usage dropped 12% month-over-month. You're the PM running the growth program for it. How do you figure out what's driving the drop, and what do you do first?

10.You're running a program to reduce the average time-to-value for new Figma enterprise customers — currently about 90 days from contract to first active team. Your goal is 60 days. Where do you start, and how do you know if your interventions are working?

11.Figma is considering consolidating three separate internal tracking systems — used by Design, Engineering, and Product — into a single source of truth. You're asked to scope the program. What's your estimate of the effort, and what are the three biggest risks you'd flag before committing to a timeline?

12.You're PM on a program to launch a major update to Figma's enterprise admin controls. Six weeks before launch, the Legal team flags a potential data residency compliance gap for EU customers that Engineering says will take 4–6 weeks to resolve. You can't slip the launch and you can't ship a compliance gap. What do you do?

13.Walk me through how you build and maintain a program status report that executives actually read and act on. What's in it, and what do you leave out?

14.You're running a program kickoff for a new workstream. How do you scope the RACI, and how do you decide when a role should be 'Responsible' versus 'Accountable' when multiple teams legitimately own a piece?

15.You're three weeks into a 12-week program and your milestone dates are slipping by two days each week. How do you diagnose whether this is a planning problem, a resource problem, or an execution problem — and what do you do differently based on the answer?

16.A product team wants to add a significant feature to a program you're running, and their estimate is 'a few weeks' — but your program closes in six weeks. How do you evaluate whether to take it in?

17.Figma is preparing to launch a new capability in Dev Mode. You're the PM coordinating Engineering, Product Design, Developer Relations, and the Enterprise Sales team. Two of those teams have conflicting definitions of 'done' for launch. How do you resolve it before it becomes a launch blocker?

18.You're handed a program that's been running for two months without a PM. There's no single source of truth, teams have diverged on scope, and the launch date is eight weeks away. How do you take control without creating chaos in the process?

19.A Figma enterprise customer is mid-onboarding and their champion just went on leave. The new point of contact says they want to pause the rollout. What do you do in the next 24 hours?

20.You're PM on a FigJam feature rollout and you realize the help documentation, in-product tooltips, and the external blog post are all describing the feature differently. Launch is in three days. What do you do?

21.You're running a cross-functional program for a Figma Slides launch and Engineering tells you they're on track, but the Designer lead keeps saying 'it's not ready' without specifics. Launch is four weeks out. How do you get to the truth?

22.You're the PM on a program to roll out a new internal tooling standard across six product teams. Two teams adopt it immediately, two are slow but cooperative, and two are openly resistant. You have no direct authority over any of them. How do you move all six forward?

23.A senior engineer on your program tells you privately that another team's technical approach is going to cause serious integration problems down the line, but they don't want to raise it publicly because of an existing political tension with that team's tech lead. Launch is ten weeks away. What do you do?

24.It's two weeks before a major Figma enterprise customer conference and you discover that the demo environment — which three teams have been building toward — doesn't actually showcase what was promised in the event marketing. The gap is real and significant. What do you do?

25.Tell me about a time you had to get buy-in from a stakeholder who had no reason to prioritize your program. What was your approach?

26.Describe a time you had to represent a customer's concern internally and the team pushed back. How did you advocate for the customer without burning bridges?

27.You're coordinating a program across Sales, Marketing, and Product — and you realize all three have made commitments to different external audiences that are now in conflict. None of the three teams see it as their problem to fix. What do you do?

28.Tell me about a time you had to deliver bad news to a senior leader or executive — something that was going to change their plans significantly. How did you prepare, and how did they react?

29.You're managing a cross-functional program and a key partner team — say, Enterprise Sales — starts going directly to Engineering to make scope requests, bypassing you entirely. The Engineering team is responding. How do you handle it?

30.Tell me about a time you were managing toward a major milestone and discovered that two senior stakeholders — both above you — had fundamentally different views of what success looked like. How did you get them aligned?