Jul 2026 - Present
Finstar Financial Group
Senior Cloud InfraDevOps Engineer
A fintech lending group working in Vietnam, the Philippines, South Africa, India, Sri Lanka and Europe. Each product (risk engine, communication platform, API gateway, DWH, KYC/scoring) runs on its own AWS EKS cluster. I am responsible for the reference architecture: 25+ clusters in several regions. Everything is 100% Terraform plus the shared Helm library chart, with GitOps via ArgoCD and FluxCD. Nobody does manual work in the console.
- I am responsible for the AWS/EKS reference architecture: 25+ clusters in several regions, one per product or environment. All of them are 100% created with Terraform and deployed with GitOps (ArgoCD and FluxCD), with zero manual work in the console
- I set up a new production EKS cluster from scratch for the data warehouse team in Africa: networking, cross-account IAM, ArgoCD bootstrap. Then I added StarRocks with its load balancer, DNS and security groups
- I rolled out the Linkerd service mesh to new namespaces with Terraform in two regions, Africa and Europe
- FinOps: I set up Karpenter consolidation policies and right-sized the node classes. Compute costs stay flat, even though we now have more than 25 clusters
- I added graceful shutdown to the shared Helm library chart (terminationGracePeriodSeconds and lifecycle hooks). It now ships to 10+ clusters. I documented it in the platform guides on autoscaling, RBAC, secrets and jobs that every dev team works from
- I built and maintain an internal Kubernetes dashboard (FastAPI + vanilla JS): workloads, RBAC, real disk usage, ingress health checks. Dev teams use it every day instead of kubectl