Product Manager · Bengaluru, India

I turn operational chaos
into products people trust.

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.

20%
faster driver verification
30%
less manual payout processing
20%
faster operational reporting
15%
lift in product adoption
PRDs that ship SQL & analytics Payout automation Agile delivery KPI dashboards User research EV mobility 0→1 development Stakeholder management PRDs that ship SQL & analytics Payout automation Agile delivery KPI dashboards User research EV mobility 0→1 development Stakeholder management
01

How I think about product

Four habits that show up in every project below.

Start with the workflow, not the wireframe

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.

Trust is a feature

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.

Instrument what you ship

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.

Talk to the person doing the work

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.

02

Selected work

Four systems built end-to-end at Magenta EV Solutions, 2024–2026.

Rental & revenue-sharing · EV mobility

Driver onboarding app, built from scratch

The driver's journey
Sign up
→
↓
ID & KYC
→
↓
Background check
→
↓
Hub-aware vehicle match
→
↓
Payment & deposit
→
↓
Activated

The problem

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.

What I owned

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.

Key decisions

  • Ran usability sessions with first-time drivers before launch, and used what broke to redesign the flow rather than patch it afterward.
  • Brought Compliance and Legal in early so regulatory checks were built into the flow, not bolted on after the fact.
  • Made vehicle selection hub-aware, so drivers only ever saw vehicles they could realistically pick up nearby.
Role

Product Lead, end-to-end

Tools

Figma flows, JIRA, PRDs

20%

faster user verification cycle

Finance & operations · Multi-client models

Payroll and payout automation

The system
Model A
Model B
Model C
Model D
→
↓
Automated calculation engine
→
↓
Audit trail & role-based access
→
↓
Payout

The problem

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.

What I owned

Automating payout logic across all four models, plus the governance layer around it — approvals, audit trails, and access controls.

Key decisions

  • Automated the calculation logic itself, rather than adding manual double-checks — removing the error path instead of catching it later.
  • Built audit trails and role-based access before Finance asked for them, treating transparency as core rather than a compliance add-on.
  • Restricted sensitive payroll data to authorized roles only, closing a privacy gap the old email-based process never addressed.
Role

Product Owner

Tools

SQL, JIRA, workflow automation

30%

less manual processing time, calculation errors eliminated

Business intelligence · Cross-functional reporting

A single source of truth for KPIs

The pipeline
Ops data
Finance data
→
↓
Consolidated schema (SQL)
→
↓
Tableau & Power BI dashboards
→
↓
Automated KPI digests

The problem

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.

What I owned

Tableau and Power BI dashboards, the SQL underneath them, and the consolidation of scattered data sources into one reporting layer.

Key decisions

  • Fixed the data model first — consolidating sources into one schema — instead of layering dashboards on top of messy data.
  • Automated KPI email digests for regional managers, so most weeks they never had to open a dashboard to get their answer.
Role

Product Lead

Tools

SQL, Tableau, Power BI

20%

faster reporting, 15% less manual reporting effort

Fleet operations · Maintenance

Asset maintenance ticketing system

The ticket lifecycle
Breakdown reported
→
↓
Ticket created
→
↓
Auto-escalation by severity
→
↓
Resolved
→
↓
Logged for pattern analysis

The problem

Breakdowns and repairs were tracked over email. Nothing was accountable, nothing was timestamped, and no one could see the patterns behind repeated failures.

What I owned

The ticketing workflow end-to-end: intake, escalation rules, notifications, and the analytics layer behind it.

Key decisions

  • Built custom escalation rules so high-impact breakdowns notified the right team automatically, instead of relying on someone noticing an email.
  • Added a time-to-resolution and failure-pattern analytics layer from day one, so the system could inform maintenance planning — not just log tickets.
Role

Product Owner

Tools

JIRA, workflow design, analytics

20%

faster breakdown resolution tracking

03

About

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.

Education

Master of Computer Applications
NIST, Brahmapur — 2022
Bachelor of Computer Applications
Utkal University — 2020

Certifications

Google Project Management Certificate
Google — 2024
Master Data Analysis — Python, SQL, Tableau, Power BI, AWS, ETL
Udemy — 2025

Skills

Product Strategy0-to-1 DevelopmentPRDs & User Stories Agile/ScrumStakeholder ManagementUX Collaboration SQLPythonTableauPower BIAdvanced Excel JIRAGitProcess Automation
04
Working on something ambiguous and operations-heavy? I'd like to hear about it.