Jaguar Land Rover · EV charging & interoperability
Own the journey. Align the ecosystem.
Owning the Plug & Charge backend roadmap and aligning vehicle, cloud and charging partners around one driver experience.
01 / problem
The problem to solve
Automatic public charging depended on JLR, our charging-platform partner DCS, and a chain of energy-tariff and identity-verification providers all working together as one service. Each integration could succeed technically while the overall driver experience still failed, making organisational boundaries a poor definition of the product.
02 / decision
The decision
I owned the backend product roadmap for JLR’s Plug & Charge capability, setting priorities for Hubject integration, certificate exchange and validation, vehicle authentication and backend arbitration. I used the end-to-end driver journey to guide these choices: a driver should be able to plug in and begin charging with minimal friction.
03 / approach
How I approached it
I translated the roadmap into prioritised work across backend services, vehicle systems and external charging ecosystem partners, including Hubject integration. With engineering and security colleagues, I balanced new capabilities with API integration, certificate validation, authentication, integration testing, technical debt and production readiness. I kept partner dependencies and delivery responsibilities visible so the backend work supported a coherent customer experience.
04 / outcome
What changed
The capability is live: at a compatible public Plug & Charge station, the driver can plug in and charging can begin automatically without an app or RFID card. Multiple partner and platform capabilities are presented to the customer as one simple interaction.
05 / What I take forward
What I take forward
The customer experiences the whole service. Product accountability needs to reach across organisational and integration boundaries.
Explore another story