← Back to Directory

Nextdoor

Mid-sized

Screna has 11 Nextdoor interview write-ups. The most reported round is the technical phone screen (9).

11 interview notes · updated Jun 2026

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·Mobile Engineer·Technical Phone Screen

Jun 2026
Nextdoor mobile engineering interview that centered on a UIKit debugging exercise covering a pretty wide range of iOS-specific issues. Not a whiteboard algorithm session, more of a 'here's broken code, fix it and talk through your reasoning' kind of thing.
  • Given a UIKit project with multiple bugs, identify and fix issues related to object lifecycle and scope management.
  • In the same codebase, identify and resolve threading issues.
  • Fix table view cell sizing bugs in the provided iOS project.
  • Identify and correct button action handling bugs in the UIKit project.
  • How would you improve the overall code quality, modularity, and architecture of this iOS codebase?

“This tripped me up more than I expected.”

View Post

Nextdoor·Mobile Engineer·Technical Phone Screen

May 2026
Nextdoor mobile engineer interview that was basically one coding problem with two follow-ups tacked on. The core question was straightforward enough but the iterative rewrite at the end is where things got real.
  • Given a post with nested comment threads where each comment can have child comments at arbitrary depth, flatten the entire structure into a single array using depth-first traversal.
  • Follow-up: modify your solution to stop traversal beyond a certain depth level.
  • Follow-up: rewrite the solution iteratively using an explicit stack instead of recursion.

“Recursive solution came pretty naturally.”

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·Machine Learning Engineer·Technical Phone Screen

May 2026
Coding round at Nextdoor for an MLE role. One problem, a twist on the classic merge intervals, but with weekday-aware timestamps. The conversion trick is clean once you see it, but I fumbled around longer than I should have before landing on it.
  • Given a list of time intervals where each interval includes a weekday (Monday through Sunday), a start time, and an end time in HH:MM format, merge all overlapping intervals. Intervals can span across consecutive weekdays.

“The key move is flattening everything onto a single integer timeline: multiply the weekday index by 24*60, then add the minutes from HH:MM.”

View Post

Nextdoor·Machine Learning Engineer·Take-home Assignment

Apr 2026
Nextdoor ML Engineer take-home where you build a full classification pipeline in Colab on a tabular dataset. Pretty standard end-to-end exercise but they want you talking through decisions the whole time, not just handing over a notebook with good numbers.
  • Build an end-to-end classification model on a provided tabular dataset in Google Colab, from EDA through evaluation, and walk the interviewer through your decisions as you go.

“The part that tripped me up wasn't the modeling, it was remembering to actually narrate.”

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

Nextdoor·Machine Learning Engineer·Technical Phone Screen

Mar 2026
Coding round for an MLE role at Nextdoor. One meaty algorithmic problem that looks like a sorting question until you realize the photo grouping logic makes it way messier than it first appears.
  • You have a list of feed objects, each with an id, score, and type (Normal, Video, or Photo). Every 3 consecutive Photo objects should be merged into a single grouped photo object whose score is the highest score among those 3 photos. After grouping, sort all objects (grouped photos included) by score in descending order. How do you handle groups with fewer than 3 consecutive photos, and how does score-based sorting interact with the grouping step?

“I jumped straight to the sort and completely skipped thinking about what 'consecutive' actually means in this context.”

View Post