Full Stack Engineer

Amps is building the AI-native infrastructure layer for connected energy. The grid is being rebuilt around millions of small, distributed assets - home batteries, solar inverters, heat pumps, EV chargers and electric vehicles. Each manufacturer ships its own API, its own auth model, its own quirks and its own idea of what 'state' means. Anyone trying to build a real energy product ends up spending months on integrations before they write a single line of the thing they actually set out to build. We remove that problem. Amps gives developers one REST API, typed SDKs, webhooks and a sandbox to read real-time telemetry from and issue control commands to devices across Tesla, Enphase, SolarEdge, Daikin, Mitsubishi, Wallbox, BMW and every other manufacturer our customers need. Our customers are OEMs exposing device data and control at scale, energy software builders shipping customer-facing products, and utilities operating distributed energy portfolios across grids and markets. If it has an API, we connect to it and we make it behave like one coherent system.

The role involves working across the stack, with the centre of gravity on the backend: the services that talk to hundreds of third-party device APIs, normalise wildly inconsistent data into a single model, and move commands out to physical hardware reliably and quickly. This is a systems job as much as a product job. Devices go offline. Vendor APIs rate-limit, time out, and change. Commands have real-world consequences - a battery that doesn't charge when it should costs someone money. Getting this right means thinking carefully about queues, retries, idempotency, caching and back-pressure, and then building the developer-facing surface that hides all of it. You'll also build the front-end our customers use: dashboards, onboarding flows and developer tooling in Next.js and React.

What you’ll be doing:

• Designing and building backend services in TypeScript and Node.js that ingest telemetry and orchestrate control across large device fleets.
• Building and extending our public API — the product our customers experience most directly — along with SDKs, webhooks and sandbox environments.
• Integrating new device manufacturers and turning inconsistent vendor APIs into a clean, unified model.
• Working on the distributed pieces: queueing, caching, event pipelines, rate limiting, observability and failure handling.
• Building customer-facing interfaces in Next.js and React.
• Shaping technical direction with the rest of the team — architecture, tooling and standards are all still open.

What we’re looking for:

• 5+ years building backend applications, with hands-on experience in TypeScript and Node.js. If your depth is in another language (Go, Python, Java, Kotlin, Rust) that’s fine, provided you have real TypeScript and Node.js experience alongside it.
• Exposure to distributed system design — queues, caching, asynchronous processing, and the failure modes that come with them.
• Exposure to building front-end applications with Next.js and React. You don’t need to be a specialist, but you should be comfortable owning a feature end to end.

Nice to have:

• Experience building and maintaining public-facing APIs.
• Exposure to the energy or electrification space - DERs, EV charging, heat pumps, solar, grid services or energy markets.
• Experience building agents and working with LLMs (e.g. RAG, evals, etc).

You don’t need an energy background to do well here. Several of the hardest problems are ordinary distributed systems problems wearing an unfamiliar hat. Winning is what counts.

How we work:

• Hybrid - 2/3 days a week together in our Central London office, the rest wherever you work best.
• Small team, short feedback loops, very little process.
• Developer experience matters to us internally as much as externally.