Technical leadership that writes code.
I lead the IT department at One Marketing Group: multi-account cloud architecture, CI/CD, and a team that builds instead of firefighting.
Contact →How I work
- Multi-account cloud architecture on AWS and OCI, with cost as a design constraint (FinOps).
- Hands-on technical decisions: I design, review PRs, deploy, and debug in production.
- CI/CD pipelines automated with GitHub Actions — boring, repeatable deploys.
- Zero-Trust security by design, not as a final patch.
- Metrics first: every infrastructure decision is justified by its operational return.
Results in the role
42% cloud cost reduction (AWS + OCI) through FinOps.
Legacy → static stack migration (Astro 6 + Cloudflare): 60% load time reduction.
53 Cloudflare zones managed: DNS, Workers, R2, SSL.
Sustained availability with distributed monitoring (UptimeRobot + Sentry).
Engineering leadership principles
- A leader who stops touching code loses technical judgment. I keep mine.
- Planned migrations, not firefighting.
- Fewer dependencies, more control: static components, edge, stateless.
- Small, automated teams outperform large, manual ones.