Technical Architect | Cloud Platform & Site Reliability Engineering | AWS | Azure | Kubernetes | OpenShift | Terraform

I design, automate and operate secure cloud platforms for large, regulated environments. My work sits at the intersection of cloud architecture, Linux engineering, Kubernetes platform operations, observability, reliability and infrastructure automation.

I enjoy turning difficult operational problems into repeatable engineering systems: infrastructure as code, safe automation, useful telemetry, clear runbooks and architecture decisions that balance reliability, security and cost.

• Production Platform Architecture and Reliability — a sanitized walkthrough of a four-cluster primary/DR platform supporting 5,000+ microservices and 1M+ daily transactions. It covers my personal ownership, architecture decisions, alternatives and trade-offs, failure behaviour, deterministic validation, incident remediation and recovery engineering.
• Role-Aware Oracle Data Guard Failover for Azure Data Factory — a sanitized production-style design that replaced manual DNS/DNAT failover with fail-closed HAProxy routing driven by Oracle database role, managed identity, Key Vault, systemd automation and service-aware Azure Load Balancer health checks.

• Cloud platforms: AWS and Microsoft Azure architecture, networking, security, governance and operations
• Containers: Kubernetes, Red Hat OpenShift, EKS, Helm, Docker and Podman
• Infrastructure as code: Terraform, ARM concepts, reusable modules and policy-aware deployments
• Automation and validation: Ansible Automation Platform, Python, Bash, PowerShell, deployment checks and diagnostic tooling
• Observability: OpenTelemetry, Prometheus, Grafana, Loki, Tempo, Mimir and cloud-native monitoring
• Linux and infrastructure: Red Hat Enterprise Linux, SUSE Linux, VMware, OpenStack, high availability and enterprise backup platforms
• Reliability: incident response, operational readiness, capacity management, disaster recovery, SLIs, SLOs and error budgets
• FinOps: cost allocation, trend analysis, architecture-cost trade-offs and optimization governance

1. Automate the repeatable, document the exceptional.
2. Prefer private, least-privilege designs by default.
3. Measure customer impact, not merely infrastructure activity.
4. Make failure modes explicit before production.
5. Treat cost as an engineering signal alongside reliability and security.
6. Build platforms that enable teams rather than creating operational dependency.

• Red Hat Certified Architect, AWS Solutions Architect Professional, Google Professional Cloud Architect, CKA, CKAD and Terraform Associate
• Fortinet NSE 7, Cisco CCNA, PRINCE2 and ITIL
• MSc Electrical Engineering and first-class BSc engineering degree
• Mandela Rhodes Scholar and Erasmus mobility alumnus

My academic work includes cloud-native 5G network-slice optimization, orchestration and metaheuristic resource allocation. See 5GSLICEOPTIMIZATION and 5GMETAHEURISTIC.

Every technical repository includes a GitHub Actions validation workflow. From a clone of this profile repository, all checks can be dispatched and reviewed with:

chmod +x scripts/run-portfolio-ci.sh
./scripts/run-portfolio-ci.sh dispatch
./scripts/run-portfolio-ci.sh status

The workflows validate Terraform, Ansible syntax, Kubernetes schemas, Prometheus rules, Python tests and Bash diagnostics without requiring access to private cloud environments.

The portfolio uses synthetic networks, placeholder identifiers and generated data. It contains no employer source code, credentials, customer information, production exports or confidential architecture.

I am particularly interested in international remote roles spanning technical architecture, platform engineering, cloud architecture, solutions engineering, DevOps and site reliability engineering.