Kyle Kingsbury Portfolio
Creator of Jepsen, the distributed-systems testing framework that has found and publicly documented consistency bugs in MongoDB, Cassandra, etcd, Redis, and dozens of other production databases. His write-ups are a de facto industry standard for how to test distributed system claims empirically.
What makes it work
A breakdown of the choices that make this portfolio stand out.
Adversarial testing as the portfolio's core work
Jepsen doesn't just describe distributed systems theory — it runs real databases under network partitions and process crashes and publishes exactly which consistency guarantees held and which didn't, with reproducible test code.
Naming vendors and being specific about failures
The Jepsen reports name the exact database, version, and configuration that failed, rather than speaking in generalities about "some systems." That specificity is what made the reports change how database vendors market consistency guarantees.
Long-form technical writing that doesn't soften uncomfortable findings
The reports are written for engineers who need the truth about a system's failure modes, not for the vendor's marketing team — a stance that builds long-term reader trust even when it creates short-term friction.
What Backend Developers can take from this
Specific, actionable tips to apply to your own portfolio — no generic advice.
If you can, publish work that produces a falsifiable, reproducible result (a test suite, a benchmark, a failing repro) rather than only opinion.
Name specifics — exact versions, exact configurations, exact failure conditions — instead of hedging into vague generalities.
A body of work built around one rigorous methodology, applied repeatedly across many subjects, reads as more credible than one-off posts on scattered topics.
More Backend Developer portfolios
Ready to build your portfolio?
Follow the Backend Developer roadmap — skills, projects, and timeline to get hired.