Seven years shipping infrastructure at scale — queues that don't drop messages, APIs that degrade gracefully, and dashboards nobody has to squint at during an incident.
I'm a backend engineer who spends most of my time in the unglamorous middle of a system: message brokers, retry logic, and the alerting that tells you something's wrong before a customer does.
Before that, I spent three years on a small team scaling a payments pipeline from thousands to millions of daily transactions, which is where I learned that most outages come from unlikely things happening at the same time.
Outside of work I mentor early-career engineers and contribute to a couple of open-source queueing libraries.