Software Engineer, Backend - Base Power Platform

About the Role

You will build the services and APIs behind the Base Power Platform: the software that lets Base and our utility partners operate a geographically distributed battery fleet.

The Utilities team builds the Base Power Platform. Base Operators is its control plane for monitoring fleet state, issuing commands, setting schedules, configuring partitions, and reporting performance. The platform supports Distribution Deferral, Bulk Power Capacity, and Speed to Power across regulated utility markets.

This is a services-first backend role on AWS. You will design Go services and typed APIs, move fleet telemetry at scale, and build the multi-tenant primitives that let utility partners integrate with Base without bespoke engineering. Your code sits between software decisions and physical batteries in homes — correctness matters.

What You'll Do

• Build the Go services and Connect/proto APIs behind Base Operators: fleet state, dispatch, schedules, partitions, and performance reporting.

• Design and operate the Utilities telemetry serving path: ingesting battery data at fleet scale and serving it fresh and queryable to Base Operators, reporting, and partner APIs.

• Build multi-tenant, partner-facing APIs: authentication, tenant isolation, rate limiting, versioning, and self-serve onboarding.

• Make control paths safe by construction: idempotency, retries, backpressure, data consistency, and complete audit trails.

• Own your services in AWS end to end: infrastructure as code, managed queues and databases, deployment, and observability.

• Partner with product engineers on API shape frontends can trust: pagination, error semantics, generated clients, and predictable performance.

• Partner with Trading and Markets on dispatch, settlement data, and performance guarantees.

• Debug production from logs, traces, and metrics — and fix problems permanently, not repeatedly.

What You'll Bring

• 5+ years building production backend systems. We use Go heavily, but care more about systems judgment than a specific language.

• Strong API design instincts: typed contracts (Connect, protobuf, gRPC-style), versioning, error semantics, and empathy for API consumers.

• Solid distributed systems fundamentals: queues, retries, idempotency, backpressure, rate limiting, and data consistency.

• Experience moving and serving data at scale: streaming or telemetry ingestion, time-series or analytical storage, freshness guarantees.

• Experience deploying and operating services on AWS with infrastructure as code.

• Experience with multi-tenant systems—authn/z, isolation, and rate limiting—is a plus.

• Fluency with observability: metrics, logs, traces, and debugging from production data.

• Comfort with edge-connected systems — where networks fail, devices disconnect, and physical state matters — is a plus.

• Clear writing, strong judgment, and the ability to turn ambiguity into facts, decisions, and follow-through.

About the Team

The Utilities team builds the Base Power Platform: the software Base and utility partners use to operate a geographically distributed battery fleet. The software we write is the control plane for monitoring fleet state, issuing commands, setting schedules, configuring partitions, and reporting performance. The platform supports Distribution Deferral, Bulk Power Capacity, and Speed to Power across regulated utility markets.

We build the services and APIs that give consoles, utility partners, and Trading trustworthy fleet data and safe control over physical batteries. We work with product engineers on API shape, and with Trading and Markets on dispatch, settlement data, and performance guarantees. We work in person, move at Base Pace, and own what we ship end to end.

Our Values

• First Principles Thinking: Question assumptions. Principles > rules.