← Back to Directory

Notion

Mid-sized

Screna has 19 Notion interview write-ups. The most reported round is the technical phone screen (16).

19 interview notes · updated Jun 2026

Notion·Software Engineer·Hiring Manager Screen

Jun 2026
Behavioral round with the hiring manager for a Data Engineer role at Notion. Three classic prompts with probing follow-ups on each, so having tight stories ready matters more than you'd think.
  • Why do you want to join this company, and why are you leaving your current role?
  • Walk me through a project you're most proud of, covering how you scoped the problem, designed the solution, your specific contributions, and what the outcome was.
  • What's a piece of constructive feedback a manager has given you, and what did you actually do with it?

“The two-part structure tripped me up a bit.”

View Post

Notion·Software Engineer·Technical Phone Screen

Jun 2026
SQL technical screen for a Data Engineer role at Notion. One question, pretty focused on aggregation and schema reasoning. Nothing wild but the tie-handling follow-up tripped me up a bit.
  • Given an events table, write a SQL query to find the country with the highest total number of events. If there's a tie, return all tied countries. Walk through your schema assumptions and explain how your query would change if the country column lived on a separate users table instead.

“Started with the obvious GROUP BY country, COUNT(*), ORDER BY count DESC LIMIT 1 and felt good about it for about five seconds until they asked about ties.”

View Post

Notion·Software Engineer·Technical Phone Screen

Jun 2026
SQL-heavy technical screen for a Data Engineer role at Notion. The main question was a layered multi-part problem that built on itself, and the whole thing took longer than I expected to reason through cleanly.
  • Given a multi-part SQL problem where each step filters on the result of the previous one, how would you use boolean aggregation (like BOOL_OR) to flag groups, then chain those flags across sub-queries to arrive at a final metric? Also, why doesn't a single GROUP BY pass solve this?

“This one tripped me up more than it should have.”

View Post

Notion·Software Engineer·Onsite - Cross-functional / Panel

Jun 2026
A short cross-functional behavioral round at Notion for a Data Engineer role, basically a single 30-minute conversation built around one collaboration story with a Data Science partner. Pretty focused and low-pressure format, but the depth they expected on that one story was real.
  • Walk me through a project where you worked closely with a Data Science partner. How did you split up the work, stay in sync, handle disagreements, and what did you actually ship together? Looking back, what would you change about how you collaborated?

“This is the whole interview basically.”

View Post

Notion·Software Engineer·Technical Phone Screen

Jun 2026
SQL-heavy technical screen for a Data Engineer role at Notion. The whole thing basically came down to one join question but they pushed pretty hard on extensions and edge cases.
  • Given a parent table and a related child/transactional table, write a SQL query that returns all parent rows along with any matching child rows, including parents with no matches. Make sure to handle NULLs from the unmatched side and use proper aliasing. Be prepared to extend this to joining more than two tables.

“Pretty standard LEFT JOIN setup but they kept poking at it.”

View Post

Notion·Software Engineer·Technical Phone Screen

May 2026
Interviewed for a Data Engineer role at Notion and got a coding question that looked deceptively simple on the surface. The problem had some real depth once you started thinking about complexity tradeoffs.
  • Given a string (representing a password) and an integer k, write a function that counts the number of distinct substrings of exactly length k within that string.

“I went straight for the sliding window with a hash set, which is the obvious move.”

View Post

Notion·Software Engineer·Technical Phone Screen

May 2026
Notion Data Engineer interview, first part of a three-part coding problem centered on building a DAG class from scratch. Pretty approachable as a standalone problem but they made clear there were more parts coming, so you can't just slap something together and call it done.
  • Implement a DAG class with at minimum add_node and add_edge methods, where add_edge must reject any edge that would introduce a cycle. What data structure do you use internally, and how does your cycle detection work on insert?

“I went with an adjacency list and DFS-based cycle detection on every add_edge call.”

View Post

Notion·Software Engineer·Technical Phone Screen

May 2026
Notion data engineer interview with a SQL-heavy technical screen. One question, but it had enough layers to keep you busy for a while.
  • Given a customers table with budgets and a products table with prices, simulate each customer buying as many products as possible starting from the cheapest. Return the list of products each customer ends up purchasing.

“I went straight for a window function approach, running SUM(price) over products ordered by price, then joining to customers and filtering where the running total stays within budget.”

View Post

Notion·Software Engineer·Take-home Assignment

May 2026
Notion SWE interview focused entirely on a hands-on Spark data engineering task. You set up a local environment, read in CSV or JSON files, and ran a cleaning and transformation pipeline using DataFrame APIs. Pretty practical, no LeetCode nonsense.
  • Set up a local Spark environment and build a data cleaning and transformation pipeline that reads CSV or JSON input files, applies projection, filtering, joins, aggregations, and deduplication, then writes the output to disk.
  • How do you handle null or malformed rows when reading data into a Spark DataFrame?
  • When writing the cleaned output, how would you decide on a partitioning strategy?

“The core of the whole thing.”

View Post

Notion·Software Engineer·Technical Phone Screen

Apr 2026
Notion SWE interview with a frontend coding question. Pretty focused on product-adjacent UI logic, which makes sense for them.
  • Build a Todo List application that supports nested items and allows toggling items between done and undone states.

“The nesting part is what trips people up.”

View Post