Infrastructure Software Engineer

Camus Energy builds software solutions that help new load and generation connect to the grid faster—without sacrificing reliability.

As electricity demand accelerates and clean energy scales, traditional interconnection processes are becoming the bottleneck. Utilities and developers face growing queues, long timelines, and costly upgrades that slow progress across the grid.

Camus enables flexible grid connections that allow new load and generation to connect sooner by planning for and operating within real system constraints. Our platform bridges the gap between grid operators and large load developers, providing a view of time‑varying grid capacity for any given new interconnection point.

We combine high-reliability software experience from companies like Google and Meta with deep power systems expertise across the utility sector. If you’re excited to work at the intersection of infrastructure, software, and climate, we’d love to hear from you.

We're looking for an Infrastructure Software Engineer to sit at the intersection of software development and site reliability. Our software stack is cloud‑native, built on active collaboration with popular open source technologies from developer tooling through production. You'll spend roughly half your time writing production code for product platform and core systems infrastructure and the other half driving reliability, observability, and operational health of these systems with the rest of the engineering team.

On the software side, you'll contribute to the full backend of our product — building and shipping features while also helping to define and build the platform and infrastructure layers those features run on. That means writing production‑quality services and APIs and thinking carefully about what it means for a system to be maintainable, observable, and operable 'll bring an infrastructure‑aware perspective to product development, helping the team build things that are designed to run well in production from the start.

On the reliability side, you'll take the lead on how we build, deploy, monitor, and alert on our systems — but this isn't a sole‑ownership role. You'll work alongside the broader engineering team, building the culture and practices around reliability as much as the tooling itself. That means driving postmortems and remediations collaboratively, establishing the frameworks that help everyone participate meaningfully in on‑call and incident response, and closing the loop by improving internal tooling and systems.

Our platform sits at the heart of how utilities and energy providers manage an increasingly complex grid. The systems you build and operate need to be fast, correct, and available — grid operators make real‑time decisions based on the data and interfaces we provide, and reliability has consequences that extend well beyond our codebase. We take that responsibility seriously, and we want someone who does too.

• Design and build backend services, APIs, and platform infrastructure that power our platform
• Contribute to product features end‑to‑end — from backend logic and data pipelines to the deployment and operational scaffolding that ships them reliably
• Lead the development of our observability stack — metrics, logging, and alerting — and establish the practices that keep the whole team engaged in production health
• Own and evolve our CI/CD pipelines, deployment tooling, and release processes to make shipping software faster and safer
• Drive incident response and postmortems collaboratively, and follow through by building the automation and tooling that closes the loop on recurring issues

• Minimum 3 years of experience in a software engineering role with a strong infrastructure or platform focus
• Experience working with Python 3 — you’re comfortable owning backend services and APIs end to end, not just writing scripts
• Hands‑on experience with Kubernetes and GCP (or comparable cloud), ideally in production environments
• Experience working with CI/CD pipelines
• Familiarity with observability tooling such as Prometheus and Grafana, and an instinct for what good monitoring looks like
• A collaborative…