I started my career as a Network Engineer and Systems Administrator — managing Linux environments, physical switches, and on-premise servers long before "the cloud" was a common phrase. That foundation gave me a way of thinking about infrastructure that most cloud-native engineers never develop: understanding what is actually happening at every layer of the stack.
Over time I moved into software development, writing backend services and automation tooling in Python, Go, and others. That stretch taught me how engineers think and what they need from the infrastructure running under them. It changed how I communicate and how I design systems.
Today I work as a Cloud Engineer and SRE, bridging development and operations. I help teams migrate to AWS, harden their architecture, and stop hemorrhaging money on cloud spend they never intended to run.
Whether you need a cloud architecture review, a cost audit, or someone to embed with your team on an ongoing basis let's talk.