Senior Software Engineer

Job description

Senior Engineer Location: Bristol, London or Edinburgh (hybrid, three days a week in the office) Level: Senior Engineer II (TL1) Team: Engineering Contract: Permanent Reporting To: Software Engineering Manager About Kaluza 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, 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 you’ll do You’ll join a technology community of product-focused and data-led product and platform engineers working at scale. We have a diverse ecosystem, spanning TypeScript on AWS, Go on GCP and Scala, we index on product-minded problem solving over language purity. As a Senior Engineer you’ll own a slice of the product end-to-end, from design through to production, and you’ll build AI coding agents as your default. We’re looking for someone whose judgement is worth more than their typing speed. From your first day you’ll have paid access to Claude Code, with a budget we don’t ration, and access to the systems you need through MCP. Our tools and conventions evolve quickly, and you’ll directly impact how we build from here. Own a slice of the product end to end: shape the problem with product and design, build the interface and the services behind it, ship it, and run it in production. Work across the stack over time : depending on the team you’ll work across the interface people use, the services behind it, and the APIs between them, in whatever stack your team runs. Build with AI coding agents as your default : Break work down so agents can execute, direct them, and review their output as carefully as you’d review a colleague’s pull request. You’ll also maintain the tests and safeguards that let agent written code merge safely. Stay close to the people who use what you build: directly or through our forward-deployed engineers: a supplier’s operations team, a customer plugging in…