I write and maintain the software that manages data planes for Astro, a managed Apache Airflow product. This involves everything from control plane API layer, to Temporal service workers interacting with Cloud APIs, to the manifests that run on the Kubernetes based data planes. This software maintains all infrastructure and manifests for ~400 Kubernetes clusters across 3 cloud providers supporting ~2400 Airflow deployments. I work in about 60% Go, 20% YAML manifests, and 20% various other IaC languages.

Hired on to help mature and scale their software systems. Company had a very immature software that has high market value, but not much engineering experience to be able to maintain and scale it. I started off by redesigning their EC2 hosted PHP monolith and various task runners into Python microservices on ECS and with Apache Airflow for task orchestration. I brought agile product management and engineering to the organization and was given leeway to hire and lead 3 additional engineers to bring the microservice based SaaS to MVP. To accomplish this, I built out a new AWS multi-account architecture using Terraform and ECS as well as all new build and deployment automation. I maintained a focus on keeping the systems and designs simple and abstracting complexity away from the tools.

Member on a team of 3 responsible for scaling and maintaining 3 EKS clusters, including all build, deployment, monitoring, and alerting systems for applications deployed on them. I was brought in to the company for expertise in AWS and Terraform. I built out continuous integration patterns and pipelines for container and AWS Lambda workloads as well as designed automation and standards for building Kubernetes service templates using Jsonnet and Helm.

Brought on for AWS/Terraform expertise to build out a new service platform using Kubernetes and Rancher. Quickly built out a multi-account architecture and many modules. Left after a short time due to slow movement and a top down decision to use Azure over AWS.

Early engineer at Tempus. As a member of the DevOps team, I was assigned and worked with a product team that built a portal for doing clinical data abstraction augmented by NLP algorithms. All systems I touched had to maintain HIPAA compliance. I worked with both the engineering and data science side, with responsibility for all of their automation, infrastructure, and monitoring. Utilizing shared tools with the DevOps team, I built repeatable pipelines and patterns to enable the product team to build and deploy new services with ease. We were given leeway to explore anything in AWS and I tribute my breadth of AWS experience to Tempus.

SAVO was primarily a .NET shop. I started off as an embedded member of the mobile team. Shortly after starting, the company chose to migrate from on-prem to AWS. Given the timeline and the core infrastructure teams lack of experience, I was to build their automation for building out the AWS environment and deployment practices. My biggest contribution was my work on a Jenkins pipeline with policy logic to evaluate and conditionally apply Cloudformation templates.

Originaly brought on as an intern to be the sole developer of a .NET based SCADA system. I was hired full time as a Manufacturing Engineer to further integrate machines with data collection. I eventually moved over to the IT department and was given a management title to oversee IT for 13 production facilities.