I focus on the architecture and evolution of Kubernetes-based cloud platforms: how they are deployed, configured, secured, operated and exposed to the teams that build on top of them.
My recent work has been around SaaS and Bring Your Own Cloud environments across AWS and Google Cloud. That includes infrastructure automation, platform defaults, security controls, reliability practices and the operational routines needed to keep those systems understandable over time.
I usually work where architectural decisions meet day-to-day operations. I care about making infrastructure repeatable, but also about making the reasoning behind it clear: why defaults exist, how environments should be provisioned, where responsibilities sit, and what trade-offs teams need to understand before depending on a platform.
Earlier in my career I worked across DevOps consulting, technical training and community organizing. That background still shapes how I approach platform engineering. A platform is not only a technical system; it is also documentation, defaults, support paths, operational habits and shared language between teams.
I tend to be most useful in roles where infrastructure, product engineering, reliability and security overlap, especially when the work involves turning scattered operational knowledge into a platform that other teams can use with confidence.