Fullstack roots, cloud focus, and production ownership.
I started in product engineering, moved deeper into backend systems, and now focus on platform reliability: the delivery paths, cloud foundations, observability, and operational guardrails that help teams move faster without turning production into guesswork.
Certifications
Credentials that reflect hands-on investment in cloud architecture, Kubernetes operations, infrastructure automation, and delivery practice.
Certified
AWS Solutions Architect - Associate
Certified
AWS DevOps Engineer - Professional
Certified
Certified Kubernetes Administrator (CKA)
Certified
Terraform Associate
Certified
Google Cloud Engineer - Associate
Certified
Azure Administrator - Associate
Areas of Strength
Not tool collecting. The useful part is knowing which guardrails, signals, and automation make production safer to change.
Cloud foundations
I build AWS-first environments with predictable networking, tight IAM boundaries, and reusable patterns. The value is not more YAML; it is a foundation teams can trust under real traffic.
- AWS
- Networking
- IAM
- EKS
- Secrets
Delivery systems
I build CI/CD workflows with policy gates, artifact integrity, and clear promotion paths. Teams ship faster when pipelines are boring, explainable, and rollback-aware.
- Kubernetes
- Terraform
- CI/CD
- GitHub Actions
- ArgoCD
Production signal
I build observability into platforms from the start. SLOs, dashboards, runbooks, and alert hygiene matter because the hardest failures are often degraded, quiet, and only obvious to users.
- Prometheus
- Grafana
- SLOs
- Runbooks
- Observability
Backend and automation judgment
Fullstack roots shape how I make platform decisions. I automate repetitive work, use AI where it helps, and keep infrastructure reviewable enough for humans to own.
- Node.js
- TypeScript
- PostgreSQL
- APIs
- Scripting
Timeline
The path from product engineering into cloud platforms, reliability, and end-to-end ownership.
2018 - 2020
Fullstack engineering
Built product features end to end, worked close to users, and learned how delivery speed and technical clarity affect real teams.
- Frontend
- APIs
- Product delivery
2020 - 2022
Backend systems
Moved deeper into APIs, integrations, data flow, and service reliability, with more attention on deployment quality and production behavior.
- Services
- Data
- Reliability
2022 - 2024
Cloud and delivery systems
Shifted into infrastructure, CI/CD, and Kubernetes delivery, focusing on repeatable systems and change safety instead of one-off environment work.
- AWS
- Terraform
- Kubernetes
2024 - Present
Platform reliability focus
Concentrating on resilient platforms, observability, operational guardrails, and automation that keeps human ownership in the loop.
- Platform
- SRE
- Automation
Gallery
A collection of moments from speaking, teaching, and community events.
Recent Wins
A live snapshot of what's shipped, fixed, taught, and shown up for — across production systems, community work, and team moments.
Delivered cohort 3 of the Scratchcode engineering bootcamp
Ran the third cohort of the Scratchcode bootcamp — eight weeks of cloud, DevOps, and backend fundamentals with 18 students. Highest completion rate yet.
Impact
16 of 18 students completed the programme. 4 landed their first junior cloud or backend roles within 6 weeks of graduation.
Tightening EKS ingress health checks to make rollouts boring again
Reduced deployment friction by aligning ALB health checks, readiness behavior, and ingress expectations so rollout failures became faster to diagnose and less disruptive.
Impact
Turned a recurring ingress failure into a repeatable, low-drama diagnosis path with clearer rollout signals and faster recovery.
Cut EKS cluster costs by 34% without touching capacity
Identified and fixed a cluster cost problem caused by over-provisioned node groups and unset resource requests — without reducing actual workload capacity or changing application behaviour.
Impact
34% reduction in EC2 spend for the cluster. Freed up budget that funded two additional environments for the team.
Team offsite to Cape Coast — and why it mattered more than I expected
A two-day trip with the Scratchcode team to Cape Coast turned into one of the most useful alignment sessions we've had. A mix of work, history, and real conversations about where we're headed.
Impact
Came back with clearer personal goals, stronger team context, and a renewed sense of direction after months of heads-down building.