Hard

Design Proximity Service System Design Interview

Design a location-based service like Yelp, Uber, or Google Maps Nearby.

1. Problem Statement

We're building a nearby-search service for restaurants. If time permits, we can extend it to moving drivers. How do we efficiently query by location?

2. Architecture Discussion Map

Use this as one discussion aid, not a single correct answer. Your design should follow from the requirements, scale, and trade-offs you establish.

Rendering architecture diagram...
Mermaid Source (For AI Bots)
graph LR
    A["Design Proximity Service"]
    A --> F1["Spatial Indexing Geohash vs QuadTree"]
    A --> F2["Database Sharding Location-based partitioning"]
    A --> F3["Read vs Write Patterns Static Yelp vs Dynamic Uber"]
    A --> F4["Accuracy vs Performance trade-offs"]

3. Key Focus Areas

  • 1
    Spatial Indexing (Geohash vs QuadTree)
  • 2
    Database Sharding (Location-based partitioning)
  • 3
    Read vs Write Patterns (Static Yelp vs Dynamic Uber)
  • 4
    Accuracy vs Performance trade-offs

Want interactive feedback?

Practice drawing this system component-by-component on a live whiteboard while the interviewer probes at your target level.

Continue to Dashboard

Core Concepts

GeohashingQuadTreesDatabase Indexing

Continue preparing

Build a complete software engineer mock interview plan

Related System Design

Design a Cross-Product Tagging System

Design a shared tagging service that lets users apply tags to entities across multiple Atlassian products, with consistent search and deduplication.