Moved payment retries from cron jobs to a Kafka pipeline. Fewer double charges, much faster refunds.
go · kafka · postgresSenior backend engineer · payments and infrastructure · 8 years
I build the parts of a product nobody notices until they break: payments, queues and the databases behind them. My last system moved $2B a year and paged me twice.
01 · Try to break it
This is a simplified version of a payments system I designed. Click any box to take it down and watch traffic route around it. Click again to bring it back.
02 · A year of commits
Hover a square.
03 · git log --oneline
Moved payment retries from cron jobs to a Kafka pipeline. Fewer double charges, much faster refunds.
go · kafka · postgresMoved 3TB of ledger data to a new database while it took live traffic. Nobody noticed, which was the point.
postgres · logical replicationRebuilt CI so a change reaches production in 9 minutes, with automatic rollback.
kubernetes · argo · terraformA small Go library other teams now use. 1,200 stars, and a very polite issue tracker.
go · redisHow I work
Write the runbook before the code. If I can't explain how it fails, I don't understand how it works.
About me
I'm open to senior or staff roles on infrastructure or payments teams, remote or in Austin. I care about on-call that doesn't burn people out and code reviews that teach.
Hey, I'm Sam. Tell me about the scariest part of your system. That's usually where I can help most.
A real voice note, recorded for this sample. On your webfolio, it's your own voice.Sam's design docs are the ones we use to teach new hires.engineering director
Calmest person on an incident call I've ever worked with.site reliability lead
He made me a better engineer in six months of code reviews.former mentee
sample references, written for this made-up engineer.
Remote first, happy to travel monthly. Austin for hybrid.
For short architecture reviews, yes.
Two weeks.