Real, anonymous reports from people who interviewed for Software Engineer at Nextdoor, newest first and distilled into what to expect across the loop.
After a recruiter outreach, I went into a phone screen that quickly turned into coding. The coding screen had two parts, and I passed. From there, the loop continued, but the process also felt a bit unstable—at one point I decided to stop after I’d passed the coding screen, even though I understood the next stage was the longer interview day.
I applied online and then got contacted by a recruiter for a quick 20-minute call. After that, the process jumped straight into two scheduled rounds: a coding interview and a system design interview. The coding part felt like a LeetCode-style medium problem.
The initial recruiter outreach is generally positive and organized, focusing on background and role fit, with many candidates appreciating the clarity and responsiveness of the recruiters throughout the process.
Candidates can expect multiple coding interviews featuring LeetCode-style problems, often with a mix of easy to medium difficulty, and interviewers who may provide hints or guidance during the sessions.
A system design interview is typically included, where candidates are asked to design larger systems or components, requiring a broader understanding of architecture and engineering principles.
Behavioral interviews are part of the process, focusing on candidates' experiences and cultural fit, often utilizing STAR-style questions to assess alignment with company values.
The interview environment varies, with some candidates experiencing supportive and friendly interactions, while others report interruptions and a rushed atmosphere that can hinder performance.
Candidates frequently express frustration over the lack of feedback and closure after interviews, with many experiencing abrupt rejections without clear explanations, leading to uncertainty about their performance.
