InterviewLegend

Design a Rate Limiter

Signature problem
Alex Chen52 min readAdded 835 real interview reports

A rate limiter counts the requests each caller has made recently and turns away the ones over its limit, usually with a 429 Too Many Requests response. It keeps one buggy integration or one scraper from using up capacity that everyone else needs, and it gives every caller a predictable share. At Walmart it's among the most reported design prompts in recent loops, and it shows up in more forms than most. Staff (IN5) loops can give it a dedicated system design round. SDE-3 loops tend to combine it, high-level design first and then low-level design with code. It has also come up as a Java low-level design round, and as a data structures round where you build an in-memory version for a refund service. One SDE-3 loop even asked it in the managerial round, next to questions about the candidate's own project.

The Walmart angle
Walmart's Marketplace APIs use a token bucket, so you can anchor the design in a real system. An empty bucket returns 429, and every response carries x-current-token-count and x-next-replenishment-time. Limits are set per endpoint, and a seller's own integration and each Solution Provider app get separate allotments. That's the shape designed here.

WalmartPremium lesson · System design round

The Walmart design, worked end to end.

  1. The API and data modelSystem design · Signature problem
  2. The design, drawn out2 diagrams
  3. 8 deep divesWith the tradeoffs
Get the Walmart questions

$49 a year · all 107 companies · instant access

835 Walmart interview reports · guide updated

Walmart interview guide

Know what Walmart asks before you walk in.

24 coding · 5 system design · 20 behavioral questions

Get Premium$49 a year · Instant access
Or start freeNo card.

Get their questions first.

Had your Walmart interview?How we research

InterviewLegend is independent and not affiliated with or endorsed by any company it covers.