Real, anonymous reports from people who interviewed for Software Engineer at Notion Labs, newest first and distilled into what to expect across the loop.
I started with a recruiter screen, and it felt pretty fast to move from there. The whole process stayed practical and didn’t lean on LeetCode-style puzzles. After the recruiter call, I had a technical screen where I worked through a practical coding problem. What surprised me most was how much the interview emphasized modern tooling: there was an AI-enabled coding component where I had to use an AI assistant effectively (something like Claude Code / Cursor), and the expectation was that I understood how to work with those tools rather than just write code from scratch.
My process started like it was going to be smooth: I had a recruiter screen, then a hiring manager conversation, followed by a standard demo of the product. The interview content itself didn’t worry me much, and the recruiting person was helpful about what the rounds would look like.
The interview process typically begins with a straightforward recruiter screen, followed by a technical screen that often includes practical coding exercises rather than traditional LeetCode-style questions. Candidates should expect a focus on modern tooling and collaborative coding practices.
Technical interviews often involve live coding sessions that emphasize real-world coding skills, with a mix of AI-enabled coding components and practical problem-solving. Candidates should prepare for coding challenges that are collaborative and focus on building rather than trick questions.
The interview loop includes system design discussions and conversations with managers, where candidates are evaluated on their engineering thought process and collaboration under pressure. Expect a respectful yet challenging tone during these interactions.
Many candidates reported issues with communication and feedback throughout the process, often experiencing long delays or a lack of updates after completing rounds. It's advisable to follow up proactively but be prepared for potential silence or generic responses.
The overall structure of the interview process is generally systematic, with a clear timeline that can span several weeks. However, candidates have noted inconsistencies in pacing and organization, which can affect their experience and perception of the company.
While many candidates found the interviews to be rigorous and fair, there were mixed feelings about the overall culture and engagement level of interviewers. Candidates should be prepared for varying degrees of interaction and support during technical discussions.