← Nextdoor Interview Insights

Nextdoor·Software Engineer·Onsite - System Design / Architecture·Senior

SeniorPrefer not to say
Jun 2026

Summary

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.

Questions Asked (1)

Q1

Design the Nextdoor Newsfeed system.

System DesignTechnical Trade-offsData Modeling
Author's notes

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

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by clarifying functional and non-functional requirements, then design a scalable feed system that balances relevance and freshness for hyperlocal content. Focus on the unique aspects of Nextdoor: neighborhood-level granularity, privacy, and the mix of user-generated and algorithmic content.

Pro tip: Emphasize how you would handle the 'cold start' problem for new neighborhoods and the trade-offs between precomputed and on-the-fly feed generation, showing awareness of real-world constraints.

1. Clarify Requirements

Ask questions to understand scale (users, posts, neighborhoods), feed types (chronological vs. ranked), latency requirements, and privacy constraints. Define core features: post creation, feed retrieval, ranking, and notifications.

2. High-Level Design

Outline the main components: API gateway, feed service, post service, user/neighborhood service, ranking service, and data stores (SQL/NoSQL, cache, search index). Sketch data flow from post creation to feed delivery.

3. Data Modeling

Design schemas for users, neighborhoods, posts, and relationships (e.g., user-neighborhood membership). Consider how to efficiently query posts by neighborhood and user connections.

4. Feed Generation & Ranking

Discuss strategies for feed generation: fan-out on write vs. read, precomputed timelines, and ranking algorithms (e.g., relevance, recency, engagement). Address scalability and personalization.

5. Scalability & Trade-offs

Explain how to scale each component (sharding, caching, CDN), handle hot neighborhoods, and ensure low latency. Discuss trade-offs like consistency vs. availability, and cost vs. performance.

Key Points to Mention

  • Neighborhood-level partitioning and privacy controls
  • Feed ranking algorithm (e.g., EdgeRank-like, machine learning models)
  • Fan-out on write vs. fan-out on read for feed generation
  • Caching strategies (Redis, Memcached) for hot feeds
  • Handling of media content (images/videos) with CDN and object storage
  • Monitoring and metrics for feed quality and system health

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.