Design for failure, operate for clarity
Things break. Brokers drop, jobs stall, nodes run out of memory. I build systems that degrade gracefully and make their failures visible, instead of quietly hoping they won't.
I have 9+ years building and running cloud-native distributed systems and internal platforms, mostly in Go and Python on AWS, Azure, and Google Cloud.
At ServiceNow, I own the technical vision and governance for enterprise platform APIs and agentic workflows, standardizing RBAC, observability, and rate-limiting across distributed engineering teams. Previously at Thoughtworks, I led architecture and cloud infrastructure for Singapore’s national health platform—delivering high-resilience systems for 500,000 citizens, zero-trust Kubernetes clusters, and streaming platforms processing 2M+ CDC events daily.
A few principles I've settled on after nine years of building and running distributed systems.
Things break. Brokers drop, jobs stall, nodes run out of memory. I build systems that degrade gracefully and make their failures visible, instead of quietly hoping they won't.
When many teams share one platform, contracts, access control, and observability aren't overhead. They're the product. I'd rather build that in from the start than bolt it on later.
Efficiency is a design constraint, not a quarterly cleanup. Cost, latency, and reliability are decisions you make up front, because that's when they're still cheap to change.
I reach for proven tools and keep novelty off the critical path. The interesting complexity belongs in the problem I'm solving, not in the stack that has to hold up at 3 a.m.
Notes on the distributed platforms, streaming systems, and infrastructure I've built for enterprise production.
I designed the internal platform API around Snowflake Cortex Analyst and Agent and run it as a shared, governed service for ~8 internal engineering teams. That covers API contracts, role-based access control, rate limiting, and observability, plus the integration work to wire it into enterprise AI, agentic workflows, and Microsoft Teams.
I ran the infrastructure side of Singapore's national health data platform, which serves ~500,000 citizens. The biggest change was moving to a hub-and-spoke Azure Databricks workspace topology, which removed cross-workspace compute redundancy and isolated sensitive healthcare workloads. I also tracked down memory and partition problems that were destabilizing the HDInsight Spark clusters.
Built and ran an event-driven Change Data Capture (CDC) pipeline on an HDInsight Kafka cluster with Debezium connectors. It picks up transactional changes from the source databases as they happen and pushes them to downstream analytics engines and data catalogs, without adding lock contention on the primary OLTP tables.
Locked down production Kubernetes clusters with Calico network policies, isolating namespace traffic and shrinking the pod-to-pod attack surface. On the Daimler DataOps work, I built a standard Continuous Delivery for Machine Learning (CD4ML) pipeline with MLflow, DVC, and Jenkins so model training and deployments were reproducible and versioned.
Wrote a small, concurrent notification service in Go and gRPC for booking status changes and campaign alerts across the travel ad-tech services. I also automated provisioning on Google Cloud Platform so teams could spin up throwaway test environments whenever they needed one.
Nine years of building and running production systems across healthcare, ad-tech, and enterprise software.
Notes on distributed systems, event streaming, cloud architecture, and platform engineering.
What actually goes wrong running a 2M+ events/day CDC pipeline on HDInsight Kafka, and the trade-offs we settled on.
How we built a shared, multi-tenant API for LLMs and unstructured data that now serves 8+ teams and 50,000 requests a day.
Zero-trust microsegmentation in a regulated healthcare cluster, and what it did to the attack surface.
Certifications across Google Cloud and Microsoft Azure.
Tools and platforms I've used in production over the last nine years.
Conference presentations, internal knowledge forums, and engineering mentorship.
A talk on writing Airflow DAGs that survive failure: task retries, dependency design, and how to stop one bad task from taking down a pipeline.
Ran internal knowledge-sharing forums that grew to ~30 engineers, and gave talks on Docker, database sharding, and distributed systems basics.
Mentored 8+ engineers across ServiceNow, Thoughtworks, and BeautifulCode, most of whom moved into senior individual-contributor roles. B.Tech in Computer Science & Engineering.
Happy to talk about distributed systems, event streaming, cloud platform work, or senior engineering roles.