Intervu is in beta — feedback welcome at support@intervu.io

Notion Senior Software Engineer Interview Questions

30 real practice questions for the senior-level Senior Software Engineer role at Notion (Productivity SaaS), spanning behavioral, technical, system design, leadership, and problem solving. Lead technical projects and mentor junior engineers. The first 3 questions below include what Notion interviewers actually listen for, plus likely follow-ups.

Questions
30
Categories
Behavioral (6), Technical (6), System Design (6), Leadership (6), Problem Solving (6)
Difficulty mix
10 easy · 10 medium · 10 hard
Avg. answer time
~4 min

Behavioral Questions (6)

  1. 1.Tell me about a time when user feedback completely changed how you approached a feature or project. What was the original plan, what did users tell you, and how did you pivot?

    easy~3 min

    What interviewers look for

    • Demonstrates genuine user empathy by describing specific user pain points or use cases that weren't initially considered
    • Shows ability to let go of personal attachment to technical solutions when users signal different needs
    • Describes concrete actions taken to gather and validate user feedback before making changes
    • Explains how the pivot improved user outcomes with measurable results

    Likely follow-ups

    • How did you validate that the user feedback was representative rather than just a vocal minority?
    • What was the hardest part about changing direction after you'd already invested engineering time?

    Company context

    Notion's 'Put the Mission First' principle emphasizes paying close attention to the problems people want to solve with better tools and following their lead. Since Notion builds tools that empower others to build their own tools, engineers must be exceptionally responsive to how users actually want to shape and customize their software experiences.

  2. 2.Tell me about a time when you advocated for removing or simplifying something users were already using. How did you make the case that less would be better?

    easy~3 min

    What interviewers look for

    • Shows 'Always Start with Users' thinking by prioritizing user clarity over feature preservation
    • Demonstrates data-driven approach to understanding which features were creating user confusion or friction
    • Describes how they built consensus for removal despite existing user attachment
    • Explains the positive user outcomes that resulted from simplification

    Likely follow-ups

    • What was the strongest argument against removing the feature, and how did you address it?
    • How did you handle users who were actively using the feature you wanted to remove?

    Company context

    Notion's 'Always Start with Users' principle means every feature decision begins with what customers truly want. Given Notion's goal of making toolmaking ubiquitous, engineers must resist feature bloat that makes the product harder for non-technical users to customize and shape for their needs.

  3. 3.Describe a feature you built that you later had to cut or significantly simplify based on user feedback. What convinced you to remove functionality you'd already shipped?

    medium~4 min

    What interviewers look for

    • Shows intellectual humility by describing a feature they were proud of that didn't work for users
    • Demonstrates 'Always Start with Users' thinking by prioritizing user confusion/friction over feature completeness
    • Explains the data or feedback that convinced them the feature was causing more harm than good
    • Describes how they handled the emotional challenge of cutting work they'd invested in

    Likely follow-ups

    • How did you distinguish between users who needed time to learn the feature versus those who fundamentally didn't need it?
    • What did you learn about feature design that you apply to new projects now?

    Company context

    Notion's 'Always Start with Users' principle requires that every feature decision begins with whether it's actually useful to people. Given Notion's mission to make toolmaking ubiquitous, engineers must be willing to cut complexity that gets in the way of user creativity and customization, even after significant engineering investment.

  4. 4.Walk me through a time when you had to deliver a project much faster than originally planned. How did you compress the timeline without compromising quality?

    medium~3 min
  5. 5.Tell me about the most significant technical project or initiative you said no to in the last year. What made you push back, and how did that decision play out?

    hard~5 min
  6. 6.Describe a situation where you initially dismissed user feedback as wrong or misguided, but later realized they were pointing to a real problem. What changed your mind?

    hard~5 min

