Official Judge Rulebook

Evaluation Rules, Marks Distribution & Costing Price

Every submission on HLDArena is graded by a 100% deterministic compiler and discrete-event simulator — zero LLM randomness. Every question splits marks into 60% Functional Requirements & Plain-English Write-up and 40% Non-Functional Diagram Simulation.

Open Problemset

1. Marks Distribution Across Difficulty Tiers

Harder tiers carry higher maximum marks while preserving the exact 60% Write-up / 40% NFR ratio across all 110 questions.

Scoring ComponentShareEasyMediumHardExpert
Total Question Marks100%500 pts1,000 pts1,500 pts2,000 pts
Part A — Functional Requirements & Plain-English Write-up60%300 pts600 pts900 pts1200 pts
A1. Functional Requirements (FR-1..FR-N) Coverage
Address every Functional Requirement bullet on the left end-to-end (request flow, state updates, and edge cases).
22.5%113225338450
A2. Plain-English HLD Explanation Quality
Write complete, natural English sentences (15+ words) explaining which component acts and why. Keyword lists or copied prompt text fail.
10.5%53105158210
A3. Data Model, Keys & Partitioning
State your record keys, identifier approach, and how data is partitioned as volume grows.
10.5%52105157210
A4. Consistency & Failure Handling
State how reads and mutations maintain the required consistency model and how component failures are handled.
9.0%4590135180
A5. 1:1 Diagram <-> Write-up Alignment & Sizing
Explain and state capacity sizing for every box drawn on your whiteboard, and draw every component you mention in text.
7.5%3775112150
Part B — Diagram Simulation (Non-Functional Requirements)40%200 pts400 pts600 pts800 pts
B1. Latency SLO Adherence (weighted p50 / p99)11.0%55110165220
B2. Throughput & Burst Goodput Capacity11.0%55110165220
B3. Resilience, Failover & Availability9.0%4590135180
B4. Monthly Cloud Cost Efficiency6.0%306090120
B5. Topology Clarity & Simplicity3.0%15304560

2. Standardized Monthly Costing Price Schedule

Every question computes monthly cloud spend deterministically from your drawn components and sizing specifications: Total Monthly Cost = Σ(Component Cost) + Network Egress. Exceeding a question’s budget cap triggers MLE_OVER_BUDGET.

Infrastructure Component RoleSmall ($/mo)Medium ($/mo)Large ($/mo)Unit Scaling Formula
Client / External Origin$0$0$0External traffic source (free)
Anycast DNS$25$45$85flat per DNS node
Load Balancer$35$80$170unit × instances
Object / Blob Store$35$85$180unit × instances
Compute / App Service$45$95$195unit × instances
API Gateway$50$115$240unit × instances
Coordination / Lock$55$115$220unit × instances
Message Queue / Stream$60$135$290unit × max(instances, ceil(partitions/8)) × (1 + min(2, replicas))
In-Memory Cache$65$145$310(unit × nodes + extra RAM) × (1 + replicas)
Edge CDN$75$160$340unit × instances (1.0× global edge)
Key-Value / NoSQL DB$95$210$450unit × shards × (1 + replicas) × instances
Search / Index Store$110$235$490unit × shards × (1 + replicas) × instances
Relational DB$115$245$520unit × shards × (1 + replicas) × instances
Unspecified Defaults

Client origin = $0. Unspecified boxes default to 1 instance, small tier, 1 shard, 0 replicas, single-AZ (8 GB RAM on cache).

Cache Memory Surcharge

Includes 8 GB RAM/node (+$3/GB above 8 GB×nodes). NVMe/SSD-tiered cache includes 64 GB/node (+$0.10/GB extra).

AZ / Region Multipliers

Single-AZ: 1.0× · Multi-AZ: 1.05× with redundancy (instances > 1 or replicas ≥ 1), 1.30× standalone · Multi-Region: 2.35×.

Elastic & On-Demand

