Staff Software Engineer at Google, previously at Microsoft and Disney+ Hotstar. My career has been centered on one problem: making large-scale infrastructure reliable, understandable, and boring in the best possible way.

I've built sovereign cloud environments for multiple nations, operated Kubernetes orchestration at 5,000-cluster scale, and run DNS services carrying billions of queries per day. The work that interests me most is where complexity has real consequences — where a bad design decision doesn't just slow you down, it takes down production.

What I optimize for:

• Reliability before impressiveness
• Systems that scale without becoming fragile
• Reducing operational toil without sacrificing observability
• Making complexity measurable and automatable

I trust systems that are calm at 3 a.m. more than systems that are exciting at 3 p.m.

Building Google Infrastructure to deliver compute, memory, GPUs and TPUs resources with the reliability of Google Cloud infrastructure.

These are highlights from my career. Most of this work was internal; where I have public work, it's linked directly.

Designed and operated the platform automating provisioning, deployment, and management across 5,000+ AKS clusters and 6.7M+ cores at peak scale. The system handled the full lifecycle: bootstrap, scheduling, upgrade orchestration, and failure recovery — with zero-touch operations as the target state.

Azure Kubernetes Go Container Orchestration Infrastructure Automation

Built sovereign cloud infrastructure for multiple nations from the ground up. Each environment required isolated networking, sovereign DNS, and compliance with strict data-residency regulations — all while maintaining operational parity with global Azure.

Azure Sovereign Cloud Networking DNS Compliance Infrastructure

Designed and operated mission-critical DNS services for sovereign cloud regions. The system handled billions of queries per day with five-nines availability requirements, strict latency SLAs, and no tolerance for data exfiltration across trust boundaries.

Azure DNS Distributed Systems Reliability Engineering Observability

I'm most likely to contribute to or collaborate on:

• Infrastructure tooling that reduces manual operational toil
• Observability and tracing systems for cloud-native environments
• Kubernetes ecosystem tooling — especially lifecycle and scheduling
• DNS and networking utilities for distributed systems

If you're building something ambitious in cloud infrastructure, platform engineering, or distributed systems, reach out.

Beyond engineering, the subjects I keep coming back to:

DNS at scale · Kubernetes orchestration · Sovereign cloud design · Reliability engineering · Distributed systems internals · Platform engineering