Skip to content
Kaluza

Senior Software Engineer

Edinburgh, UKHybrid · United Kingdom
Senior · FullTime · Engineering
POSTED 23 SEPTVERIFIED 2H AGO
Apply Ask
Open for
41d
since 23 Sept
Visa
UK
licensed sponsor
Hiring · 30d
38
+1 net · open roles
TypeScriptScalaAWSGCPDistributed systems

Senior Engineer

Location: Bristol, London or Edinburgh (hybrid, three days a week in the office)

Level: Senior Engineer I - Senior 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 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 the first design conversation to running it in production, and you’ll build it with AI coding agents as your default. We’re looking for someone whose judgement is worth more than their typing speed.

Engineers at Kaluza build with AI, and we mean that practically. From your first day you’ll have paid access to Claude Code, with a budget we don’t ration, and MCP access to the systems you need. Our tooling and conventions are evolving quickly, and you’ll have a heavy hand in defining how we build moving forward.

What you’ll do

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 it, direct them, review what they produce as carefully as a colleague’s PR, and maintain the tests and guardrails 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 a car at night. Instrument what you ship so you can see how it’s used, and turn what you learn into shipped changes.

Make good work the default: shape the codebase, conventions and automated checks so that agents and new teammates produce the right thing without anyone catching it in review.

Mentor, review, and share what you know.

What you’ll bring

These are the practices and behaviours we see most in our top engineers and value deeply, but we don't expect everyone to tick every single box. If you're excited by the role and can see yourself thriving here, we’d love to hear from you.

Ideally, you’ll have:

Experience shipping production software: You bring real depth to either the front or back end of a modern stack, and potentially an openness to stretch across both as you navigate our diverse ecosystem.

A daily agentic development practice: You build with tools like Cursor or Claude Code, can walk us through work you’ve shipped this way, and review AI output as rigorously as a colleague’s PR.

Able to navigate a complex, high-stakes domain: You keep complex energy logic legible across microservices, knowing exactly when to use sync vs async to prevent cascading failures.

Cloud and operational ownership: You're comfortable deploying on major cloud platforms using shared tooling. You fully own your software in production, which includes participating in an out-of-hours on-call rota.

Source · KaluzaFirst seen 2 NovOriginal ↗