Senior Cloud InfraDevOps Engineer
Fintech lending group live in Vietnam, the Philippines, South Africa, India, Sri Lanka and Europe — each product (risk engine, communication platform, API gateway, DWH, KYC/scoring) on its own AWS EKS cluster. Own the reference architecture across 6 AWS accounts, 5 regions and 25 clusters — 100% Terraform + the shared Helm library chart, GitOps via ArgoCD and FluxCD, no manual console work.
- Own the AWS/EKS reference architecture across 6 AWS accounts and 5 regions (Africa, Asia-Pacific, Europe) — 25 clusters, one per product/environment, 100% provisioned via Terraform, GitOps via ArgoCD and FluxCD, zero manual console work
- Built a new production EKS cluster from zero for the Africa DWH team — networking, cross-account IAM, ArgoCD bootstrap — then added StarRocks with its load balancer, DNS and security groups
- Rolled out the Linkerd service mesh to new namespaces via Terraform across two regions (Africa and Europe)
- FinOps: Karpenter consolidation policies and node-class rightsizing keep compute spend flat as the fleet grows past 25 clusters
- Added graceful shutdown to the shared Helm library chart — terminationGracePeriodSeconds + lifecycle hooks — shipping to 10+ clusters, documented in the platform's autoscaling/RBAC/secrets/jobs guides every dev team works from
- Built and maintain an internal Kubernetes dashboard (FastAPI + vanilla JS) — workloads, RBAC, real disk usage, ingress health checks — dev teams' daily driver instead of kubectl