Real, anonymous reports from people who interviewed for Software Engineer at Notion Labs, newest first and distilled into what to expect across the loop.
Get your personalized Notion Labs Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
My experience started with a recruiter outreach and then quickly moved through the next stages, with a surprisingly fast turnaround after each step. I’d receive updates by email shortly after rounds, and every interviewer I spoke with was friendly and easy to work with. The whole process gave off the feeling that they care about candidate experience.
The recruiter call was logistics-focused, but the tone was warm and understanding, and it put me at ease going into the technical work. Across the rest of the loop, I didn’t feel blindsided by odd formats or unclear expectations, and I kept getting signals that my communication and performance were being taken seriously.
4 months ago
Average Positive New York, NY
My process felt pretty straightforward from the start, and the biggest pattern was how practical the technical work was. I didn’t see much “LeetCode-style” focus; instead, I got questions and coding tasks that leaned more toward working with a real codebase—especially around React proficiency and how I’d reason about abstractions and engineering tradeoffs.
After the initial screens, the technical portions stayed grounded in implementation. Even when the questions pulled in core data structure or algorithms concepts, they were framed to match the kind of thinking you’d use while building features rather than solving trick problems. I also remember a coding interview that involved writing SQL against data sourced from the Notion API, and I was glad I had reviewed the API documentation beforehand because that context mattered.
5 months ago
Average Positive United States
After the recruiter call, I went into an OA/take-home style step, then a longer onsite sequence that felt designed around real engineering work rather…
10 months ago
Average Negative Canada
The process I experienced started with a very uncomfortable tone that made it difficult to think out loud. In the technical portion, the interaction f…
10 months ago
Average Negative United States
My experience felt oddly scripted and predetermined. The recruiter matched me into a team where the role required TypeScript, and I hadn’t applied spe…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Recruiter & Initial Communication
The interview process typically begins with a recruiter call that is warm and informative, setting clear expectations for the subsequent steps. However, candidates have reported inconsistencies in follow-up communication, with some experiencing significant delays and a lack of updates after initial screenings.
Recruiter callCommunicationExpectations
Technical Screen & Coding Challenges
Candidates can expect a technical screening that focuses on practical coding tasks rather than traditional algorithmic problems, often involving real-world scenarios and technologies like React and SQL. The interviews emphasize collaboration and practical problem-solving, although some candidates noted varying levels of engagement from interviewers during these sessions.
Coding challengesReactPractical tasks
Onsite Interviews & Structure
The onsite interviews typically consist of multiple rounds that include coding, systems design, and behavioral questions, all aimed at assessing real engineering skills and cultural fit. While many found the process organized and respectful, some experienced a lack of clarity and engagement from certain interviewers.
Overall, candidates reported a mixed experience regarding feedback and communication post-interview, with some feeling well-treated and others left in limbo with little closure. The quality of feedback varied, and many expressed a desire for more constructive insights after their interviews.
Candidate experienceFeedbackCommunication gaps
Interview Tone & Environment
The tone of the interviews generally ranges from friendly and supportive to, in some cases, unprofessional or dismissive, impacting candidates' comfort levels and performance. A collaborative atmosphere is preferred, but some candidates reported feeling lectured or pressured during technical discussions.
Interview toneCollaborationComfort level
Process Timeline & Efficiency
Candidates noted that the timeline for the interview process can vary significantly, with some experiencing quick turnarounds while others faced lengthy delays and uncertainty. This inconsistency can affect candidates' perceptions of the company's organization and respect for their time.