Backend Developer

Kyle Kingsbury Portfolio

Computer safety researcher working as an independent consultant

Creator of Jepsen, the open-source distributed-systems testing library (7.5k GitHub stars) behind free public analyses of MongoDB, Cassandra, etcd, Redis and more than two dozen other databases, queues and coordination services since 2013. Each report checks a system against its own documentation's claims. The most recent cover MariaDB Galera Cluster 12.1.2 and NATS 2.12.1.

Distributed SystemsJepsenDatabase TestingClojure

Location

American Midwest

Companies

Jepsen

Skills

Distributed SystemsJepsenDatabase TestingClojure

Notable

  • Creator of Jepsen, the distributed-systems safety testing library (7.5k GitHub stars)
  • Jepsen analyses of more than two dozen databases, queues and coordination services since 2013
  • Author of the Riemann monitoring system (4.3k GitHub stars)
  • Author of the Clojure from the Ground Up tutorial series

What makes it work

A breakdown of the choices that make this portfolio stand out.

1

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.

2

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 the point: Jepsen's stated aim is to push vendors "to make accurate claims and test their software rigorously."

3

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.

Projects

Kyle Kingsbury's main body of work is other people's databases, analyzed one version number at a time. Jepsen is the library that breaks them, and Riemann shows he builds as well as he tests.

Open SourceadvancedOngoing since 2013

Jepsen

ClojureDistributed SystemsFault Injection

A Clojure framework for distributed-systems verification with fault injection. It runs real binaries on real clusters, injects network partitions, clock skew and crashes, records a concurrent history, and checks that history against a consistency model.

A reusable testing method for distributed systems, built and maintained for over a decade.

  • Opaque-box testing: bugs it finds are observable in production, not theoretical

  • Generative, property-based operation histories

ResearchadvancedOne report per system

Jepsen analyses

JepsenConsistency ModelsDatabases

Free public reports, each checking whether a specific database, queue or consensus system lives up to its documentation's claims. The list runs from Redis 2.6.13 and MongoDB 2.4.3 (2013) to NATS 2.12.1 and MariaDB Galera Cluster 12.1.2.

Each report names the exact version, configuration and failure it found.

  • Every analysis is listed with version and date

  • Published under a public ethics policy

Open SourceadvancedLong-running project

Riemann

ClojureStream ProcessingMonitoring

A network event stream processing system for monitoring, written in Clojure. His about page lists it first among his work.

Shows infrastructure-building range beyond testing other people's systems.

  • Event-stream model for monitoring

  • Maintained under its own GitHub organization

Ready to build your portfolio?

Follow the Backend Developer roadmap — skills, projects, and timeline to get hired.

Backend Developer Roadmap