I built Swedle because I noticed a gap between reading about SWE concepts and actually recognizing them in practice. You can read the SRE Book or DDIA cover to cover, but when a system starts misbehaving at work, pattern-matching from vague symptoms to root cause is a different skill entirely. The format is simple — you get progressive clues about a real software problem, starting vague ("deploys are getting slower") and ending specific. The challenge is identifying the problem with as few clues as possible. It covers four sources that most engineers encounter at some point: the Google SRE Book, Martin Fowler's catalog, The 12 Factor App, and Designing Data-Intensive Applications. There are 500 puzzles at launch, one per day. No accounts, no install — just open the site and play. Scores are shareable in the same grid format people are used to from Wordle.

Swedle — Daily SWE Diagnostic Puzzle

Daily puzzle: diagnose SWE problems from progressive clues.

Daily puzzle: diagnose SWE problems from progressive clues.