Two years shipping 0→1 systems in EV mobility — from a driver onboarding app to payout automation across four partner models — grounded in data, sharpened by the people who actually use it.
Four habits that show up in every project below.
Before I decide what a screen looks like, I want to know how the work actually happens — how a driver gets verified, how a payout gets approved. The interface follows from that, not the other way round.
Audit trails, role-based access, and clear approval logs aren't compliance overhead I add at the end. They're what makes finance, ops, and legal teams comfortable actually using what I build.
A process you can't measure is a process you're guessing about. Every workflow I've automated ships with a way to see, in real time, whether it's actually working.
Usability sessions with first-time drivers caught problems no spec review would have found. The person doing the task, not the stakeholder describing it, is the fastest way to find what's broken.
Four systems built end-to-end at Magenta EV Solutions, 2024–2026.
New drivers had no fast way to get verified and onto the road. Onboarding was slow and manual, which meant revenue-generating trips couldn't start — for the driver or for the business.
The product end-to-end: account setup, KYC, background verification, hub-aware vehicle selection, payment and deposit integration, and activation — from wireframes and PRD through launch.
Payouts were calculated manually across four different partner and client models — slow, error-prone, and quietly eroding trust with drivers and partners every time a number came out wrong.
Automating payout logic across all four models, plus the governance layer around it — approvals, audit trails, and access controls.
Operational and financial data lived in separate systems. Regional managers spent hours every week manually pulling numbers together before a business review could even start.
Tableau and Power BI dashboards, the SQL underneath them, and the consolidation of scattered data sources into one reporting layer.
Breakdowns and repairs were tracked over email. Nothing was accountable, nothing was timestamped, and no one could see the patterns behind repeated failures.
The ticketing workflow end-to-end: intake, escalation rules, notifications, and the analytics layer behind it.
I'm a Product Manager based in Bengaluru, working mostly in operations-heavy, data-rich environments — most recently EV mobility. Over the past two years I've owned six concurrent product initiatives at Magenta EV Solutions, from a driver onboarding app built from scratch to payout automation across four partner models.
My background is technical: an MCA, plus certifications in Google Project Management and applied data analysis. In practice that means I'm usually the person who can write the PRD, query the database, and sit in on a usability session — in the same week. While I was leading product, Magenta EV Solutions was recognized as Most Innovative Employer of the Year, 2025.