DevOps Engineer specialising inAgentic DevOps Workflows

I build AI-driven infrastructure systems that deliver faster, safer, and with less toil. Engineering teams spend time on product, not pipelines.

See My Work Read My Story

Approach

How I Think About Agentic DevOps

Traditional DevOps: an engineer writes Terraform, runs a plan, checks the output, applies it, monitors for errors, and repeats.

Agentic DevOps: I follow the Gather → Act → Verify method. The AI reads the Jira ticket to gather facts, understands the infrastructure context, acts by writing the Terraform, checks it against security rules, reviews the cost estimate, and asks me to approve and verify before it applies. I'm not removed from the process but elevated above it.

Context before code

Before an AI agent writes a single line, it needs to understand the full picture. CLAUDE.md is the briefing document I write for every project: architecture, conventions, security rules, service ports, everything. An agent without context is just autocomplete.

Specialised agents, not one agent doing everything

I run subagents with isolated roles. A security auditor that only reads. A Terraform writer with write access. A cost optimizer that reviews spend. Each one knows its job and stays in its lane.

Safety is not optional

Every agentic workflow I build has three layers of protection: a prompt guard that catches destructive intent before reasoning begins, a pre-execution guard that blocks dangerous commands, and a post-execution logger that timestamps every infrastructure action. SAY → DO → LOG.

Projects

Things I've Built

AI Infrastructure

Agentic DevOps with Claude Code

I wanted to know what it felt like to let an AI agent do the infrastructure work while I supervised.

So I built the whole system. CLAUDE.md for project memory. Skills for on-demand execution — /scaffold-terraform, /tf-plan, /tf-apply, /deploy. Subagents for specialised roles. MCP servers for live AWS and Terraform awareness. Safety hooks so nothing destructive could happen without my approval.

Then I gave the agent a task: deploy a live website to S3 and CloudFront. It planned, it applied, it deployed. I reviewed and approved at each stage.

It worked. And it changed how I see this profession.

View Repo

Agentic Rebuild

DevOps with Claude Code: PetClinic on EKS

I'm taking the same application I deployed with a team — and rebuilding it alone. But my crew this time is AI.

Five MCP servers: Terraform, AWS, Cost Estimator, Library Docs, and Jira Integration. Two repositories with clear separation — the app repo is read-only, the infra repo is mine to build. Domain-specific rules for Terraform, Kubernetes, Helm, ArgoCD, and pipelines. Jira-driven development where Claude reads the epic acceptance criteria and builds against them.

Full observability. Security hardening throughout.

Platform Repo App Repo

Team Project

Spring PetClinic on AWS EKS

An 11-person team. 8 Spring Boot microservices. Two sprints. I was the Team Lead and Kubernetes Engineer.

I wrote the Kubernetes manifest files, managed namespaces, ConfigMaps, Secrets, and Ingress. The team integrated AWS Secrets Manager via External Secrets Operator so nothing sensitive ever touched the codebase, wired up GitOps with ArgoCD, built the GitHub Actions CI/CD pipeline, and made the whole stack observable with Prometheus, Grafana, and Zipkin distributed tracing.

When it went live, it worked. That's the standard.

View Repo

AWS · Terraform

Three-Tier Book Review App on AWS

I built a full three-tier architecture on AWS — frontend, backend, database — provisioned entirely with IaC. Then I wrote a complete guide so anyone could follow the same path.

View Repo

Videos

Walkthroughs & Demos

Recorded walkthroughs of projects I've shipped — narrated end to end so you can see how the pieces actually fit together.

Scaling Spring PetClinic Microservices on AWS

A walkthrough of how the 8 Spring Boot microservices were deployed and scaled on AWS EKS.

Watch on Loom

Deploying Portfolio Website on AWS

End-to-end deployment of a portfolio site on AWS — infrastructure, delivery, and the moving parts in between.

Watch on Loom

Writing

Things I've Written

I write when I learn something worth sharing. Here are three that best represent where my head is at.

Medium

Agentic DevOps: Less Writing Infrastructure Code, More Designing AI-Driven Delivery Systems

"What if your infrastructure wrote itself? I built the system that does."

Read article Medium

Kubernetes Health Probes: Stop Assuming Your Pods Are Fine

"Your pod says it's running. It's lying. Here's how to catch it."

Read article Hashnode

We Deployed 8 Microservices to AWS EKS as a Team — Here's What Actually Happened

"Eleven people. Eight services. Two sprints. Here's what actually happened."

Read article

Read All Articles

About

The Story

I started DevOps breaking things on Linux, debugging pipelines at odd hours, reading AWS documentation until things finally clicked. I did the fundamentals properly. Terraform. Kubernetes. Docker. CI/CD. Observability. I didn't skip steps.

Then I led an 11-person team deploying 8 Spring Boot microservices to AWS EKS. I wrote the Kubernetes manifests, managed namespaces, ConfigMaps, Secrets, and Ingress. I was the one making decisions when things broke.

Around the same time, I was selected as a DevOps Facilitator for Build With Oyo, an Oyo State Government-backed programme to train the next generation of tech talent in Nigeria. I taught students who were just starting out. Watching them go from confused to confident was something I was proud to be part of. I was also recognised as Champion of the Week in my cohort for completing four major AWS deployments in seven days.

Then something shifted in how I think about this profession.

The most valuable engineers aren't the ones who write the most code. They're the ones who design systems that write code for them. That's what pulled me into Agentic AI DevOps. Not as a trend. As a direction.

That's where I am now. And I'm just getting started.

Contact

Let's Talk

I'm open to fully remote DevOps and Cloud Engineer roles, as well as contract engagements. If you're building something that needs solid infrastructure, or you want to bring Agentic DevOps workflows into your team, I'm interested in that conversation.

Get In Touch Download CV