Staff Engineer, Kaluza

• Have deep technical expertise applied to system design and architecture ownership across a squad, not just a single team or service
• Be able to create and challenge product and engineering proposals and make design trade-offs, backed by data
• Have a track record diagnosing and resolving complex technical and product issues, including in domains you aren't already close to
• Be skilled at establishing and driving adoption of architectural patterns and technical standards that other teams build on top of
• Be comfortable taking ambiguous, loosely-defined technical requirements and turning them into a concrete plan others can execute against
• Be accomplished at influencing both upwards and outwards, bringing clarity and alignment to engineering leadership, product, and adjacent squads on technical direction
• Have a track record mentoring and upskilling other engineers, and fostering a learning culture beyond your own immediate team
• Be comfortable operating in a high-integrity data domain (billing or payments), where reliability, security, and auditability come before speed
• Have demonstrable customer obsession and a working-backwards practice: start from the problem other engineering teams or end customers have, and design the simplest platform capability that solves it
• Have a demonstrable record of applying AI/LLMs to deliver customer impact, not just adopting AI tooling internally
• We understand some people may not apply for jobs unless they tick every box. But if you're excited about joining us and think you have some of what we're looking for, even if you're not 100% sure, we'd still love to hear from you

Desirable

• Kaluza runs the billing and payments engine behind some of the world's biggest energy retailers. This role builds and evolves the platform other engineering teams build on top of: the shared APIs, integration patterns, and technical standards that let billing and payments capability get built once and reused everywhere, instead of 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, having a consistent, well-designed API platform is what lets new capability get adopted quickly and safely across every team that needs it, rather than each team solving integration and standards problems on its own. Getting this right directly shapes how fast Kaluza can extend billing and payments capability to new markets and clients
• We're also in the middle of reorganising how this part of the business works, moving toward one shared global core that every market configures rather than rebuilds. This role's remit, API platform and standards, is one of the technical foundations that shift depends on
• You'll own system design and architecture for the API Platform and Standards squad, not just a single service
• You'll create and challenge product and engineering proposals, backing design trade-offs with data
• You'll diagnose and resolve complex technical and product issues, including in areas outside your immediate domain
• You'll establish architectural patterns and technical standards that other teams build on top of
• You'll take ambiguous, loosely-defined technical requirements and turn them into a concrete plan others can execute against
• You'll influence engineering leadership, product, and adjacent squads to bring clarity and alignment on technical direction
• You'll mentor and upskill engineers beyond your immediate team, contributing to a wider learning culture