About

Architecture that survives contact with production
I’m an enterprise solutions architect with 10+ years designing secure platforms, cloud native architectures, governance frameworks and modernization strategies across government, banking, utilities and regulated environments: platforms at 3M+ users, 500K+ daily transactions and 10K+ peak concurrent scale. I work at the seam between enterprise strategy and technical execution: strategy documents that end in running platforms, decision records engineers actually follow, delivered with your team rather than around it.
What I bring
Architecture & Governance
TOGAF-informed strategy, formal ADRs, technology standards, migration governance, risk and financial management.
Cloud Native Modernization
Strangler fig migrations, domain driven microservices, Kubernetes/OpenShift/RKE2 platforms, HA and disaster recovery.
Security in Regulated Environments
Zero Trust, NIST/CIS/OWASP, threat modeling, data privacy, secure by design integration for government and banking.
Technical Leadership
Mentoring and knowledge transfer, stakeholder engagement, platform capability building across engineering teams.
How engagements run
Every engagement, whatever its size, follows the same discipline. Each stage has a defined output, so you always know what you’re paying for and what exists at the end of it.
1 · Understand
The business pressure behind the technology request.
Problem statement, constraints, success measures
2 · Assess
Current state with evidence, not folklore.
Readiness findings, risk register
3 · Architect
Target architecture and migration sequence, decided through ADRs.
Blueprint, ADR set, phased roadmap
4 · Validate
Load, failover and security proof before traffic moves.
Validation plan with go/no-go criteria
5 · Implement
Delivery alongside your engineers.
Running platform, transferred capability
6 · Measure
Outcomes against the success measures.
Outcome report
Background
- Solutions Architect, Rwanda Revenue Authority (2026): the UNDP supported E-Tax modernization; monolith to microservices strategy for 3M+ users; 20+ domain services; Zero Trust; governance via formal ADRs; RKE2 + GitLab CI/CD proof of concept.
- Consulting Software Engineer, Clearpoint Consulting (2024 to 2025): containerization and CI/CD for banking and government; 40% deployment time reduction; 99.9% availability architectures; observability and security regimes.
- Software Engineer, Clearpoint Consulting (2020 to 2024): 5+ OpenShift platforms; TRIRIGA/Maximo HA/DR; enterprise integration; Oracle→MSSQL migration at 100% data integrity.
- Software Engineer, Trans Business Machines (2015 to 2019): IBM BSM monitoring for national revenue and power utilities; 99% uptime SLAs.
- BSc Business Information Systems, Middlesex University London, First Class Honours.
Professional philosophy
Principle over product
Solutions follow the underlying technology principle, not a vendor. Object storage is the need; any compatible service can meet it.
Value driven technology
No technology enters the stack without a clear, measurable business reason for being there.
Research led solutioning
Recommendations grounded in research and fitted to each organization’s context, never generic templates.
Enablement over dependency
Teams operate the platform independently once the engagement ends. Knowledge transfer is a deliverable, not a side effect.
Pragmatic modernization
Wrap, extend or surgically replace: never rip and replace a working system just because it is old.
Guardrails, not gates
Governance as automated enablement in the path of work, instead of approval queues that people route around.
Simplicity by design
Deliberate push back on complexity drift: less technical debt, fewer redundant systems, long term maintainability.
Secure and open by design
Security built in from the start; open source and open standards first, reducing cost and lock-in.