Lagos, Nigeria | LinkedIn | Blog | Email
I build backend services and infrastructure labs that are easy to verify: CI/CD pipelines, AWS EC2 release automation, Dockerized IT support systems, and observable FastAPI services.
Open to DevOps Engineer, IT Support / Systems, and Backend Infrastructure roles.
| Capability | Proof to Review |
|---|---|
| CI/CD release automation | EC2 release pipeline with Node 22/24 build/test gates, controlled manual/tag deploy, PM2 reload, rollback script, and scheduled health checks |
| Backend reliability | API Reliability Suite with auth, rate limiting, readiness checks, Prometheus/Grafana/Jaeger, and circuit-breaker fallback |
| Container pipeline quality gates | GitHub Actions CI/CD demo with Node matrix tests, ESLint, Trivy SARIF, Docker Buildx, and GHCR publishing |
| IT systems operations | GLPI ticketing system with Docker Compose, MariaDB, persistent volumes, ITSM workflow notes, and a documented implementation write-up |
| Infrastructure breadth | DevOps labs covering Linux, AWS, Docker, Kubernetes, Terraform, Ansible, Prometheus, Grafana, and capstone deployments |
| Project | What It Demonstrates | Evidence Status |
|---|---|---|
| API Reliability Suite | FastAPI service with JWT auth, refresh-token rotation, rate limiting, readiness checks, structured logs, Prometheus metrics, Grafana dashboards, Jaeger tracing, and Redis-backed fallback behavior | Passing CI, Security, and Docs runs; load-test report, Grafana, and AI-debug screenshots |
| EC2 Release Pipeline | GitHub Actions workflow that tests a Node/Express app on Node 22/24, deploys to EC2 from a manual or pushed v* tag, reloads with PM2, and keeps rollback logic in scripts/deploy.sh |
Passing CI matrix run, deploy script, and scheduled health-check workflow; live EC2 deploy evidence still needs to be captured |
| Container CI/CD Pipeline | Node.js pipeline with Node 22/24 tests, linting, Trivy SARIF upload, Docker Buildx, GHCR image publishing, and simulated staging/production rollout steps | Passing GitHub Actions workflow; real deployment target still needs to be connected |
| GLPI Helpdesk Lab | Self-hosted ITSM/helpdesk lab using GLPI, MariaDB, Docker Compose, named volumes, internal-only database networking, ticket categories, SLA policy notes, and support roles | Compose file, operations runbook, backup/restore/smoke-test scripts, and implementation write-up; copy redacted screenshots into the repo next |
| DevOps Labs | Training portfolio with curated evidence paths for AWS HA WordPress, e-commerce CI/CD, Terraform modules, Ansible playbooks, and observability labs | Root README now separates implementation evidence from gaps; best screenshots, run links, and dashboard exports should be promoted next |
| Skill Area | Projects |
|---|---|
| GitHub Actions, CI/CD, release automation | github-actions-ec2-pipeline, github-actions-cicd-demo |
| AWS, EC2, IAM, deployment operations | github-actions-ec2-pipeline, devops-labs |
| Docker and service deployment | glpi-ticketing-system, github-actions-cicd-demo, api-reliability-suite |
| Monitoring and observability | api-reliability-suite, devops-labs |
| Linux and systems administration | devops-labs, glpi-ticketing-system |
| Backend infrastructure | api-reliability-suite, github-actions-ec2-pipeline |
I keep the pinned portfolio small and evidence-based. Training projects are labeled as labs, simulated deployments are called out as simulations, and every major project should include at least one reviewable artifact: workflow run, screenshot, log output, dashboard, load-test result, or deployment note.
- GLPI helpdesk implementation - ITSM setup, web server troubleshooting, roles, assets, tickets, SLA notes, and reporting.
- dev.to/darestack - notes on DevOps, Linux, backend reliability, and hands-on infrastructure projects.