Auto-scaling (+25% burst pool). Serverless / on-demand DB or KV store (0.55× unit factor).

Network Egress

$55 per 10k avg goodput RPS ($32 per 10k RPS with Edge CDN) + $75 per cross-region link per 10k RPS.

3. Plain-English Write-up & 1:1 Diagram Alignment Rules

How to structure your Design Write-up so the deterministic compiler credits your design accurately.

Cover Every Functional Bullet (FR-1..FR-N)

Each question lists standardized Functional Requirement bullets (create/write path, read/fetch path, update/delete or expiry lifecycle, and consistency/fault behavior). Explain end-to-end how your architecture handles every bullet.

Write Natural Plain-English Prose (≥ 15 Words)

Write complete English sentences connecting which component acts, what operation it performs, and why. Bare keyword dumps, repetitive filler, unfilled [...] template prompts, or copied prompt text fail with WA_FUNCTIONAL.

Keep 1:1 Parity Between Diagram & Write-up

The simulator enforces strict 1:1 topology lock: components mentioned only in text without being drawn on the whiteboard are ignored in simulation, and drawn boxes left unexplained in text receive uncalibrated single-node defaults.

State Explicit Sizing, Keys & Failure Handling

Specify hardware tier (small, medium, large), instance/shard/replica counts, memory capacity, partitioning keys, consistency rules, and AZ/region layout in either box labels or your write-up.

4. Judge Verdict Codes

Verdicts are evaluated in priority order across 3 sample waves and 4 hidden stress/fault waves.

AC
Accepted: Passes topology validation, plain-English FR write-up gate, consistency guarantees, latency SLO, availability target, and monthly budget across all 7 judge waves.
INVALID_TOPOLOGY
Invalid Architecture Graph: Canvas has no connected request path from client/ingress to compute/backing services, or contains isolated/unwired infrastructure components.
WA_FUNCTIONAL
Functional / Write-up Gate Failed: Write-up is empty, shorter than 15 words, keyword-only spam, unfilled [...] template prompts, copied prompt text, or leaves required FR-1..FR-N bullets unexplained.
WA_CONSISTENCY
Consistency Violation: Architecture serves stale or conflicting state (e.g., missing cache invalidation on read-after-write or missing atomic/quorum coordination on strict inventory problems).
TLE_LATENCY_SLO
Latency SLO Exceeded: Weighted p99 latency across simulated baseline, hot-key skew, and burst traffic waves exceeds the problem’s Max p99 ms threshold.
AVAILABILITY_BREACH
Availability Target Breached: Single points of failure, queue saturation, or AZ/node crash waves drop goodput availability below the problem’s minimum availability percentage.
MLE_OVER_BUDGET
Monthly Cloud Budget Exceeded: Total monthly infrastructure + network egress cost exceeds the problem’s monthly USD budget cap.

5. Competitive Architect Rating & Rank Tiers

Every account starts at 1200. Solving new questions with AC (or improving your best score on solved questions) increases your Architect Rating; experimenting with failed runs never penalizes your rating.

Associate< 1250
Associate Architect
Engineer1250–1399
Systems Engineer
Senior1400–1599
Senior Systems Architect
Staff1600–1849
Staff Architect
Principal1850–2149
Principal Architect
Distinguished2150–2499
Distinguished Architect
Grandmaster2500+
Grandmaster Fellow

6. ArenaCoins Earning Rules

ArenaCoins are stored per user account in the database. Each question solve, General HLD discussion, Interview Experience, published AC solution, and Bio profile milestone is credited per user.

Difficulty TierSolving (AC)Posting AC Solution
Easy+1+5
Medium+3+8
Hard+6+10
Expert+10+15
Profile Bio & Community Milestones
Post General HLD Discussion+80
Share Interview Experience+50
Add LinkedIn+25
Add GitHub+20
Add LeetCode+15
Add Codeforces+10
Add CodeChef+10