Work
I’m a cloud engineer and architect. DevSecOps first, CI/CD all the things.
How I default to working:
- Automate it, or it didn’t really happen
- Build the secure path early, not as a retrofit
- Fail fast, fail forward, keep improving the system
Now - TerraFlow Energy #
I help deliver TerraFlow Energy’s EMS (Electricity Management System) into customer environments. Every customer environment is a little different, so the interesting problem is rarely the software - it’s making delivery repeatable when the target keeps moving.
What that covers:
- Architecture and deployment strategy for customer-ready EMS environments
- CI/CD pipeline design and automation
- Security-first engineering across build, release, and operations
- Reliability, observability, and operational hardening
Before this #
Cloud SRE and architecture work across three industries that look nothing alike.
Oracle - Cloud SRE and architect.
Shell - Oil and gas.
Nike - Global footwear and apparel.
The through-line is the same in all of them: production systems people actually depend on, where being careless has a real cost. Energy, oil and gas, and retail have completely different regulatory shapes and failure modes, and all three punish teams that treat delivery as an afterthought.
How I work #
DevSecOps first. Security belongs in the delivery workflow from the start. Bolted on at the end, it just becomes the thing everyone routes around.
Automation over handoffs. Repeatable pipelines and infrastructure automation beat tribal knowledge and manual runbooks every time.
Learn-forward. When something breaks, the useful questions are about fast feedback and clear ownership - not who to blame, and not which old habit to revert to.
What I build #
- Cloud platform patterns for scalable delivery
- CI/CD pipelines that support frequent, safe releases
- Secure-by-default workflows and guardrails
- Deployment playbooks that hold up in production