Web3 Talent

I've spent the last 5+ years keeping blockchain infrastructure alive at scale first at Polygon Labs, now at Avail, which spun out of it. That arc took me from running a 500+ server Polygon PoS validator fleet (zero slashing, zero key compromises, staged hard forks with no downtime) to owning Avail's entire mainnet infrastructure end to end: validators, multi-chain RPC serving 1k–10k req/sec, indexers, and everything underneath, across AWS, DigitalOcean, Hetzner bare metal, and two on-prem racks.

What makes me good at this? I treat infrastructure as a product, not a ticket queue. At Avail I built the internal platform our product teams deploy through — 3 Kubernetes clusters I architected from scratch, self-service CI/CD, unified observability on SigNoz/OpenTelemetry so 80–90 services run without anyone filing a request to ops. That cut our MTTR by 60–70%. When a social-engineering attack compromised GitHub access, I contained it in hours, then built a one-click key rotation tool so the next incident takes minutes. When cloud bills got out of hand, I built a cost-visibility service, made the case with data, and led a full AWS migration that cut spend 50–60% with zero customer-facing downtime.

I've been on-call for mainnets for five years, so I have strong opinions about boring systems: everything through Terraform/Ansible GitOps, no standing production credentials, alerts mapped to real failure modes,runbooks that actually get read. Lately I've been building LLM-powered incident triage that auto-remediates the fixable stuff before a human wakes up.

I contribute merged PRs to Avail's open-source repos, I'm happiest on a small team with real ownership - where the infrastructure is a competitive advantage, not a cost center. I make systems boring so teams can move fast