
Nextdoor Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 178 interview experiences · FREE TO READ
Which role are you interviewing for?
30 roles · 178 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Nextdoor.
Executive Assistant
Applied and had a phone screen with the recruiter. It was positive and they said next steps would be to meet with the hiring manager. After that, communication got murky. My LinkedIn was viewed privately by someone at the company, and I waited about two weeks for next steps. Then I was told the role location had changed, but shortly after, the same role was reposted for the original location. While everyone was polite, the shifting information and lack of transparency made the experience frustrating.
- Can you share an instance where you functioned as a genuine business partner to a leader, going beyond typical administrative duties? How did your contributions facilitate progress for the team or company?
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?
Talent Acquisition Specialist
I interviewed with Nextdoor and was excited about the opportunity to join the team. However, after multiple conversations, I never received an update on my candidacy even after following up. While I understand that hiring processes can be complex, the lack of communication was disappointing. Even a brief update would have been appreciated, especially with questions revolving around candidate experience. A strong candidate experience should include timely follow-ups, especially for those who have invested time in the process. That said, I appreciate the opportunity to interview and hope Nextdoor improves its communication with future candidates.
- Can you describe your sourcing efforts and how you manage stakeholders?
Staff Software Engineer
The interview process involved two leetcode-style coding questions. I was surprised by this as I had anticipated more system design questions. The first interviewer was too quick to offer suggestions, which I felt might have been detrimental. My experience suggests that guiding candidates too much can be confusing and unproductive. Despite the circumstances, I believe I performed reasonably well. However, the questions were lengthy, time was limited, and I felt rushed by the interviewers towards the end. Ultimately, I was not offered the position.
- Could you construct a bi-directional graph representing users, posts, and comments?
- Can you create a function for a random Secret Santa assignment?
Nextdoor 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 →“Can you write a function to determine if two HashMaps are identical, considering keys are strings and values can be strings or other HashMaps?”
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 construct a tree from a given parent-child comment history?”
Read reports →“Can you create a secret santa linking for a list of people?”
Read report →“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 report →“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 →“How would you parse a tree-like structure given some information about how each node is represented internally?”
Read report →Formats, difficulty and experience
Across all 178 Nextdoor interview reports.