Available for new work
I design and ship distributed services, APIs and data pipelines. Ten years turning ambiguous requirements into infrastructure that holds under real traffic.
01 · About
I started out writing scripts to automate my own work and never really stopped. Today I lead backend work on systems where downtime is measured in revenue: payments, logistics, and high-volume event ingestion.
My bias is toward simple, observable architecture. Fewer moving parts, clear ownership boundaries, and instrumentation you can actually trust at 3am. I like problems where the answer is a design decision, not a library.
02 · Selected work
Replaced a nightly batch job with a streaming pipeline handling 40M events per day. Cut end-to-end latency from 6 hours to under 2 seconds and removed the single point of failure that caused two outages the year before.
Designed and shipped a versioned public API with contract tests, generated SDKs and a deprecation policy. Grew from 0 to 900 active integrations in the first year without a single breaking change.
Introduced structured tracing and SLO-based alerting across 30 services. Alert noise dropped 84% and mean time to resolution went from 47 to 12 minutes.
A lightweight Postgres-backed job queue with exactly-once semantics and no extra infrastructure. Used in production by several teams and a few companies I have never met.
03 · Toolbox
04 · Contact
I am open to backend and platform roles, and to short consulting engagements on reliability and data architecture.