The Incident Challenge
theincidentchallenge.com/ →Production incidents, against the clock, for real
WHAT IT SOLVES
You might ship features fast, but can you debug a live incident at 3 AM under pressure? That's what this tests
WHY IT'S INTERESTING
It's not about syntax, it's about triage
No 'write a function' — you get production logs, monitoring, and a broken service. Find what went wrong and fix it. Only 20% reach the correct answer. That's a difficulty sweet spot
Bi-weekly events, 36 countries, real competition
Not a static quiz bank — it's a live bi-weekly event with leaderboards, timers, and real stakes. 300+ participants across 36 countries. Running a global community event on schedule is its own engineering challenge
The 'Famous Incidents' archive
Past challenges include 'Famous Incidents' — real-world production failures from the industry's history. Not made-up homework problems, but actual messes someone had to clean up
「"Something breaks. Your job is to figure out what happened, why it happened, and how to fix it fast."」
TECH GUESS
Likely Next.js frontend, unclear backend — the leaderboard and timer mechanics suggest a real-time component (WebSocket or similar)
Discussion (0)
- No comments yet — be the first.
