Available question text
Debug and fix a broken token-based rate limiter, then analyze a proposed code change that passes existing tests but introduces a regression, and write a new test case that exposes the incorrect behavior.
Related questions
Continue with questions that share topics or the same question type.
- Token Bucket Rate Limiter (Go Code Review)
Practical engineering
- Token Bucket Rate Limiter (Java Code Review)
Practical engineering
- Design a Logging Library with Severity Filtering, Rate Limiting, and Aggregation
Practical engineering
- Firewall Rule Engine: Debugging and Refactoring
Practical engineering
Sources · 1 reference
These records explain where the question appears. A company tag or candidate report does not guarantee a future interview question.
Hello Interview · 1 record
Palo Alto Networks
Token Rate Limiter: Debugging and Testing
Reported Oct 25, 2026 · 1 source report
JUNIOR
Source snapshot: Nov 12, 2026
View source