PracHub
QuestionsPremiumLearningGuidesCheatsheetNEWCoaches
|Home/System Design/Lyft

Design web crawler for 1000 devices

Last updated: Mar 29, 2026

Quick Overview

This question evaluates understanding of distributed systems and large-scale web crawling, including coordination and state management, URL deduplication and scheduling, politeness and per-host rate limiting, fault tolerance, load balancing, and storage for fetched content.

  • hard
  • Lyft
  • System Design
  • Software Engineer

Design web crawler for 1000 devices

Company: Lyft

Role: Software Engineer

Category: System Design

Difficulty: hard

Interview Round: Onsite

##### Question Design a web crawler that starts from a single link and distributes crawling across 1,000 different devices; address coordination, load balancing, fault tolerance, and scalability follow-ups

Quick Answer: This question evaluates understanding of distributed systems and large-scale web crawling, including coordination and state management, URL deduplication and scheduling, politeness and per-host rate limiting, fault tolerance, load balancing, and storage for fetched content.

Related Interview Questions

  • Design a Donation Platform - Lyft (hard)
  • Design a charity donation platform - Lyft (medium)
  • Design a scalable real-time chat system - Lyft (hard)
  • Design a distributed web crawler - Lyft (hard)
  • Design a scalable news feed system - Lyft (hard)
Lyft logo
Lyft
Aug 4, 2025, 10:55 AM
Software Engineer
Onsite
System Design
15
0

Distributed Web Crawler: Design for 1,000 Devices

Context

Design a production-ready web crawler that starts from a single seed URL and scales crawling across 1,000 heterogeneous devices. The crawler should respect robots.txt and per-host politeness constraints, deduplicate URLs/content, and persist pages and metadata.

Requirements

  • Start from one seed link and discover new URLs recursively.
  • Distribute crawling across ~1,000 devices.
  • Address:
    1. Coordination of work and state
    2. Load balancing and throttling
    3. Fault tolerance and recovery
    4. Scalability and typical follow-ups
  • Assume an internet-scale target with diverse domains and varying latency.

Deliverables

  • High-level architecture and data flow
  • How URLs are assigned, deduplicated, and scheduled
  • Policies for robots.txt, per-host rate limits, retries
  • Storage approach for frontier state and fetched content
  • Specific mechanisms for coordination, load balancing, fault tolerance, and scaling

Solution

Show

Comments (0)

Sign in to leave a comment

Loading comments...

Browse More Questions

More System Design•More Lyft•More Software Engineer•Lyft Software Engineer•Lyft System Design•Software Engineer System Design
PracHub

Master your tech interviews with 7,500+ real questions from top companies.

Product

  • Questions
  • Learning Tracks
  • Interview Guides
  • Resources
  • Premium
  • For Universities
  • Student Access

Browse

  • By Company
  • By Role
  • By Category
  • Topic Hubs
  • SQL Questions
  • Compare Platforms
  • Discord Community

Support

  • support@prachub.com
  • (916) 541-4762

Legal

  • Privacy Policy
  • Terms of Service
  • About Us

© 2026 PracHub. All rights reserved.