How the interviewer opens it
“Design a service that enforces tenant quotas for virtual machines, CPUs, and storage. It must support concurrent resource requests, reservations, and quota reclamation.”
The prompt is vague on purpose. The first minutes are for you. Reduce the prompt to the core features and agree on the numbers before you draw.
What to clarify first
- Quota scope and units
- Scale
- Traffic and read:write ratio
- Latency
- Consistency and availability
- Reservation lifetime
- Resource providers
- Limit changes
- Durability and retries
- Excluded requirements
The interviewer has the answers. In a SysRound round, Alex gives these answers, as a real interviewer does.
Scope of a strong answer
Core requirements
- Reserve several resource types without exceeding any quota
- Convert reservations into resource allocations
- Reclaim quota after reservation cancellation or resource deletion
- Read quota usage and change quota limits
Usually out of scope
- Global quotas across regions
- Parent quotas across tenant groups
- Resource placement and physical capacity
- Billing and the implementation of resource providers
What interviewers ask about
- Concurrent resource requests
- One request consumes several resource types. Concurrent requests must share one consistent view without creating partial reservations.
- Reservation expiry
- A reservation can expire while a provider still creates resources. A clock cannot prove that the provider stopped.
- Resource reclamation
- Deletion, callbacks, and retries cross service boundaries. Premature release can approve replacements while old resources still exist.
Common mistakes
- Checks quota and updates usage in separate steps without an atomic guard.
- Treats reservation expiry as proof that resource creation stopped.
- Returns quota before resource deletion completes.
- Handles duplicate requests but ignores duplicate or late provider callbacks.
- Uses stale display values to approve resource requests.
- Adds global coordination before defining the quota scope and regional authority.
The bar by level
- Senior (L5/E5)
- Defines the full reservation lifecycle. Resolves expiry races, uncertain provider results, duplicate callbacks, and crash recovery. Separates stale display reads from authoritative approvals.
- Staff (L6+/E6+)
- States the end-to-end safety assumptions for providers and database failover. Explains why uncertain work can retain quota indefinitely. Addresses hot scopes without weakening correctness. Adapts the design to global limits and defines the availability trade-off.
Sources · 1 reference
These records explain where the question appears. A company tag or candidate report does not guarantee a future interview question.
SysRound · 1 record
No company association
Design a cloud resource quota service
Reported date not specified
Source snapshot: Nov 12, 2026
View source