Notion, based in San Francisco, makes a connected workspace for documents, wikis, projects and databases, with AI features built in. Candidates describe product-flavored technical rounds, including take-homes, object-oriented coding and debugging, more often than classic algorithm drills. This page covers what Notion builds and who it hires, the process candidates commonly report, the technical depth the teams care about, representative problem types, what interviewers score, and a three-week prep plan.
What Notion builds and who it hires
Notion's engineers build the editor, where every piece of content is a block in a flexible tree; real-time collaboration and sync across web, desktop and mobile; Notion AI; and the public API. Notion's engineering blog describes sharding Postgres into 480 logical shards across 32 physical databases, chosen because 480 divides evenly in many ways, and later spreading the same 480 shards across 96 database instances.
- Product engineers: TypeScript and React features end to end.
- Infrastructure and data engineers: Postgres, sync and the data lake.
- Mobile engineers: the iOS and Android apps.
- AI engineers: Notion AI features and the systems behind them.
What the process tends to look like
| Stage | What happens | How to prepare |
|---|---|---|
| Recruiter call | Role, team, level and timeline | Know the product and the team's area |
| Technical screen | A practical coding interview or a take-home, often in TypeScript or React for product roles | Practical coding in your interview language, explained aloud |
| Final loop | Object-oriented coding, a debugging round, system design for experienced hires, and hiring-manager conversations about craft | One design in the company's domain and two strong behavioral stories |
Processes differ by team, level and office and change over time, so treat this as the common shape candidates report and confirm the specifics with your recruiter.
Blocks, collaboration and product craft
The block model. Notion has written that everything on a page is a block with a type, properties and children. A natural exercise is modeling a tree of blocks with moves, inherited permissions and rendering.
Real-time collaboration. Be ready to discuss syncing edits from many clients, ordering operations, offline edits and conflict resolution, focusing on trade-offs rather than formal proofs.
Product craft. Interviewers care about the experience: loading states, undo, and performance on very large pages. Mention how you would check a feature with real users. Our React interview questions help with front-end rounds.
Representative problem types
These are the kinds of problems candidates describe, not a leaked question list. Practice the category, not the exact question.
- Model a tree of blocks and move a subtree safely.
- Implement undo and redo for an editor.
- Build a small dashboard component in React from a spec.
- Debug a failing feature in an unfamiliar codebase.
- Design sync for a document edited offline on two devices.
- Route each request to the right database shard by workspace.
- Medium algorithm problems on trees and strings.
What interviewers score
- Working code: a solution that runs, handles edge cases and is readable by the next engineer.
- Practical judgment: the trade-offs you name and the simplest design that meets the requirement.
- Product sense: understanding who the user is and what failure looks like for them.
- Ownership: examples where you shipped, measured and fixed things yourself.
The behavioral side
Technical rounds decide most outcomes, but every Notion loop also asks about how you work. Prepare a short story for each of these, with a result and what you learned:
- Something you shipped end to end. Cover the user problem, your decisions, what you measured and what you would change.
- A disagreement with a teammate. Show how you made the decision on evidence and kept the relationship.
- Why this company? Connect its product and engineering problems to the work you want to do next.
Structures and sample answers for the common questions are in our software engineer behavioral answers guide.
A three-week prep plan
- Week 1: practical coding: build small features against an API, parse and transform data, and write tests, in the language you will interview in.
- Week 2: system design for the company's domain, plus two behavioral stories about shipping and fixing something under pressure.
- Week 3: timed mixed problems, a mock interview every other day, and research into the product and its engineering blog.
For practice lists, use LeetCode company-tagged questions and the NeetCode 150 roadmap; for design rounds, read system design building blocks; and compare the practical style of Datadog.
Where CoPilot Interview fits
Most of a Notion loop is spoken: you explain an approach, defend a trade-off and talk through your past work. CoPilot Interview is an AI interview assistant whose free AI mock interview builds technical and behavioral questions from your résumé and the job description, reads them aloud and scores each spoken answer out of ten, so you can rehearse the explanation as well as the code. The free plan gives 15 minutes a day of live help in sessions of up to 15 minutes, with AI mock interviews included. Online assessments and many coding rounds forbid outside help, so practice beforehand and follow your employer's rules on the day.
Disclosure: CoPilot Interview is our product, so weigh what we say about it accordingly.
Frequently asked questions
What programming language should I use in a Notion interview?
Candidates and job posts commonly describe TypeScript across Notion's stack, and product rounds often use TypeScript or React; general rounds may allow your strongest language.
Does Notion send an online assessment?
Candidates describe a live technical screen or a take-home rather than a puzzle-style online assessment; it depends on the role and the year.
Is the Notion interview LeetCode-heavy?
Less than at many large companies, as candidates describe it. Expect some medium problems, but spend more of your time on practical builds, object-oriented design and debugging in TypeScript or React.
How should I prepare for Notion coding questions?
Practice practical problems under time limits, build small features against an API in your interview language, and prepare one system design in Notion's domain. Explain every solution out loud, because follow-up questions about trade-offs matter as much as the first answer.
Can I use AI tools in a Notion interview?
Only if the instructions you receive say so. Online assessments and live coding rounds generally forbid outside help, and some companies now state their AI policy in the invitation. Use AI to practice beforehand, and follow your employer's rules.
Practice this interview before the real one
The AI mock interview builds questions from your resume and the job description, reads them aloud and scores each spoken answer out of 10. Included on the free plan.
Start a mock interview