I build systems
at scale.

MoEngage needed a unified way to manage messaging templates across 6 channels — Push, Email, SMS, In-App, On-Site, and WhatsApp. No central system existed. I built one from scratch.

The system handles folder organisation, REST APIs, rate-limiting, Redis caching, and DB optimisations. It sits in the critical path of all outbound & inbound messaging.

Marketers were writing raw Jinja syntax to personalise campaigns. Error rates were high, campaigns were breaking, and non-technical teams were blocked entirely.

I built a visual content builder that abstracts all template logic into a drag-and-drop UI — generating correct Jinja under the hood automatically.

Enterprise clients were sending campaigns to their entire audience — millions of users — when the goal was a controlled rollout. No cap mechanism existed.

I designed dynamic audience capping enforced at the campaign level, before any message is dispatched.

Developers integrating with MoEngage Inform's transactional messaging (3B+ messages daily) had to deal with raw HTTP and auth flows. I designed and shipped a clean Python SDK to PyPI with proper error handling and versioned releases.

Also unified AWS and Azure deployments into a single CI/CD pipeline, cutting release overhead in half.