Prep RoomSign inStart free
Code RoomConcurrent rate limiter
HardPrep Room Coding #4642

Concurrent rate limiter

Vibe & agenticNetworking & APIsConcurrencySenior–Staff~20 min

You need a client-side rate limiter in Go that throttles outbound calls to a third-party API to its published quota (e.g. 100 requests/second) from across many goroutines. You'll have an AI agent implement it. Write the prompt/spec — constraints, edge cases, acceptance criteria — so it's correct first try under concurrency. What does a naive prompt ("throttle the API calls to 100 per second") get wrong?

Implement
token_bucket_admit(capacity: int, refill_per_sec: int, arrival_ms: list[int]) → list[bool]
Examples
in[2,2,[0,0,0]]out[true,true,false]
in[1,1,[0,500,1000]]out[true,false,true]
in[2,2,[900,950,1000,1050]]out[true,true,false,false]
What a strong answer looks like

Treat the AI’s output as a draft to verify, not an answer to trust. Name the specific flaw and the input that triggers it, say how you’d catch it (tests, edge cases, reading critically), and how you’d re-prompt or decompose to get it right.

0:00 of about 20 min

Vibe & agentic: describe the solution in plain language (or narrate it) and the coach grades your approach.

Which questions mattered is sealed until you submit. Telling you now would just be handing over the edge cases.