Maestro Interactive
Lead backend engineer. I own the services that take the hit on event day — the minute a broadcast goes live and the audience arrives all at once — and the quieter work of keeping the platform simple enough to operate.
I build and operate the infrastructure that keeps millions of concurrent viewers watching live sports: in Go and TypeScript, on Kubernetes, against the messy parts of production.
I'm a lead backend engineer at Maestro Interactive, where I work on the infrastructure behind live streaming for tier-one sports and media properties. The job is distributed systems under real load, and the kind of consolidation work that turns a collection of microservices back into something you can reason about.
I've been writing backend code since the mid-2000s. My instinct is to measure before I migrate, to delete before I add, and to treat infrastructure as something that has to earn its complexity. Most of what I ship is invisible from the outside; a few side projects are on GitHub.
Lead backend engineer. I own the services that take the hit on event day — the minute a broadcast goes live and the audience arrives all at once — and the quieter work of keeping the platform simple enough to operate.
Backend engineering on much the same stack, for one of the biggest names in broadcast. Services, infrastructure, and the habits that come from operating under a live audience.
Go, TypeScript, Python, with a dash of Bash.
Kubernetes, GCP, Terraform. Comfortable elsewhere, not religious about it.
MongoDB at scale, PostgreSQL by choice, Redis, NATS.
I start from the problem, not the playbook. I'd rather remove a system than add one. When I'm wrong, I want to find out fast.