Notion Program / Project Manager Interview Questions

1.Tell me about a project where feedback from users completely changed the direction you were heading. What did you actually do differently after hearing it?

2.Give me an example of a time you simplified something for users that your internal team thought was already good enough. How did you know simplification was the right move?

3.Walk me through a time you cut something from a project scope after talking to users. What made you confident it was the right call?

4.Describe a time you had to compress a project timeline significantly. What specifically did you change, and what did you protect?

5.Tell me about the most significant thing you said no to on a project — something people expected you to include. What was your reasoning and how did it land?

6.Tell me about a time when something a user told you forced you to go back and question a fundamental assumption your whole project was built on. What did you do next?

7.Notion has three main customer tiers — free, Plus, and Business/Enterprise. If you had to estimate what percentage of Notion's total revenue comes from Enterprise customers, how would you think through it?

8.Notion's weekly active users dropped 8% over a three-week period and no major changes shipped during that window. How would you investigate what happened?

9.Notion is considering investing in a dedicated onboarding program for new Enterprise workspace admins. How would you size whether that's worth doing, and what would you measure to know if it worked?

10.Notion's AI feature has a monthly active user rate that's lower than expected given the number of workspaces that have it enabled. How would you figure out why, and what programs would you consider running to close the gap?

11.Notion is planning to launch a major new feature for Enterprise teams. Product, Engineering, Marketing, and Sales each have a different assumption about who the primary user persona is. You're the program manager. How do you get alignment, and what's the cost of not getting it before launch?

12.You're running a program to migrate Notion's largest Enterprise customers to a new workspace permissions model. Midway through, you discover that 20% of those customers have custom integrations that will break on migration — and the engineering team says fixing the integration layer will take eight more weeks. The business team has committed referenceable customer logos for a marketing campaign launching in six weeks. What do you do?

13.Walk me through how you typically structure a project kickoff. What does your first week on a new initiative look like?

14.How do you decide which projects are on track versus at risk? What signals do you actually watch, and how often?

15.You're managing a cross-functional launch involving Product, Engineering, Marketing, and Sales — and two of those teams have conflicting priorities for the same two-week window. How do you resolve it without a mandate from the top?

16.How do you write a project brief that actually gets read and acted on? What's in it, and what do you leave out?

17.You're three weeks from a major launch and engineering tells you a core feature will be two weeks late. You can't move the date, and you can't cut the feature entirely. Walk me through exactly how you respond.

18.You inherit a project that's been running for three months with no clear owner and inconsistent documentation. How do you get it back under control without losing the momentum the team has already built?

19.A stakeholder asks you to add a status update meeting to a project that already has two syncs a week. How do you handle it?

20.You're the PM on a project and you realize halfway through that you gave leadership an overly optimistic timeline in the kickoff. The deadline is in four weeks and you're six weeks out from done. What do you do right now?

21.Your team is two weeks from launching a new Notion AI feature when a competitor ships something nearly identical. Leadership wants to know if you should accelerate, differentiate, or hold the current plan. How do you think through this and what do you recommend?

22.You're managing a high-visibility internal tooling project and the engineering lead tells you they want to redesign a core component before shipping — work that wasn't in scope and will add three weeks. The business sponsor has already announced the delivery date externally. What do you do?

23.You're running a cross-functional initiative involving three teams and you discover that two of them have been solving the same problem in parallel for six weeks — neither knew the other was working on it. Both solutions are partially built. What do you do and how do you prevent it from happening again?

24.You're leading the program for a major Notion enterprise feature rollout. Two days before general availability, your security team flags a potential data access issue that affects shared workspaces. It's not confirmed — it might be a false alarm — but if real, it could expose customer data. The launch is tied to a committed customer contract. What do you do in the next two hours?

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 bring them along?

26.Describe a time you had to be the person who told a key partner — in Sales, Finance, or another function — that the thing they were counting on wasn't going to happen as promised. How did you handle it?

27.Tell me about a time two senior stakeholders had genuinely incompatible views on a program decision — not just a priority disagreement, but a real conflict. How did you navigate it without it becoming political?

28.You're running a program where a key external customer is asking for weekly status calls and direct access to your engineering lead. Your engineering lead doesn't want that exposure. How do you handle it?

29.Tell me about the most senior person you've had to push back on — not in a 'tell me no' way, but where you believed they had a materially wrong assumption about your program. How did you make the case?

30.You're coordinating a cross-functional program and you realize that two of your partner teams have been giving their leadership two different stories about what the program will deliver — and neither one matches what you've been telling yours. How do you respond?