Notion frontend phone screens ask you to build a piece of an editor: an undo and redo history, or a React view of nested JSON. Here is what members report.
This guide is built from 2 Notion interview reports that FrontendLead members posted in April and May 2026, plus what Notion has published about how it hires. Both reports cover the phone screen, so that stage is described from first-hand accounts and the rest comes from Notion’s own writing. Each section says which is which. The exact prompts are in the members-only section below.
The biggest pattern: both phone screens were practical builds with a design conversation attached, not algorithm puzzles. One candidate implemented undo and redo and then discussed the low-level design. The other rendered arbitrary JSON in React. In both, the structure of your code was part of the grade.
By Shivam Bhalla · Updated
01Notion frontend interview at a glance
- Phone screen
- One practical coding problem with a design discussion (2 member reports, 2026)
- Topics reported
- Undo and redo with low-level design; visualizing JSON in React
- Levels reported
- SWE2 with 3 years of experience; Senior with 6.5 years
- Hiring bar
- Craft and values; Notion says it passes on candidates who miss either (Notion, 2023)
- Interview style
- Conversational and two-way, with a published interview guide per role (Notion, 2023)
- References
- Taken seriously; Notion calls them a strong predictor of success (Notion, 2023)
- Evidence
- 2 member reports, both phone screens
02Notion frontend interview process
Members have reported the phone screen. For the other stages, this section relies on Notion’s February 2023 post on how it hires, written by its Chief People Officer. Ask your recruiter for the interview guide for your role, since Notion says it has one for every role.
- 1
Recruiter conversation
Source: Notion’s hiring postNotion says its best interviews are two-way conversations, not interrogations, and that it wants each side to work out whether there is a long-term match. Come with real questions about the team and the product area. Ask for the role’s interview guide on this call.
- 2
Phone screen
One practical problem, per 2 member reportsBoth members got a single build-style problem. A SWE2 candidate implemented undo and redo and discussed the low-level design. A senior candidate was asked to visualize JSON in React, with a public JSON editor given as a reference for the expected behavior.
Expect to write working code and then defend how it is organized: where state lives, how the pieces would grow, and what you would change with more time.
- 3
Onsite interviews
Not yet reported by membersNo member has reported a full Notion onsite loop, so the number and type of rounds are not confirmed here. Notion describes its process as rigorous: it wants comprehensive signal before an offer, and it resolves open questions before moving forward.
- 4
References and decision
Source: Notion’s hiring postNotion says references are an important part of its process and a strong predictor of success, not a box to check. Line up people who worked closely with you and can speak to specific projects. In 2023, Notion also said its CEO was involved in hiring for almost every role.
03What Notion looks for
Notion says it hires on two things: craft and values.
Craft. For engineers, Notion describes someone who proactively gives input on technical, product, and business decisions, has strong knowledge of best practices in their domain, and improves existing processes so others work together better. In an interview, that means explaining why you chose a design, not only that it works.
Values. Notion lists four: drivers of the mission, pace setters, truth seekers, and kind and direct. Prepare one story for each. A good “kind and direct” story is a time you gave or received hard feedback and what changed afterward.
04Coding questions Notion candidates were asked
Premium
Both prompts come from member reports of the phone screen.
Implement undo and redo, then discuss the design
SWE2, 3 years of experience, phone screen, May 2026Implement undo and redo, then talk through the low-level design. The member’s advice was to practice the implementation and be ready to explain your design choices.
Decide your model before you type. Either store snapshots of state, or store commands that know how to apply and revert themselves. Then cover the cases an interviewer will raise: a new edit after an undo clears the redo stack, several small changes may need to count as one step, and the history needs a size limit.
Practice: Undo Redo History, which the member named as a good match, then Command Undo Stack and Undoable User Table.
Visualize JSON in React
Senior, 6.5 years of experience, phone screen, April 2026Build a React view that renders arbitrary JSON, with a public JSON editor given as the reference. The member’s advice was to practice rendering dynamic JSON in React, including recursive rendering for nested structures.
The core is one recursive component that switches on the value’s type: object, array, string, number, boolean, or null. Give each node a stable key, keep expand and collapse state per node, and think about what happens with a very large or deeply nested payload.
Practice: Nested Comments I for recursive rendering in React, Pretty JSON Printer for walking every JSON type, and Read Nested Path for path handling.
05Notion frontend system design
No member has reported a Notion system design round yet. Both reported phone screens included a design discussion about the code the candidate had just written, so be ready to reason about structure even in a coding round.
If your loop includes a design round, practice on problems close to the product:
For each, be able to explain how a page of blocks is stored in the client, how an edit reaches other people viewing the page, and how the editor stays responsive on a long document.
06How to prepare for the Notion frontend interview
Practice building small editor features end to end and explaining the design afterward. Record yourself explaining one solution: both members had to discuss their design, not only write the code.
| Days | Focus | Practice |
|---|---|---|
| 1 to 3 | Undo and redo | Command Undo Stack, Undo Redo History, Undoable User Table |
| 4 to 6 | Recursive rendering and JSON | Nested Comments I, Pretty JSON Printer, Read Nested Path |
| 7 to 8 | Build a JSON viewer from scratch | Expand and collapse, stable keys, and a large payload, timed at 45 minutes |
| 9 to 11 | System design | Design Notion, Rich Text Editor |
| 12 to 14 | Craft and values stories, references | One story per Notion value, and two people ready to be references |
If you have interviewed at Notion, add your report. Each new report makes this guide more specific.
07Notion frontend interview FAQ
What does Notion ask in frontend interviews?
The two phone screens members reported were practical builds: implementing undo and redo with a low-level design discussion, and visualizing JSON in React. Neither was a pure algorithm puzzle.
Does Notion ask LeetCode-style questions?
Neither member report describes one. Both problems were small features an editor needs. That is only two reports, so keep general data structures fresh as well.
What is the Notion interview process?
Members have reported a phone screen with one practical problem. Notion describes the rest of its process as rigorous and conversational, with references treated as a serious signal, and says it publishes an interview guide for every role. Ask your recruiter for yours.
What does Notion look for in engineers?
Notion says it hires on craft and values. For engineers, craft means giving input on technical, product, and business decisions and improving how the team works. Its four values are drivers of the mission, pace setters, truth seekers, and kind and direct.
Are references important at Notion?
Yes. Notion has written that references are a strong predictor of success and an important part of its process, so choose people who worked closely with you.
