Notion product manager interview: process, values and prep
Notion evaluates every candidate against a strict craft and values bar, sends a role-specific interview guide so you know what to expect, and involves CEO and founder Ivan Zhao in the hiring process for almost every role (Notion's How Notion hires blog post). Product managers at Notion work in person three days a week on Monday, Tuesday, and Thursday (Notion Careers). Below is what Notion publishes on its hiring process, operating values, block architecture, and PRD structure, along with practice questions and a preparation checklist written by our team. Soreno, an AI voice interview practice app for product managers, includes a free STAR method template with no sign-up, and voice PM mock interviews covering product sense, metrics, and leadership stories.
Updated
- Customer in every room. Notion describes itself as a tool company that exists to help customers do their life's work. Serving customers is the primary quest, and everything else is secondary.
- Own the outcome. Because AI has commoditized many capabilities, Notion emphasizes agency. It looks for people who spot opportunities, take initiative, and do not wait for someone else to define the path.
- Why not today. In a competitive AI environment, Notion relies on collective urgency and speed. Instead of pushing work to next week, teams ask why it cannot be done today.
- Direct and kind. Notion pairs kindness with directness to accelerate trust, win more, and drive better outcomes for customers.
Key facts, benchmarks, and worked examples
Below is a breakdown of notion product manager interview, sourced from official firm, school, and government documentation.
What Notion publishes about its hiring process5 points
In its February 2, 2023 blog post How Notion hires, Chief People Officer Maryanne Brown Caughey laid out the company's recruiting standards across its more than 500 employees. While that post is more than three years old, it remains Notion's primary statement on how interviews work. Notion states that it does not hire just to hit a headcount number. If a candidate does not meet both the craft and values bar, the team passes. Every candidate invited to interview receives a role-specific interview guide from Notion ahead of time so there are no surprises about the stages or topics. If you want to warm up before your first call, you can Practice a case free, no sign-up with our AI interviewer. Here are the core elements of the hiring process Notion outlines:
1. Role-specific interview g
Role-specific interview guides
Notion sends an interview guide created for your specific role to give you a preview of the process and expectations.
2. Two-way conversations
Two-way conversations
Notion tells interviewers to treat sessions as honest, two-way conversations rather than interrogations, so both sides can judge whether there is a long-term match.
3. Resolving open questions
Resolving open questions before the offer
If the hiring team has open questions about your craft or values, they take additional steps to resolve them before moving to the offer stage.
4. Rigorous reference checks
Rigorous reference checks
Notion treats reference checks as a strong predictor of success at the company, not a box-checking exercise.
5. CEO review
CEO review
CEO and founder Ivan Zhao is involved in the hiring process for almost every role. He evaluates three questions: does the candidate excel in their craft, do they share company values, and has Notion conducted a fair, rigorous interview process.
Where Notion hires product managers1 detail
Notion is an in-person company. Employees come into the office three days a week on Monday, Tuesday, and Thursday. Notion states that working together in person allows quick questions to turn into whiteboard sessions and helps teams stay close to customers.
Part 1
On its Careers page, Notion lists (1)
On its Careers page, Notion lists product roles both under the Product Management department and embedded inside functional teams. For example, open listings include Product Manager, Connections in San Francisco and Business Development Manager, Product and Platform in New York and San Francisco under Product Management, alongside AI Product Manager, Growth Marketing in New York and San Francisco under Marketing, and Product Operations Manager in San Francisco and New York under User Research and Product Operations.
Product and technical context every Notion PM candidate needs4 points
To meet Notion's craft bar in a product sense interview, you need to understand how Notion frames its product and how its architecture works under the hood. On its product page, Notion organizes the workspace around three pillars: Capture (bringing everything into one system of record), Find (getting answers instantly with citations), and Automate (keeping work moving 24/7 with agents). Notion reports 100M users in over 50 countries, over 1.4M community members, over 50% of YC companies, and 62% of the Fortune 100 using Notion, along with being named G2's #1 knowledge base for 3 consecutive years. Recent posts on the Notion blog show where the product and engineering teams are investing their time:
1. Notion AI and
Notion AI and Custom Agents
Co-founder Akshay Kothari wrote about rebuilding Notion AI with smarter model routing, long-running agents, bring-your-own-AI options, and a new credit system. Notion also highlights internal and customer workflows like a Custom Agent that monitors Slack to triage product feedback and route bugs to engineering teams using a self-updating routing rules page.
2. App connections and
App connections and MCP
Notion connected Notion AI to 160 new apps in three weeks using a Notion agent, and supports Notion MCP so teams can connect workspace context to Claude, ChatGPT, and other external agents.
3. Model evaluation at
Model evaluation at scale
Engineering teams use an upgraded model router called Auto, relying on pairwise comparisons and calibrated judging to measure model quality.
4. Concurrent editing with
Concurrent editing with CRDTs
Notion built a CRDT-based rich-text system to merge concurrent edits across blocks without losing user work.
How Notion's block data model works5 points
In a May 18, 2021 engineering blog post, Notion explained the data model behind its flexibility. Even though that post is several years old, the block architecture remains the foundation of the editor. Everything in Notion is a block, including text, images, lists, database rows, and pages themselves. Every block has five core attributes that a product manager should keep in mind when discussing feature design, permissions, or performance:
1. ID
ID
A randomly generated UUID (UUID v4) that uniquely identifies the block. Page block IDs appear at the end of the URL in the browser.
2. Properties
Properties
A data structure storing custom attributes, most commonly the title property. Decoupling property storage from block type is why Notion's Turn into function can change a checked To-do item into a Heading and back into a To-do item without losing the checked state.
3. Type
Type
Defines how a block is displayed in the UI and how its properties and content are interpreted.
4. Content
Content
An ordered array of block IDs (downward pointers) representing nested render children inside the block, such as items inside a toggle or sub-pages inside a page. Indentation in Notion is structural rather than presentational: indenting moves a block into the content array of the preceding sibling block.
5. Parent
Parent
The block ID of the block's parent (an upward pointer). Notion uses the parent attribute rather than the content array to walk up the tree to the workspace root for permission checks, because blocks could historically be referenced in multiple content arrays and searching downward arrays on the client is inefficient.
How Notion structures a Product Requirements Document (PRD)7 points
Written specs are central to product management. In a July 28, 2023 guide on writing a PRD, Notion breaks a thorough product requirements document into seven steps. If your interview includes a written exercise, case study, or live product design prompt, structuring your thoughts around Notion's own seven-step framework keeps your answer clear and complete:
1. Define the product
1. Define the product
Summarize the plan, the project team and stakeholders, a tentative release date, the buyer persona, and the exact pain points the product solves for the end user.
2. Determine goals
2. Determine goals
Write specific, measurable, achievable, relevant, and time-bound (SMART) objectives that explain how the work benefits both the end user and the company.
3. Identify assumptions and
3. Identify assumptions and constraints
List known roadblocks around end-user needs (assumptions) and external limitations that could affect workflow (constraints), along with dependencies required before launch.
4. Limit the scope
4. Limit the scope of work
Explicitly state what is and is not in scope to prevent scope creep.
5. List features
5. List features
Detail the primary features and how end users will interact with them so every stakeholder understands the requirements.
6. Define release criteria
6. Define release criteria
Set the functionality, usability, and reliability standards that determine whether the product is customer-ready.
7. Set metrics for
7. Set metrics for success
Define the metrics and tracking method, such as error rates, adoption targets, or delivery milestones on a Kanban board, to verify success after launch.
Practice questions for a Notion PM interview6 points
Check the role-specific interview guide Notion sends you before your first round to confirm the exact topics and formats for your team. To help you prepare, our team wrote the practice questions and evaluation notes below based on Notion's published operating values, product pillars, block architecture, and AI agent workflows. You can also review our broader list of product manager interview questions or compare how large tech companies test PMs in our Google product manager interview guide. When you answer these prompts out loud, avoid reciting a memorized checklist. Instead, connect user workflows to Notion's underlying block primitives, permission model, and operating values.
1. Product sense (Blocks
Product sense (Blocks and primitives)
Users want a way to run recurring weekly team check-ins inside Notion without building a complex database from scratch. How would you solve this using Notion's existing block primitives rather than introducing a single-purpose check-in tool? What to cover: Explain how a template button or repeating database template creates standard page blocks, how properties track status without locking the user into a rigid form, and how preserving properties across block types lets a team turn check-in bullets into action items.
2. Product sense (AI
Product sense (AI Agents)
Notion's Custom Agents can monitor Slack channels and file tickets using a self-updating routing rules page. What failure modes would you expect in the first 30 days for a mid-market team, and what product guardrails would you build? What to cover: Walk through what happens when the routing rules page starts blank, how duplicate Slack reports can create redundant database rows, and how a human-in-the-loop approval step in Slack can update the routing rules page cleanly.
3. Execution and metrics
Execution and metrics (Capture, Find, Automate)
Imagine teams are capturing thousands of pages in Notion, but weekly active usage of Quick Find and AI search citations is flat. How would you diagnose the bottleneck and what metric would you set as your primary goal? What to cover: Check whether newly created blocks are being indexed fast enough after saveTransactions commits them, whether users trust the citations returned from nested sub-pages, and how often a search query ends in a user clicking a cited block.
4. Architecture and trade-of
Architecture and trade-offs
A customer wants to share a single toggle block inside a confidential strategy page with an external contractor. Given how Notion's parent pointers handle permissions, what are the product and security trade-offs of supporting block-level external sharing? What to cover: Point out that every block inherits permissions by walking upward through parent pointers to the workspace root. Allowing a child toggle block to have broader permissions than its parent page creates a risk of leaking sibling blocks or parent titles if a user indents or moves blocks in the render tree.
5. Values (Why not
Values (Why not today and Own the outcome)
Tell me about a time a project was scheduled to take a full quarter, and you found a way to test or ship the core customer value in a matter of days. What to cover: Name the specific scope you cut, how you stepped in to unblock a dependency yourself, and what you learned from putting the early version in front of real customers.
6. Values (Direct and
Values (Direct and kind)
Tell me about a time you had to tell an engineer or designer that their proposed solution missed the customer problem. How did you deliver the feedback and what happened next? What to cover: Show how you grounded the conversation in customer evidence rather than personal taste, stated the disagreement plainly without softening it into confusion, and worked together on the revised spec.
Worked example: outlining a one-page Notion PRD in an interview7 points
If an interviewer asks you to scope a new feature live or in a written exercise, using Notion's seven-step PRD structure helps you stay organized under time pressure. Below is an invented example written by our team showing how a candidate can outline a spec in ten minutes for a Custom Agent that keeps internal onboarding docs current.
1. Step 1. Define
Step 1. Define the product
We are building an Onboarding Doc Maintainer template powered by Notion Custom Agents and connected databases. The target users are engineering managers and people operations leads at growing startups who struggle when new hires hit outdated setup instructions. The project team includes one PM, one designer, and two engineers on the Custom Agents workflow team.
2. Step 2. Determine
Step 2. Determine goals
Our SMART goal is to help new workspaces resolve 80% of flagged documentation errors within 48 hours of a new hire reporting them during their first month of onboarding, without requiring manual page audits from managers.
3. Step 3. Identify
Step 3. Identify assumptions and constraints
We assume new hires will report broken steps in a designated onboarding Slack channel or page comment rather than fixing the page themselves. A key constraint is permission inheritance: the Custom Agent can only draft updates on pages where the workspace admin has granted the agent read and write access through the parent page tree. A core dependency is the Notion MCP connection to Slack and the workspace's task database.
4. Step 4. Limit
Step 4. Limit the scope of work
In scope for version one is monitoring one Slack channel for questions, matching the question to cited blocks in the onboarding wiki, and drafting a suggested block edit for the page owner to approve. Out of scope for version one is automatically overwriting published blocks without human approval or editing external third-party tools.
5. Step 5. List
Step 5. List features
First, a listener trigger that captures Slack threads where a new hire flags an outdated step. Second, a citation lookup that finds the exact paragraph or to-do block ID in the onboarding page. Third, a review queue database where the page owner can click one button to replace the old block title property with the agent's drafted text and update the routing rules memory page.
6. Step 6. Define
Step 6. Define release criteria
Before launch, the agent must accurately cite the target block on at least 90% of test queries, respect all upward parent permission checks so confidential HR pages are never surfaced, and complete block updates through saveTransactions without overwriting concurrent live edits.
7. Step 7. Set
Step 7. Set metrics for success
We will track the percentage of agent-drafted block edits approved by page owners, the time from Slack question to updated block, and the reduction in repeated onboarding questions on the same topic over a 30-day window.
Practice your Notion PM answers out loud1 detail
Overview 1
Reading about block primitives and operating (1)
Reading about block primitives and operating values is a strong start, but interviews move fast once follow-up questions begin. Start practicing with Soreno today to run live product sense, execution, and behavioral mocks with an AI interviewer that probes your reasoning and scores your answers.
From Notion: How Notion hires (February 2, 2023), Notion: Careers at Notion, Notion: Product overview, Notion: The data model behind Notion's flexibility (May 18, 2021), Notion: How to write a PRD in 7 simple steps (July 28, 2023), Notion: Tools & Craft Blog and Notion: Triage product feedback with Custom Agents.
Notion's operating values and in-person work model
Notion evaluates values alongside craft in every interview. On the Notion Careers page, the company lists four current operating values that reflect how teams work in the AI era. In its earlier 2023 hiring post, Notion also described its values as being drivers of its mission, pace setters, truth seekers, and kind and direct. When you answer behavioral and product questions, your stories should show how you work within these four current principles:
Customer in every room
Notion describes itself as a tool company that exists to help customers do their life's work. Serving customers is the primary quest, and everything else is secondary.
Own the outcome
Because AI has commoditized many capabilities, Notion emphasizes agency. It looks for people who spot opportunities, take initiative, and do not wait for someone else to define the path.
Why not today
In a competitive AI environment, Notion relies on collective urgency and speed. Instead of pushing work to next week, teams ask why it cannot be done today.
Direct and kind
Notion pairs kindness with directness to accelerate trust, win more, and drive better outcomes for customers.
Official sources: Notion: How Notion hires (February 2, 2023), Notion: Careers at Notion, Notion: Product overview, Notion: The data model behind Notion's flexibility (May 18, 2021), Notion: How to write a PRD in 7 simple steps (July 28, 2023) and Notion: Tools & Craft Blog.
1 practice question and sample answer
The practice prompts and sample answers below are Soreno's own, written for invented candidates.
Practice question and sample answer1 question
The answer ties directly to how Notion's Custom Agent memory page actually works, avoids inventing rigid non-Notion UI, and balances the Why not today value (fast setup) with Customer in every room (protecting engineering trust with a measurable metric).
Notion's Custom Agents can monitor a Slack channel for product feedback and route bugs to the right engineering team using a routing rules page as memory. If you were the PM for this workflow, how would you reduce misrouted tickets during a team's first two weeks without slowing down setup?
Show the sample answer
Sample answer. Example answer written by our team. The applicant is invented. I would start with the core tension: a new team wants the agent working today with zero setup friction, so the routing rules page starts blank. In the first two weeks, the agent has very little context, which causes misrouted tickets and erodes trust with engineers. Rather than forcing an admin to write fifty rules upfront, I would scope a lightweight feedback loop using Notion's existing block primitives. First, when the agent cross-posts a bug to an engineering Slack channel and creates a database row, I would include a confidence property on the ticket block. If the model router scores confidence below a set threshold, the Slack message tags the triage owner with a one-click dropdown to reassign the team. Second, whenever a human changes the team property on a ticket in Notion, the agent automatically appends a suggested rule block to the routing rules page and asks the owner to approve it. To measure success, I would track the percentage of auto-routed tickets that get manually reassigned within 48 hours, aiming to cut reassignments in half between week one and week two while keeping initial setup under five minutes.
The answer ties directly to how Notion's Custom Agent memory page actually works, avoids inventing rigid non-Notion UI, and balances the Why not today value (fast setup) with Customer in every room (protecting engineering trust with a measurable metric).
7-step prep checklist before your Notion interview
7-step prep checklist before your Notion interview
Our team put together this preparation checklist so you can walk into your conversations ready to discuss craft and values with specifics:
Step 1
Read the interview guide your recruiter (1)
Read the interview guide your recruiter sends you, and list one concrete story from your past work for each stage mentioned.
2. Audit your own
Audit your own Notion workspace
be ready to show or explain a workflow you built using blocks, databases, or Custom Agents, and name one friction point you noticed as a user.
Step 3
Map four behavioral stories to Customer (3)
Map four behavioral stories to Customer in every room, Own the outcome, Why not today, and Direct and kind, making sure each story highlights your personal agency.
Step 4
Review the five block attributes (ID (4)
Review the five block attributes (ID, Properties, Type, Content, Parent) so you can reason aloud about how UI changes affect the render tree and permissions.
5. Practice outlining a
Practice outlining a one-page spec in 10 minutes using Notion's seven PRD steps
product definition, SMART goals, assumptions and constraints, scope limits, features, release criteria, and success metrics.
Step 6
Prepare thoughtful questions for a two-way (6)
Prepare thoughtful questions for a two-way conversation about how your specific team balances general-purpose building blocks with out-of-the-box templates and AI automation.
Step 7
Line up strong professional references early (7)
Line up strong professional references early, since Notion relies on reference checks as a key predictor of success before making an offer.
Practice product sense and PRD trade-offs out loud
Soreno's AI interviewer runs product sense, block-architecture scoping, and behavioral questions by voice, challenges your trade-offs, and scores each part of your answer.
Questions people ask
Does Notion send interview preparation materials to candidates?
Yes. In its How Notion hires blog post, Notion states that it creates role-specific interview guides for every role so candidates get a preview of the process and face no surprises.
What are Notion's core company values?
On its Careers page, Notion lists four operating values: Customer in every room, Own the outcome, Why not today, and Direct and kind. In its 2023 hiring blog post, Notion also described its values as being drivers of its mission, pace setters, truth seekers, and kind and direct.
Is Notion remote or in-person for Product Managers?
Notion is an in-person company. According to the Notion Careers page, employees work from the office three days a week on Monday, Tuesday, and Thursday.
Is CEO Ivan Zhao really involved in Notion hiring?
Yes. Notion states that CEO and founder Ivan Zhao is involved in the hiring process for almost every role, focusing on whether the candidate excels in their craft, shares company values, and went through a fair, rigorous interview process.
Does Notion check references before making an offer?
Yes. Notion notes that reference checks are an important part of its hiring rigor and treats them as a strong predictor of success at Notion rather than a formality.