Notion Software Engineer Interview Experience - United States

Overview

This interview experience at Notion for a Software Engineer position on the Developer Experience team provides valuable insights into potential red flags in the hiring process. The candidate, who was referred into the general talent pool, experienced a series of concerning interactions that culminated in a virtual onsite with what appeared to be a predetermined outcome. This case study highlights the importance of understanding recruiting dynamics and recognising warning signs during the interview process.

The position was on the Developer Experience (DevEx) team, which required TypeScript expertise—an area outside the candidate's primary skillset. Despite this initial mismatch, the recruiter proceeded to match the candidate to this team without conducting a proper team-matching discussion or assessing fit for the role's technical requirements.

Interview Process

Initial Referral and Matching

The candidate was referred into Notion's general talent pool rather than applying directly to a specific team. The recruiter matched them to the Developer Experience team without any preliminary discussion about technical fit, career interests, or team preferences. This unilateral matching process raised questions about the thoroughness of the recruiting approach, particularly given that the role required TypeScript experience which the candidate did not possess.

Phone Screen

The technical phone screen was completed successfully with positive feedback from the interviewer. The candidate demonstrated adequate technical competency to proceed to the next stage. However, following this successful screen, the recruiter went silent for two weeks despite the candidate following up twice. No response was received until the second follow-up message was sent.

Hiring Manager Discussion

After the prolonged silence, the candidate was finally scheduled for a hiring manager chat. Notably, the hiring manager himself expressed surprise that this discussion was happening after the phone screen, stating that this conversation 'should have been before the phone screen.' This indicated a lack of communication between the recruiter and the hiring manager regarding the process flow.

The hiring manager discussion was described as the only genuine interaction throughout the process. The manager was engaged, effectively sold the role and team vision, and did not express concern about the TypeScript experience gap. The hiring manager confirmed that the virtual onsite would proceed based on the positive signals from both the phone screen and their discussion.

Technical Rounds

Virtual Onsite Structure

The virtual onsite was structured to include four interview rounds. The candidate completed two rounds before receiving notification that the process was being terminated.