Software Engineer
Software Engineer
Location: Bristol, London or Edinburgh (hybrid, three days a week in the office)
Level: Engineer I – Engineer II
Team: Engineering
Contract: Permanent
Reporting To: Software Engineering Manager
Please note: This role requires an existing right to work in the UK. We can’t offer visa sponsorship, but we review sponsorship role by role, so keep an eye on our careers site for future opportunities.
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.
The role
You’ll join the Kaluza Technology community: a large team of product-focused and data-led Product and Platform Engineers working at serious scale. Our ecosystem is diverse depending on the team, spanning TypeScript on AWS, Go on GCP, and Scala, so we care more about how you think through a problem than which language you learned it in. As a Software Engineer you’ll work in a product team on real features from your first weeks: shaping them with product and design, building them, shipping them, and learning to run them in production, with support at every step.
Engineers at Kaluza build with AI, and we mean that practically. From day one you’ll have paid access to Claude Code, with a budget we don’t ration, and we’ll teach you how we use it: planning work for agents, reviewing what they produce, and understanding every line that lands with your name on it. We care more about your judgement than your typing speed, and we’ll help you build both.
What you’ll do
Build real product features from your first weeks: pick up well-shaped work in a product team, grow into shaping it yourself, and see it through to 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, and understand what they produce: break work down so an agent can take it, review the result as carefully as a colleague’s PR, and be able to explain every line you merge. We’ll teach you our way of working with them.
Learn the systems you run: instrument what you ship, watch how it behaves in production, and shadow the on-call rota before you join it.
Stay close to the people who use what you build: a supplier’s operations team, a customer plugging in a car at night. Ask why, and bring what you learn back to the team.
Improve how the team works: tests, checks, docs and shared context that make the next person’s job easier, including the agents’.
What you’ll bring
These are the foundations and habits we see in engineers who do well here. Nobody arrives with all of them, and the junior end of this role exists so people can grow into them. If you’re excited by the role and can see yourself here, apply.
Ideally, you’ll have:
Solid foundations in one part of a modern stack: TypeScript, JavaScript, Go, Scala, Python or similar, from work, study or things you’ve built yourself, and an appetite to learn the rest.
Curiosity about how systems fail: you’d rather find out why a service fell over than restart it, and you want to learn how to design for that.
Comfort with code you didn’t write: you can read it, test it and explain what it does before you change it, whether a person or an agent wrote it.
An interest in the people who use the product: you ask who it’s for and how you’ll know it worked.
Clear writing: a PR description or a short note that a teammate (or an agent) could act on without asking you.