RepostedStripe logo

Stripe · Phone screen

In process

Stripe SWE Intern Rate-Limiter Screen: 1 Experience

Software engineer · InternshipOct 2025
Shared by

Stripe SWE intern screen, October 2025: a 45-minute per-key rate limiter with hit and allowed, built for many keys and high concurrency.

At a glance

  • Process: a 45-minute screen (01).
  • Asked recently: a per-key rate limiter with hit and allowed (01).
  • Difficulty: not rated; sliding or fixed windows were both accepted.
  • Practise first: Per-Key Rate Limiter.

Coverage: one Stripe software engineering intern candidate; screen around October 2025 (report month).

What came up

Topic Reports Last seen
Rate limiting and queues 1 of 1 Oct 2025

Questions we found

Algorithms / Data Structures

Question Reports Last seen
Per-Key Rate Limiter 1 Oct 2025

1 detailed candidate timeline

01: A rate limiter for many keys

Interview date: October 2025 (report month) · Role: Software Engineering Intern · Result: not disclosed

  1. hit(key, timestamp) records an access; allowed(key, timestamp) checks whether the recent-window count is within the limit: Per-Key Rate Limiter. Sliding or fixed windows were both allowed, and the design had to handle many keys and high concurrency.
  2. Discussion: deques or ring buffers, cleaning expired entries, bursts, unknown keys, out-of-order timestamps, long idle periods, and time and space costs.

Common questions

What is the Stripe intern rate limiter screen?

Report 01: per-key hit and allowed calls over a time window, for many keys and high concurrency.

Keep practicing

Sources: Anywhere useful interview info can be found.

0 total reactions. Your reactions: none.
0 comments

Comments

0

No comments yet — be the first to share what you know.