Senior DevOps & Platform Engineer · Kigali, Rwanda
Senior DevOps & Platform Engineer with 5+ years designing, automating, and operating cloud infrastructure across AWS and GCP. I own Infrastructure as Code (Terraform, Terragrunt), Kubernetes orchestration, CI/CD pipelines (GitHub Actions, GitLab CI, Argo CD), and observability — across fintech, data infrastructure, and AI platforms. Comfortable end-to-end: from provisioning and pipeline architecture to incident response and production support.
A platform earns its keep by giving teams paved roads — opinionated templates, IaC modules, and CI/CD pipelines that are the obvious default, not the only option. Lock-in breeds resentment; defaults that just work breed adoption.
If a developer has to file a ticket and wait, the platform has failed at its job. Onboarding time, environment lead time, and self-service completion rate are the metrics that matter — not how clever the underlying topology looks on a diagram.
Engineers are the customers. The backlog is sized by their pain, not by infrastructure purity. I track adoption, gather developer feedback, and prioritise the things that unblock teams — even when the unglamorous fix is the right one.
Regression safeguards, expanded test coverage, and acceptance-criteria validation aren't a phase — they're the contract. The system stays stable while features land.
Clear engineering docs, runbooks, and onboarding materials compound. They turn one engineer's context into the team's shared baseline.
Architecture should survive a cloud migration. Decisions favor portability, infrastructure-as-code, and Terraform modules with clean interface contracts over vendor lock-in.
From SQL-dialect compilers to API contracts to Terraform plans, tests guard the boundaries that fail loudly. Coverage is a means, not the goal.
Design, Product, and Infrastructure aren't downstream of engineering — they're how delivery actually happens. Build the workflow with them, not for them.
The best system is the one the next person can extend. Boring, predictable code beats a clever abstraction every time.
When rebuilding a system, the new code is driven by specs and observable behavior — never by reading the legacy source. That keeps inherited bugs, hidden assumptions, and IP risk on the other side of the wall.
Logs, metrics, and traces aren't a nice-to-have — they're how the system warns you before users do. Mature observability is what turns 3am pages into morning tickets and shrinks MTTR by the only number that matters: actual incidents.
Hardening, TLS, least-privilege IAM, secrets management, and patched dependencies aren't bolted on at the end — they start at the kernel and shape every API contract. Treating security as a feature is paid for in incident reports.
A banking platform built for a client — production-adjacent fintech UX, account flows, and core money movement.
A SaaS platform that helps manufacturers manage their business and customers directly — invoicing, customer relationships, and product timeline tracking in one place.
A workflow automation experiment exploring scheduling and event-driven triggers.
Built backend for the Crop2Cash Marketplace — an agritech e-commerce platform helping smallholder farmers in Nigeria source seeds, fertilizers, and other inputs. Implemented chart APIs to surface live database data and introduced a programming system that streamlined integration with existing services.