Cloud network engineer with 3+ years designing and operating multi-region Azure networks for KAF Digital Bank, a BNM RMiT-regulated Islamic digital bank — from intern to team lead.
I started in networking — a Computer Science degree in Computer Networks & Security, a CCNA, and a habit of thinking in packets, routes, and failure domains. That lens followed me into the cloud.
For 3+ years I've designed and operated multi-region Azure network infrastructure for a BNM RMiT-regulated Islamic digital bank. I authored the network security architecture behind the bank's licensing review, designed its Azure Virtual WAN estate connecting core banking and national payment rails, and grew from intern to team lead along the way.
I'd rather go deep on the network than manage from a distance — which is why the next step I'm looking for is a senior network engineering role.
Built proofs of concept with the Cloud Engineer for VNets, VPN Gateway, Private DNS Zones, Application Gateway and API Management ahead of the landing zone build, and helped establish the Azure Backup and Recovery Services Vaults that later carried DR and RMiT retention.
Designed the bank's first landing zone connectivity stack, linking core banking SaaS to national payment systems and partner networks, and replaced self-managed domain controllers with Entra Domain Services so legacy LDAP workloads kept working.
Moved the estate onto Azure Virtual WAN with Routing Intent, segmented remote access per department with P2S user groups, codified hardening in an ADR enforced through Azure Policy, and is modernising storage onto Blob. DR is proven in regular live failover drills with a 1-hour RTO.
The depth grew first, then the breadth followed. As an intern, the platform meant proofs of concept — VNets, VPN Gateway, Private DNS Zones, Application Gateway and API Management — built alongside the Cloud Engineer before the landing zone existed, on top of a networking foundation he already carried in from his CCNA. Two threads started there and never stopped: the managed file transfer platform that moves files between the bank and its partners, and the Backup and Recovery Services Vaults that later became the base for DR and RMiT retention.
As Executive, those proofs of concept became the real thing: the bank's first landing zone connectivity stack, linking core banking SaaS to national payment systems and partner networks. Identity grew up too — privileged access was strengthened ahead of go-live with Azure PIM, RBAC and SSO across 150+ identities, and self-managed domain controllers gave way to Entra Domain Services.
As Lead, the platform he built is being rebuilt properly. The first landing zone evolved into a Virtual WAN estate with Routing Intent and centralised firewall policy; remote access is segmented per department through P2S user groups; hardening is written down as an ADR and enforced through Azure Policy and a CIS-hardened golden image. Some of his own early decisions are being revisited on purpose, with file storage being modernised onto Blob. And the oldest thread is still being pulled tighter: the DR he helped build as an intern is now proven in regular live failover drills, with a 1-hour RTO against BNM's 2-hour mandate.
Designed the landing zone connecting external SaaS platforms (core banking, payments) and hybrid partner endpoints. The initial stack — VPN Gateway, Azure Firewall, SD-WAN NVA, Application Gateway, API Management, and VNets/routing — is the foundation that later evolved into the bank's Virtual WAN architecture.
Every change to the lab is a pull request. A plan job runs Terraform, lints, and classes the change by risk: low-risk merges itself, medium-risk needs an agent reviewer, high-risk needs me. Each apply snapshots the guests first, then runs Terraform and Ansible and verifies the result layer by layer. Nightly jobs catch drift and pending patches, and every runner signs in to OpenBao with its own AppRole.
A team of agents runs the lab through the same pipeline I do: a router that triages work, infra, config and network agents that can only open pull requests, a reviewer agent, and an SRE agent for incidents. They act through MCP servers for DevOps, Proxmox, SSH, UniFi and Prometheus. Anything marked protected (the host, CI, secrets, the agents themselves) is read-only to them. Prometheus and blackbox probes watch 37 targets.
A UDM Pro Max runs the zone firewall, WAN failover and per-network Proton VPN egress, and links at 10G to a USW Pro Max 24 doing L3 for the server zones. A USW Aggregation below the core carries 10G to the Proxmox host's 2×10G LACP guest trunk, the UNAS Pro and my workstation. Three UX7 access points hang off the core: one wired, one daisy-chained, one on mesh. Shared services runs an HA k3s cluster (three etcd servers behind a keepalived VIP, plus two workers), and Wi-Fi and IoT each get a pair of AdGuard resolvers.
Graduated with a 3.81 CGPA. Final year projects: a comparative study of XGBoost vs. Random Forest for zero-day malware classification (shipped as a Chrome extension), and a Flutter/Firebase study planner for live timetable clash detection.
Graduated with a 3.83 CGPA, including a 4.00 GPA in four semesters. Joined community programmes such as PERSIS, then helped organise an anti-drug awareness programme and an Arduino workshop for young children. As academic tutorship president, taught C and assembly to struggling students.