
Nextdoor Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 73 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Nextdoor.
Software Engineer
First I chatted with the recruiter about the job and what they were looking for. Then, I had two coding screens to test my skills. After that, I went into a panel interview with five people, including the hiring manager, where we did more coding and talked about system and architectural design.
- The coding questions are straightforward and don’t include any tricks.
- Nextdoor keeps the problems closely aligned with their actual products, making them feel like realistic tasks you might handle as an employee.
- Deeper discussion of system and architectural design.
Software Engineer
A recruiter reached out after I applied. The recruiter was amazing, answering questions daily and speeding things up. It's a pretty standard engineering loop with online assessment, coding, and behavioral parts. I got through about half of it. The reasons for not moving forward were kind of disappointing, which was a bummer since I thought I did okay. It's weird how that happens.
- What makes you want to work for this company?
- What are your salary expectations?
- Which team here do you think you'd be a good fit for?
Software Engineer - Android
I applied online and a recruiter reached out. After that, I had a coding interview which had two rounds, each an hour long. The first round was a technical coding interview where they asked about my Kotlin experience and DSA with a use case problem, not like LeetCode. The second round was an Android development coding interview to test my knowledge in that area. This round was unexpected as I wasn't told it would be Android-specific, I thought it would be like the first round. I did well in both rounds, but then they went silent and I didn't hear back. The recruiter was nice, and the interviewers were pleasant. Not sure what happened, but it was a good experience overall.
- Can you write a function to format credit card input?
- How would you approach coding for Android Views, View models, and basic UI handling scenarios?
Nextdoor Software Engineer Interview Questions
Quoted word for word from Nextdoor interview reports.
“How do you find a number that is repeated more than once in an array, using only constant extra space?”
Read reports →“Given a list of comments, where each comment has an ID and a parent ID, how would you print the comment IDs in a nested thread format?”
Read reports →“Can you create a secret santa linking for a list of people?”
Read reports →“Can you extend the version comparison logic to handle version strings like '1.2.2-alpha', '1.2.1-beta', '1.2.11-arbitary string'? The sorting rules are: A) Pre-release versions (alpha, beta, etc.) come before numeric versions. B) If versions have suffixes like '-beta' or '-runs', sort them lexicographically.”
Read reports →“Write Swift code to implement a data structure for generating recommendations from parsed post or comment data.”
Read report →“Can you create a linked list class and implement a reverse method for it?”
Read report →“Can you implement a HashMap that supports commit and rollback operations?”
Read report →“How would you parse a tree-like structure given some information about how each node is represented internally?”
Read report →“Can you build a data structure to hold a comment and its parent, and then print the comments hierarchically?”
Read report →Formats, difficulty and experience
Across all 73 Nextdoor interview reports.