Product Manager

I turn operational chaos into products people rely on.

At CIRRANTIC, I help turn EV charging data into products used across Google Maps, Apple Maps, and other mobility platforms, part of an ecosystem reaching 30M+ EV drivers.

Read my CVEmail me
Previously
  • EnBW
  • 1&1 Mail & Media
  • Aquatherm Engineering
How I got here

01 · The evolution

Every role changed how I think.

Engineering consultancy, then customer experience, then energy, then e-mobility.

2018–2021

Aquatherm Engineering Consultants

  • Design Engineer, Control & Instrumentation
  • Chennai

What it takes to get a complex technical system built, specified and signed off.

Control and instrumentation for 10+ thermal, hydro and solar power plant projects across three continents. I prepared the technical specifications, supported bid analysis and feasibility studies, and followed equipment through factory and site acceptance testing against ISO/IEC requirements.

  • AutoCAD
  • Instrumentation
  • Process engineering
Technology
2021–2022

1&1 Mail & Media

  • Working Student, Customer Experience
  • Germany

How to hear what a customer needs underneath what they ask for.

Read support KPIs, customer queries and bug trends across GMX and mail.com, and turned the patterns in them into product improvements and feature validation for the support, product and engineering teams.

  • Jira
  • KPI reporting
  • Product management
Business
2022–2024

EnBW Energie Baden-Württemberg

  • Working Student + Master Thesis

How energy data becomes a decision somebody has to stand behind.

A master thesis on charging-infrastructure strategy: modelling how EV charging behaves before deciding what to build for it. Alongside it, Power BI applications for the IT trading team.

  • Python
  • Gurobi
  • Power BI
TechnologyOperations
2024–presentNow

CIRRANTIC

  • E-mobility Charging Content & Product Manager
Connectors on the platform
1.5M+
Data updates a day
2.1M+

How the operational detail decides what the product should be.

I joined to improve charging data and now work on the products behind it: tariff data, the ACM and Charging Radar tools, and the requirements that reach our engineering teams.

  • MySQL
  • Tariff & station data
  • Product discovery
OperationsBusiness

The convergence

technically sound

operationally practical

valuable to customers

Miss one of the three and the product stalls. Lining all three up at once is the job.

02 · How I work

Where I'm most useful.

01

Early, ambiguous, ownerless problems

The problems I like are the ones nobody has framed yet. My first job on a vague one is to give it a shape other people can argue with, then to kill the versions that do not survive the evidence. Two of my own ideas died that way before I built anything.

02

The gap between engineering and the business

I wrote control and instrumentation specs for more than two years before I ever wrote a product requirement, then spent a year reading support tickets to find what customers meant rather than what they typed. Having sat on both sides, I translate before a misunderstanding hardens.

03

Systems with too many moving parts

In a power plant a wrong assumption does not surface at the design review, it surfaces at commissioning. Over two years of that taught me to understand how a system behaves before changing any part of it, and the habit came with me when I changed careers.

04

Operations that should be a product

Every team has work that only lives in one person's head: the corrections, the reconciliation, the checks nobody wrote down. At CIRRANTIC that work is tariff and charging data, and the job is to get it specced into modules before the person holding it moves on.

Off the clock

Chess is my favourite kind of problem: simple rules, absurd depth. If something catches my attention I usually end up reading too far into it, or building something small just to understand it. If you play, find me on Chess.com.