Design Nextdoor

Problem Statement

Design Nextdoor, a neighborhood-based social network where users verify their home address to join a geographically bounded community, then interact through a localized feed, classifieds, event postings, and private group chats with verified neighbors.

This is not a generic social network. Unlike Facebook or Twitter where content flows globally, Nextdoor partitions every user into exactly one neighborhood—a polygon-defined geographic area typically containing 500 to 5,000 households. The fundamental constraint is that content visibility is bounded by geography: a post in the Mission District of San Francisco is invisible to a user three blocks away in the Castro if those blocks belong to different neighborhood polygons.

Why This Problem Is Distinctive

A global social network optimizes for engagement and virality. Nextdoor optimizes for trust, locality, and privacy. The design challenges are fundamentally different:

1. Identity verification is physical, not digital. Users must prove they live at a specific address. This requires integrating with postal services, geolocation APIs, credit bureaus, or sending physical postcards with verification codes.

1. Content partitioning is geographic, not interest-based. A user belongs to exactly one primary neighborhood (plus optionally adjacent neighborhoods). Feed generation is bounded by polygon containment, not by social graph edges.

1. Privacy is existential. A user's home address is the most sensitive PII in the system. It must never be exposed to other users, yet it drives every access-control decision.

1. Moderation is community-scale. Conflicts between neighbors are qualitatively different from anonymous internet toxicity. The moderation system must support community-elected leads, dispute resolution, and escalation paths.

1. Scale is wide but shallow per partition. 300,000+ neighborhoods means 300,000+ independent communities, each with modest activity. The system must handle this fan-in/fan-out pattern efficiently.

Public Operating Baseline

Nextdoor publicly reports:

• 80 million+ registered users across 11 countries
• 300,000+ neighborhoods globally
• ~70% of US neighborhoods have at least one Nextdoor member
• Active in US, UK, Canada, Australia, Germany, France, Italy, Netherlands, Spain, Sweden, Denmark
• IPO via SPAC in November 2021 (NYSE: KIND)

These are cited public figures. For capacity planning in this design, we will state explicit assumptions.

The Four Architectural Planes

1. Identity & Verification Plane: Address verification pipeline, identity resolution, neighborhood assignment, re-verification workflows.
2. Content & Feed Plane: Post creation, neighborhood-scoped fan-out, feed ranking, classifieds, event listings.
3. Communication Plane: Group chat, direct messaging, notifications, invite-only semantics.
4. Governance Plane: Content moderation, community leads, dispute resolution, privacy enforcement, compliance.

A strong interview answer keeps these planes separate. The verification plane must not block content reads. The communication plane must degrade independently of the feed plane. Governance overlays all planes without becoming a single point of failure.