PracHub
QuestionsPremiumCoachesLearningGuidesInterview Prep
|Home/System Design/Pinterest

Design a Distributed Rate Limiter

Last updated: May 30, 2026

Quick Overview

This question evaluates a candidate's distributed systems and API infrastructure design skills, specifically covering rate-limiting algorithms, concurrency control, storage and consistency trade-offs, scalability, fault tolerance, and observability.

  • medium
  • Pinterest
  • System Design
  • Software Engineer

Design a Distributed Rate Limiter

Company: Pinterest

Role: Software Engineer

Category: System Design

Difficulty: medium

Interview Round: Technical Screen

Design a rate limiting service for a public API platform. The system must enforce configurable quotas per API key, user, IP address, and endpoint. It should support limits such as requests per second, requests per minute, daily quotas, and short burst allowance. Multiple application servers and API gateways will call the limiter concurrently. The limiter should return allow or deny decisions with a retry-after value, add minimal latency to the request path, scale to high traffic, and remain reliable during partial failures. Discuss algorithms, storage, distributed consistency, failure handling, observability, and trade-offs.

Quick Answer: This question evaluates a candidate's distributed systems and API infrastructure design skills, specifically covering rate-limiting algorithms, concurrency control, storage and consistency trade-offs, scalability, fault tolerance, and observability.

Related Interview Questions

  • Design Catalog Update Pipeline - Pinterest (medium)
  • Design an ads event reporting system - Pinterest (medium)
  • Design autocomplete and merchant bulk edits - Pinterest (medium)
  • Design highly available blob storage service - Pinterest (medium)
  • Design a global high-throughput rate limiter - Pinterest (hard)
Pinterest logo
Pinterest
May 14, 2026, 12:00 AM
Software Engineer
Technical Screen
System Design
5
0

Design a rate limiting service for a public API platform. The system must enforce configurable quotas per API key, user, IP address, and endpoint. It should support limits such as requests per second, requests per minute, daily quotas, and short burst allowance. Multiple application servers and API gateways will call the limiter concurrently. The limiter should return allow or deny decisions with a retry-after value, add minimal latency to the request path, scale to high traffic, and remain reliable during partial failures. Discuss algorithms, storage, distributed consistency, failure handling, observability, and trade-offs.

Solution

Show

Submit Your Answer

Sign in to leave a comment

Loading comments...

Browse More Questions

More System Design•More Pinterest•More Software Engineer•Pinterest Software Engineer•Pinterest System Design•Software Engineer System Design
PracHub

Master your tech interviews with 8,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.