Backend Developer

Brandur Leach Portfolio

Long-running blog, with articles back to 2013, by a backend engineer who spent five and a half years on Stripe's API and four years at Heroku, where he helped create the V3 API. Crunchy Data, Snowflake and Stainless came next. His July 2026 now page says he now works full-time on River, the Postgres-backed job queue for Go.

API DesignPostgreSQLDistributed SystemsTechnical Writing

Location

Austin

Companies

RiverStainlessSnowflakeCrunchy DataStripeHeroku

Skills

API DesignPostgreSQLDistributed SystemsTechnical Writing

Notable

  • Works on River, a Postgres-backed job queue for Go (5.7k GitHub stars)
  • Spent five and a half years at Stripe helping design, build and run its API
  • Helped create Heroku's V3 API during four years at Heroku
  • brandur.org is built by sorg, his own Go static site generator (526 GitHub stars)

What makes it work

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

1

API design writing grounded in production experience

His posts on API design, like "Implementing Stripe-like Idempotency Keys in Postgres" and "Why Doesn't Stripe Automatically Upgrade API Versions?", come directly from building and operating Stripe's and Heroku's public APIs, not from theorizing about REST in the abstract.

2

A dedicated "fragments" feed for short technical notes

Separating quick technical observations ("fragments") from long-form essays lets him publish frequently without diluting the archive of deep-dive posts — a structure worth copying for anyone maintaining a technical blog long-term.

3

A newsletter (Nanoglyph) that repackages the blog

Nanoglyph issues bundle links and editorial with his recent articles. Issue 052 (June 2026) folds in "The Minimum Viable Unit of Saleable Software", so readers who never check the site still get the long-form work. The newsletter page calls it "(aspirationally) weekly", which is an honest label.

What Backend Developers can take from this

Specific, actionable tips to apply to your own portfolio — no generic advice.

  • Write about the systems you actually operate, not systems you've only read about — production experience is what makes technical writing credible.

  • Separate short notes from long-form essays into different feeds so quick thoughts don't bury your deep-dive work.

  • Date your status updates. A now page stamped "last updated Jul 25, 2026" tells visitors exactly how current your job history is, even when an older about page lags behind.

Case studies

Brandur Leach sorts his output by cadence: tweet-sized atoms, short fragments, rare long articles and a daily photo sequence. The code sits one level down, where River and sorg run the job queue and the site itself.

Case StudyadvancedLong-form article (2017)

Implementing Stripe-like Idempotency Keys in Postgres

PostgreSQLRubyHTTP APIs

A long-form walkthrough of building Stripe-style idempotency keys on Postgres transactions. It is paired with "Using Atomic Transactions to Power an Idempotent API", part one of his series on getting data correctness from Postgres's transactional machinery.

Shows API-correctness thinking drawn from operating Stripe's public API, not from textbook REST.

  • Grounded in Stripe's production API design

  • Part of a series on transaction-backed API correctness

Projects

Open SourceadvancedOngoing since 2023

River: job queue for Go + Postgres

GoPostgreSQLTypeScript

A Postgres-backed background job queue for Go, introduced in his November 2023 article "River: a Fast, Robust Job Queue for Go + Postgres". It is built on transactional guarantees: a job is enqueued in the same transaction as the data it acts on.

Takes a production idea (Postgres as the queue) all the way to a maintained library with a business behind it.

  • Enqueueing is transactional, in the same Postgres transaction as the application data

  • Client libraries for Python and Ruby live under the same riverqueue org

ToolintermediateOngoing

sorg: the static site generator behind brandur.org

GoTailwind CSSAWS S3CloudFront

A custom Go executable that compiles brandur.org into static HTML, JS, CSS and images, which are stored on S3 and served through CloudFront. CI deploys it automatically when code lands on master.

His own publishing stack, running in production, doubles as a public Go codebase.

  • Serves articles, fragments, atoms, sequences and newsletters from one build

  • The about page documents the architecture and why he moved the CSS to Tailwind

Ready to build your portfolio?

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

Backend Developer Roadmap