UK remote
Senior Software Engineering Manager (Global Billing, Payments & API )
About this role
Job title: Senior Software Engineering Manager (Global Billing, Payments & API) Location: London / Bristol / Edinburgh (Hybrid Office - 3+ days per week) Salary: £100,000 - £125,000 Team: Global Billing, Payments & API) Level: PL2 This role is based in London, Bristol or Edinburgh and requires existing right to work in the UK. At this time, we are not able to offer visa sponsorship for this role. We are committed to building a diverse, global team and our sponsorship policy is evaluated on a role-by-role basis.
We encourage you to keep an eye on our careers site to stay informed about future opportunities where we are able to offer visa sponsorship. Kaluza is the Energy Intelligence Platform, turning energy complexity into seamless coordination. We help energy companies overcome today’s challenges while accelerating the shift to a clean, electrified future. Our platform orchestrates millions of real-time decisions across homes, devices, markets and grids.
By combining predictive algorithms with human-centred design, Kaluza makes clean energy dependable, affordable and adaptive to everyday life. With teams across Europe, North America, Asia and Australia, and a joint venture with Mitsubishi Corporation in Japan, we power leading companies including OVO, AGL and ENGIE, as well as innovators like Volvo and Volkswagen. What will I be doing? Kaluza runs the billing and payments engine behind some of the world's biggest energy retailers.
Every bill sent and every payment collected across Kaluza's markets increasingly runs through one shared core platform, and GBPA exists to build and run that core, so foundational billing and payments capability gets built once and reused everywhere, rather than rebuilt separately for every new market or client relationship. That matters because of where Kaluza is headed: as we grow into new markets and take on more of the world's largest energy retailers as clients, rebuilding core billing and payments capability separately for each one is slower, costlier, and more error-prone than building it once and configuring it at the edge.