Technical Questions (6)

  1. 7.Write a function that validates whether a block tree structure is valid according to Notion's rules. Consider parent-child relationships and circular references.

    easy~3 min
  2. 8.Implement a TypeScript function that merges two sorted arrays of Notion blocks, where each block has an ID and a timestamp. The result should be sorted by timestamp.

    easy~2 min
  3. 9.Our block storage engine is seeing high read latency during peak hours. The database team says queries are fast, but users report slow page loads. How would you debug this?

    medium~4 min
  4. 10.You're tasked with migrating a critical service from Python to TypeScript while maintaining zero downtime. The service handles block operations and serves 50K requests per second. What's your migration strategy?

    medium~4 min
  5. 11.You're implementing a new block type for Notion's editor that needs to support real-time collaboration. Walk me through how you'd design the data structure and handle concurrent edits from multiple users.

    hard~5 min
  6. 12.You need to add full-text search across a workspace that contains 10 million blocks with complex permission inheritance. How would you approach this?

    hard~5 min

System Design Questions (6)

  1. 13.Design a rollback system for Notion pages. Users should be able to revert any page to a previous state, but some pages have thousands of revisions. How do you make rollbacks fast while keeping storage costs reasonable?

    easy~3 min
  2. 14.You're building calendar sync for Notion Calendar that needs to stay in sync with Google Calendar, Outlook, and other providers. Events can be modified from either side, and conflicts need to resolve gracefully. How do you design this bidirectional sync?

    easy~3 min
  3. 15.You're building Notion's offline sync system. Users need to edit documents without internet, then sync changes when they reconnect. Multiple users might edit the same block offline and come back online simultaneously. How do you handle conflicts?

    medium~4 min
  4. 16.Design Notion AI's query system that needs to search across a user's entire workspace in under 200ms. The workspace contains 1M blocks of mixed content — text, databases, embeds. How do you make semantic search feel instant?

    medium~4 min
  5. 17.Design the permission system for Notion's workspace sharing. A single workspace can have 100K members with complex inheritance rules — pages can inherit from parent pages or have custom permissions. How would you ensure permission checks stay fast at this scale?

    hard~5 min
  6. 18.Walk me through how you'd build the notification system for Notion databases. When someone updates a row, you need to notify potentially thousands of subscribers across different channels — email, in-app, mobile push. How do you prevent a single database update from overwhelming your infrastructure?

    hard~5 min

Leadership Questions (6)

  1. 19.Tell me about a time you had to convince an engineer who was more senior than you to change their approach on a technical decision. What was your strategy?

    easy~3 min
  2. 20.Tell me about a time when you built something primarily to help other engineers be more effective, even though it wasn't directly tied to user-facing features. What was your approach?

    easy~3 min
  3. 21.Describe a time when you had to mentor someone who wasn't on your direct team but whose success was critical to your project. How did you approach helping them level up?

    medium~4 min
  4. 22.Walk me through a time when you had to coordinate a complex project across multiple teams where everyone was already overcommitted. How did you get alignment and execution?

    medium~5 min
  5. 23.Describe a situation where you disagreed with your engineering manager's priorities or approach, but you still needed to maintain a good working relationship. How did you handle it?

    hard~5 min
  6. 24.Tell me about a time when you had to make a significant technical decision with incomplete information because waiting for perfect data would have delayed an important project. How did you approach it?

    hard~5 min

Problem Solving Questions (6)

  1. 25.Notion's user base grew 10x in two years, but average session duration dropped 15%. Nothing changed in the product. How would you investigate what's happening?

    easy~3 min
  2. 26.Estimate how many API calls Notion processes per day. Walk me through your reasoning and key assumptions.

    easy~4 min
  3. 27.Notion is considering adding video calling to workspaces. How would you estimate the infrastructure cost and decide if it's worth building?

    medium~5 min
  4. 28.A Fortune 500 company wants to migrate 50,000 employees from Confluence to Notion. How would you estimate the timeline and identify the biggest risks?

    medium~5 min
  5. 29.Notion AI costs are growing faster than revenue. Each AI query costs us $0.02, users average 50 queries per month, but only 60% are on paid plans. How would you make this sustainable?

    hard~5 min
  6. 30.Notion is seeing 20% of new workspaces go inactive within 30 days. Each workspace setup takes engineering effort to provision. How would you identify what's causing abandonment and prioritize fixes?

    hard~5 min

More Notion interview questions