Maestro Interactive
Lead backend engineer. Live streaming infrastructure for major sports and media clients. Go, Kubernetes, GCP, MongoDB. Scaling to millions of concurrent viewers during live events.
I build and operate infrastructure that keeps millions of concurrent viewers connected to 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 Go and TypeScript services, distributed systems, MongoDB 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 for roughly twenty years. 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 lives behind the scenes. A few explorations live on GitHub.
Lead backend engineer. Live streaming infrastructure for major sports and media clients. Go, Kubernetes, GCP, MongoDB. Scaling to millions of concurrent viewers during live events.
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.