I design distributed systems that have to work at real scale — 5,700 requests per second, 44 million records a month, 1.8 million users getting personalized recommendations from 10 TB of health data. Over 20 years I've done that across Amazon, JPMorgan Chase, Safeway, and a handful of other demanding environments, mostly on AWS with Java Spring Boot and .NET Core.
The problems I find most interesting sit at the intersection of architecture and reliability: how do you build a platform that stays fast under variable load, recovers gracefully when things go wrong, and still lets teams ship without gating every release on an engineer? At Amazon Pharmacy that meant dynamic AppConfig-driven throttling and fully automated CDK pipelines. At JPMorgan Chase it meant streaming-based microservices and continuous delivery on a $1.6B revenue platform that previously shipped twice a year. At Safeway it meant replacing a vendor's rules engine entirely with an in-house SpEL-based platform so product owners could control personalization logic themselves.
My current focus is event-driven architecture, AWS-native infrastructure-as-code, and the reliability engineering layer — observability, autoscaling, idempotency, backpressure — that makes distributed systems actually trustworthy in production.
I write about performance engineering and .NET/AWS patterns at
https://ajitgoel.github.io/ Open to senior architecture and platform engineering roles, remote or hybrid.