DevOps & Cloud Infrastructure Engineer. 3+ yrs running production Kubernetes & AWS. Terraform, CI/CD, GitOps, observability. AWS & KCNA certified. Reliable, documented, cost-efficient infra.
I'm John, a DevOps and Cloud Infrastructure Engineer with 3+ years designing, automating, and operating production-grade Kubernetes and cloud-native systems. I help teams ship faster and keep their infrastructure reliable, secure, and cost-efficient — without the mess that usually comes with it.
Most of my work sits across three areas: building infrastructure properly the first time, automating the repetitive parts, and keeping things running once they're live.
What I do:
• Kubernetes on AWS (EKS) and DigitalOcean (DOKS) — cluster setup, scaling, RBAC, network policies, and security hardening
• Infrastructure as Code with Terraform, Helm, and Kustomize — reproducible, version-controlled environments across dev, staging, and production
• CI/CD pipelines with GitHub Actions, Jenkins, and GitLab — automated builds, manifest validation, and zero-downtime deployments
• GitOps delivery with ArgoCD using App-of-Apps and ApplicationSets for fully automated multi-environment rollouts
• Observability with Prometheus, Grafana, and Loki — custom dashboards, alerting rules, and faster incident response
• Secrets management with HashiCorp Vault and External Secrets Operator — centralised, auditable, and rotated properly
• AWS architecture — VPCs, ECS Fargate, RDS/Aurora, ALB/NLB, and multi-AZ high availability
• Databases — PostgreSQL, CloudNativePG, PgBouncer connection pooling, and backup/recovery strategies
Some results from past work: 99.9%+ system availability, 60% faster deployments through better CI/CD, and up to 30% lower cloud costs through right-sizing and automation. I've worked with clients across education, gaming, e-commerce, and enterprise, including international remote teams.
I'm AWS Certified Solutions Architect – Associate and KCNA (Kubernetes) certified, and I came into DevOps self-taught from a web development background — which means I care about the developer experience side of infrastructure, not just the ops side.
The way I work: clean, documented, and maintainable. I won't hand you a black box you can't touch after I leave. Whether you need a one-off fix, a full cloud setup, or ongoing reliability support, I'll make sure it's something your team can actually own going forward.
If you're building something and want the infrastructure done right, let's talk.
Work Terms
Availability & Communication
I'm available for both one-off projects and ongoing engagements. I typically respond within a few hours during business hours (GMT+3, Nairobi) and keep close overlap with UK, EU, and US-East timezones. I'll keep you updated regularly — no going quiet mid-project.
How I Work
I start by understanding what you're actually trying to achieve, not just the ticket in front of me. For larger work, I'll agree on clear milestones so you can see progress and we stay aligned. Everything I deliver is documented, so your team can maintain it after handover.
Payment
I work on an hourly or fixed-project basis depending on scope. For larger projects, I prefer milestone-based payments through Guru SafePay so we're both protected. I'm happy to discuss the structure that works best for your project.
Revisions & Support
I want the work to actually be right, so reasonable revisions within the agreed scope are included. For infrastructure work specifically, I'll walk you through what I've built and provide runbooks or documentation so nothing is a mystery.
Scope
If requirements grow beyond what we originally agreed, I'll flag it early and we'll adjust together rather than surprising you later. No scope creep, no surprise invoices.
Let's build something reliable.