Marketers think in campaigns. Engineers think in systems. I think in both.
Twelve years at the intersection of marketing strategy, software engineering, and corporate operations. I architect scalable data engines and growth automation systems that neither a pure marketer nor a pure technologist could build alone — and the work is always forward.
Built at the intersection
of three worlds
Most people at Director-level came up through one lane — marketing, technology, or operations. I came up through all three simultaneously. That's not a generalist's path. It's a different kind of specialist.
I hold an M.Tech in Computer Science and an MBA from IIM Calcutta. I've written code, architected MarTech stacks, run $3M budgets, and led programmes at 10-million-user scale. At every company, I've been the person fluent in the engineering sprint and the board strategy session.
I don't carry campaigns like trophies. Every output — good or bad — is data. The question is always: what does the next iteration look like, and how do we run it better?
Strategy
Prod
Scale
Career
VoxxLife
iQuanti
Apollo 24|7
Early Career
One principle.
Every architecture.
That's not a philosophy I arrived at recently. It's what you develop when you've built growth engines at 10-million-user scale, managed $3M budgets, and led 30-person teams — and you've had to be honest about what worked and what didn't every single time.
The next chapter is VP of Digital Strategy, with a longer arc toward Chief Digital Officer — because that's the altitude where marketing, technology, and operations finally get to make decisions together.
Let's map a
real system.
If you are scaling an enterprise engine at the intersection of marketing infrastructure, AI automation, and institutional growth — whether a platform, a turnaround challenge, or an executive mandate — let's discuss the architecture.