Slack Program / Project Manager Interview Questions

1.Tell me about a time a quieter person on your team had an idea or concern that wasn't getting airtime. How did you bring it forward, and what changed because of it?

2.Describe a time you gave feedback on someone's work — a doc, a plan, a spec — and the feedback was harder to deliver than just flagging a typo. What did you say, and how did you frame it?

3.Tell me about a time customer feedback — from a user, a support ticket, a sales call, anything — changed what you actually built or prioritized. What did you hear, and what did you do with it?

4.Walk me through a disagreement you had with a partner team — engineering, design, sales, whoever — where you genuinely thought they were wrong. How did it resolve, and do you think you got to the right answer?

5.Tell me about a cross-functional project where someone's input was being systematically overlooked — not because they were wrong, but because of how the team was structured or who had the loudest voice. What did you do about it?

6.Tell me about a time you received feedback on a deliverable — a roadmap, a project plan, a stakeholder update — that fundamentally changed how you thought about the work, not just how you polished it. What was the feedback and what did you actually change?

7.Estimate how many active Slack workspaces there are globally right now. Walk me through how you'd get to a number.

8.Slack's weekly active usage in a specific enterprise customer's workspace has dropped 25% over the past month. You're the program manager for that account. How do you diagnose what's happening?

9.You're asked to estimate the annual cost to Slack of poor meeting culture — people scheduling calls instead of using Huddles or async channels. How would you frame the problem and what's your rough number?

10.A Slack Workflow Builder automation that an enterprise customer relies on for their daily stand-up process stops triggering correctly after a Slack platform update. The customer contacts you directly. How do you manage the next 24 hours?

11.Slack is considering whether to invest in a self-serve onboarding program for mid-market customers — companies between 100 and 1,000 seats — to reduce reliance on CSMs for basic onboarding. How would you structure the analysis to decide if this is worth building?

12.Slack's Huddles feature has strong engagement among engineering teams but low adoption in sales and customer success orgs. You're asked to run a 90-day program to close that gap. How do you design the program, and how do you measure whether it worked?

13.You're running a Slack Workflow Builder rollout for a 500-person enterprise customer. Walk me through how you'd track whether the rollout is actually working.

14.What's your go-to method for building and maintaining a project schedule when your dependencies span three or more teams who each have their own sprint cadences?

15.A Slack Connect channel shared between your company and a strategic partner has become the coordination hub for a major integration project. Two weeks before go-live, you discover that three critical action items have been sitting unowned in that channel for 10 days. How do you recover?

16.You're asked to build the program plan for launching a new Agentforce integration in Slack to a subset of enterprise customers. How do you scope phase one, and how do you decide what gets cut?

17.You're the program manager for a Slack Huddles feature launch that's slipped twice. Engineering is asking for two more weeks; sales is threatening to pull committed deals if it slips again; and the product lead wants to ship a reduced scope instead. You have to make a recommendation by end of day. What's your process?

18.You're inheriting a program that's been running for six months with no formal tracking. There are Slack channels, email threads, Confluence docs, and a Jira board that nobody's updated since March. How do you get to a true picture of status in 48 hours?

19.You're coordinating a Slack Connect rollout for a new enterprise customer and their IT admin goes dark three days before the scheduled go-live. No response to messages, no handoff. What do you do?

20.You've just been handed a project that has three executive sponsors who all think they're the primary decision-maker. No one has explicitly resolved that ambiguity. How do you handle it before it becomes a crisis?

21.You're managing a cross-functional program and halfway through you realize the success metrics everyone agreed to at kickoff no longer reflect what the business actually needs. The metrics are in the charter, stakeholders reference them in updates, but they're measuring the wrong thing. How do you handle it?

22.You're running a high-visibility internal program and a senior engineer on the team starts consistently missing deadlines without explanation, causing downstream slips. You don't have direct authority over this person. What's your move?

23.You're three weeks from launching a major enterprise feature and a customer advisory board session — which ran after the build started — surfaces that your core assumption about how customers will use the feature is probably wrong. Changing direction now would blow the timeline. What do you do?

24.You're the program manager on a Salesforce-Slack integration initiative and you discover that two separate teams — one on the Slack side, one on the Salesforce side — have been building overlapping solutions to the same problem for six weeks without knowing about each other. Both are close to done. How do you handle it?

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

26.Walk me through how you keep executives appropriately informed on a program — not so much that they're in every detail, not so little that they're surprised when something goes sideways.

27.Tell me about a time you were managing a program and a sales or customer-facing team made a commitment to a customer or prospect that you hadn't signed off on. How did you handle it?

28.Describe a time you had to represent your program's needs to finance or leadership during a budget or resource conversation — and you didn't have all the data you wished you had. How did you make the case?

29.Tell me about the most significant trust breakdown you've experienced with a key stakeholder on a program you were running. What caused it and how did you repair it?

30.You're the PM for a strategic program, and you realize one of your key stakeholders has been consistently agreeing in meetings but consistently not following through between them. Nobody else seems to have noticed yet. What do you do?