The engineer who replaces tribal knowledge with pipelines that enforce it — eight years building cloud and Kubernetes platforms that hold up under audit, not just under demo.
Senior DevOps & Cloud Automation Engineer. AWS, Kubernetes, Terraform, Ansible, GitLab CI/CD, and the policy gates that keep all of it honest.
Houston, TX — United StatesEight years across infrastructure as code, CI/CD, Kubernetes, automation controllers, Linux operations, and policy-as-code — building systems that reduce manual work and hold up under audit.
Automate the repeatable work instead of documenting manual steps forever.
Keep infrastructure and configuration separated by clear ownership boundaries.
Prefer private, least-privilege, auditable access over broad network exposure.
Make CI/CD the control plane for validation, approval, and rollback evidence.
Tools grouped by where they sit in the delivery path, not by how impressive they sound.
The delivery path I default to for governed infrastructure changes — every line below is a real control point, not a diagram for its own sake.
"Treat security and policy as part of the delivery path, not an afterthought."
Infrastructure, DevOps, and automation experience across banking, cloud technology delivery, and data services environments.
“Governed cloud automation for banking environments where reliability, auditability, and access control matter every day.”
At US Bank, I work on cloud automation and DevOps engineering for regulated infrastructure. The focus is practical: make AWS environments repeatable, keep changes visible, and turn security requirements into controls that run inside the delivery workflow instead of sitting outside it.
My work spans Terraform modules, GitLab pipelines, AWX and Ansible Automation Platform workflows, Kubernetes operations, private AWS access patterns, observability, and production support. I partner with platform, security, compliance, and application teams to keep infrastructure consistent across environments and easier to operate under change control.
“Moved teams away from hand-built environments and toward repeatable cloud delivery.”
At MUV Technologies, I supported cloud and automation work for application teams that needed faster, cleaner environment delivery. I helped provision AWS services, automate server configuration, and build deployment workflows that reduced manual release steps across development, test, and production environments.
The role covered a broad operational surface: infrastructure provisioning, CI/CD, Docker and Kubernetes support, Ansible and AWX-based operations, monitoring, scripting, backup checks, and deployment runbooks. It was the period where my work shifted from system administration into platform-style automation.
“The infrastructure foundation: servers, monitoring, access, change windows, and steady operations.”
At Grayradiant Data Services, I worked close to the infrastructure layer: Linux and Windows servers, virtualization support, patching, access management, monitoring, backups, and incident troubleshooting. The work required careful change handling and a clear understanding of how applications depended on the underlying environment.
I also began automating repetitive administration with scripts, scheduled jobs, templates, and documented procedures. That foundation shaped the way I now approach cloud work: standardize first, automate what repeats, and make operations easy to verify.
Modeled as an enterprise platform engineering structure — modules, live deployments, and governed pipelines, organized by ownership group.
Modernizing cloud infrastructure, building automation frameworks, or talking shop about platform engineering — always open to connecting.