Nextdoor Software Engineer interview questions

5 Software Engineers have shared notes from their Nextdoor interviews, with the questions they were asked in each round. That is 45% of the 11 Nextdoor interview notes on Screna AI.

5 Software Engineer interview notes

Nextdoor·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Interviewed for a software engineering role at Nextdoor and got a system design round focused on their newsfeed. Pretty standard format but the problem had enough Nextdoor-specific quirks to keep it interesting.
  • Design the Nextdoor Newsfeed system.

“Spent the first few minutes just thinking about what makes Nextdoor's feed different from a generic social feed.”

View Post

Nextdoor·Software Engineer·Technical Phone Screen

May 2026
SQL-heavy technical screen for an analytics engineer role at Nextdoor. Three queries back to back, then a discussion about indexing. Pretty standard stuff but the tie-breaking and index conversation took longer than I expected.
  • Given a users table with a signup timestamp and a follows table, write a SQL query to return the total number of users.
  • Write a SQL query to find the calendar month in which the most users signed up, returning the month and the count.
  • Write a SQL query to find the user with the most followers, returning the user_id and follower count. How would you handle ties?
  • What indexes would speed up each of these three queries, and why?

“Easiest of the three, just COUNT(*) on users.”

View Post

Nextdoor·Software Engineer·Technical Phone Screen

Apr 2026
Nextdoor analytics engineering interview that went deep on SQL ETL design, specifically building idempotent pipelines that compute KPIs from raw event tables into rollup structures. Pretty technical throughout, no fluff questions.
  • Write an idempotent SQL ETL query that computes user growth KPIs (new users and cumulative users) for a given target date and upserts the results into a rollup table.
  • Write an idempotent SQL ETL query to compute DAU (distinct active users on a target date) from the sessions table and load it into the rollup table.
  • Write an idempotent SQL ETL query for photo activity KPIs: photos uploaded, likes received, and comments received on a target date, loading results into the rollup table.
  • Write an idempotent SQL ETL query to compute follower distribution stats as of end of a target date: average followers, median, 90th percentile, and percent of users with at least one follower.

“The idempotency part is what tripped me up at first.”

View Post

Nextdoor·Software Engineer·Technical Phone Screen

Apr 2026
Coding round for a software engineer role at Nextdoor. One problem, feed grouping, which sounds straightforward until you start thinking about edge cases with the ordering logic.
  • You're given a list of feed items (Normal, Video, Photo), each with an id, type, and score. Group every 3 consecutive Photos into a PhotoGroup (preserving their original order), where the group's score is the max score of its members. Then sort all items (including ungrouped ones) by score descending.

“The grouping part clicked pretty fast but I tripped on the score calculation.”

View Post

Nextdoor·Software Engineer·Technical Phone Screen

Apr 2026
Nextdoor coding screen with a calendar interval merging problem. The twist on the standard LC 56 variant kept things interesting, and the wraparound edge case is where things could go sideways fast if you're not careful.
  • Given a list of weekly time intervals where each endpoint is represented as a string like 'DAY HH:MM' (e.g. 'Mon 09:00'), merge all overlapping or adjacent intervals. Intervals that appear to wrap past Sunday back to Monday should be split before merging. Return the merged intervals sorted chronologically within the week.

“The core merge logic isn't the hard part, converting the string format to minutes-since-Monday and back is where I lost a few minutes.”

View Post