Senior software engineer. Ten years building backend systems and leading full-stack teams — from national banking infrastructure to e-commerce platforms and startups. Systems that don't fall over, wherever they run.
I get called in when a system is fragile, migrating, or already on fire — a startup's codebase after a founder exit, a national bank's reporting pipeline, an e-commerce platform under real transaction load. Ten years across fintech, banking, e-commerce, and agency work has taught me the same lesson every time: the win isn't a clever architecture diagram, it's a system so stable nobody remembers it was ever risky. I optimize what's slow, secure what's exposed, mentor the team that inherits it — as an engineer, tech lead, or architecture consultant — and move on to the next thing that needs stabilizing.
National incident reporting that held under bank-scale load
Problem: A shared, reliable reporting platform for 50+ commercial banks at national scale.
What I did: Fifty-plus banks depending on one reporting pipeline — lag and regulators notice. I split the monolith into Laravel/Spring Boot microservices, hunted the slow queries in MySQL and MS SQL Server, and got critical reports out 30% faster without losing a nine of uptime. Three juniors I mentored on it now own pieces of the system.
LaravelSpring BootJavaMicroservicesMySQLMS SQL Server
shipped — elken sdn. bhd., 2018–2019
AWS migration · −20% infra cost · −40% API response time
Migrated a legacy e-commerce/MLM platform to AWS without downtime
Problem: A monolithic e-commerce and MLM platform, aging infrastructure, thousands of active users, complex commission logic that couldn't afford to break mid-migration.
What I did: Built the new platform end-to-end on Laravel/Lumen with a Vue.js frontend, then migrated the legacy monolith to AWS with auto-scaling — cutting infrastructure costs 20%. Profiled and tuned the codebase and database until average API response time dropped 40%.
