About me

🚀 “From Circuits to Banking Platforms” – My Professional Story

I started my career in 2012 in an electronics embedded company. I was close to hardware, firmware, and real-world systems. That phase taught me discipline — systems must work reliably, not theoretically.

But I was curious about scale.

I moved to Zoho, where I transitioned into full-scale product engineering. There, I learned what it means to build for millions of users. I grew from an Android developer to a Mobile App Lead, understanding product thinking, performance optimization, and user experience at scale. Zoho shaped my engineering fundamentals — clean architecture, ownership mindset, and shipping production-grade software.

Then I moved to Blackhawk Network in the fintech and payments domain. That’s where I understood transactional integrity, distributed systems, and financial-grade reliability. Payments don’t tolerate mistakes. That phase strengthened my backend capabilities and system-level thinking.

Today at Maybank, I operate at a different altitude.

As a Technical Lead Engineer in the Customer Engagement Platform, I’m not just writing code — I’m driving strategic digital banking initiatives. I lead a team of 12 engineers and simultaneously drive multiple programs:

ML-based loan decisioning orchestration (SG & MY models)

SME digital onboarding initiatives

Push notification routing architecture

Backend integration for business banking products

Salesforce integration services

MAE ecosystem integrations

I design microservices architectures, drive Kafka-based event flows, ensure production stability, and mentor engineers — all while balancing delivery pressure.

What differentiates me is not just technical knowledge — it’s ownership.

When something breaks in production, I don’t look for blame — I look for patterns. When frameworks create cross-project risks, I escalate early. When delivery timelines compress, I restructure execution. When juniors hesitate, I mentor.

I’ve evolved from writing features… to building systems… to building teams.

After 14 years across embedded systems, SaaS, fintech, and banking, I now see engineering not as coding — but as decision-making under constraints.

And I’m still learning.