kaluza - Senior Software Engineer II

• 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 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 the team around you: Coach and mentor your peers and help improve how we work and evolve as a team. • 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. • Experience shipping production software: You have a depth of experience in either a front-end or back-end of a modern stack, and potentially an openness to stretch across both as you navigate our diverse ecosystem. • AI coding tools: 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 pull request. • 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. • Strong product sense. You ask the “why” before building, and you can describe a time when user feedback or metrics changed what you shipped. • Clear written communication. You write specs, pull request descriptions and post-mortems with enough clarity and context that either a human teammate or an AI agent can immediately act on them. • A multiplier for your team: You mentor peers and proactively shape how the team works; introducing conventions, checks or shared context that makes everyone else’s output consistently better. • Experience building tooling around coding agents, such as MCP servers, skills or CI checks • Experience in energy, or another real-time or regulated field • Five values guide how we work at Kaluza: • Play to win: Collective pride in decarbonising energy at scale. • Solve the real problem: Cutting through complexity to focus on real-world outcomes. • Build trust every day: Consistency, transparency and doing what we say. • Own the outcome: Full accountability, wins and setbacks, without ego. • Go further together: Collaboration, respect and different perspectives.