Cloud Software Developer

We're looking for a hands-on builder who is at their best running things in production, not just shipping them. Broad enough to move across backend, integrations, data, and operations. Pragmatic enough to know that a system that quietly runs without drama is worth more than one that demos well.

Must haves

• Hands-on experience in cloud, backend, platform, or DevOps roles

• Real experience taking systems to production and scale, not only building them

• Start-up or scale-up background: broad responsibility, close to production-critical systems, without a separate ops team to catch you

• Has carried genuine operational weight: on-call, incidents, production support

• Has designed and shipped public or partner-facing APIs or SDKs that external developers actually integrated against

Nice to haves

• Hardware or IoT integration experience, or having worked on a connected consumer hardware product

• Full-stack or web-app development experience (e.g. React)

• Experience with AI-assisted development tooling and an openness to using it in what you build and how you build it

Your mission

Starflow is building clean energy tech for homes and buildings, and we are building it as an open system from the start: hardware, Cloud platform, and the interfaces that connect them. Clean APIs and SDKs for third parties to build against are a design priority, not an afterthought, alongside the customer-facing product itself.

As our next Cloud Software Developer, you'll join Snorre to shape what the Cloud platform becomes. You'll take ownership of core backend systems, the developer workflow that keeps them shipping, and the operational layer that keeps them running. The interfaces you'll design will be used by end-users, by other teams inside Starflow, and by external developers building on top of the platform. Getting those right, under real launch pressure, while the product and the platform are both evolving, is the work.

A platform that carries real customers
The Cloud platform handles real device traffic and a growing customer base, reliably, at scale. It supports the first commercial product launch from a technical standpoint and grows with the customer base without re-architecture. When the question is "can Cloud carry real customers today?", the answer is demonstrably yes.

Customer-facing interfaces, live
End-users can view and interact with their Starflow system through a real interface. Cloud and design work closely so that what gets designed is something the platform can serve, and it reaches users without stalling on a missing backend or an undefined contract. The platform exposes what it needs to for those interfaces, and for third parties integrating via APIs and SDKs.

Shipping to production is routine
Cloud changes reach production multiple times per day. A regression is caught by the pipeline, not by a customer. The team's instinct when they have a fix is "ship it," not "wait for a safe window."

Other teams build on Cloud, not around it
Embedded, product, and design can integrate against Cloud contracts from documentation alone. Device-to-Cloud communication is reliable enough that other teams stop treating it as a risk. A third-party developer could build against the public API or SDK without a verbal walkthrough.

What you'll build

A production-grade backend and Cloud platform
You'll take the Cloud platform from a working prototype to something that carries real customers and scales with them. Working with Snorre, you'll shape the architecture before production build starts, contributing your own perspective on what gets hardened, what gets rebuilt, and in what order. The result is a backend that is tested, observable, maintainable, and secure by default.

An operations and delivery workflow that makes shipping routine
You'll build the CI/CD and automated testing pipeline that makes frequent, low-drama production releases the default, and you'll own the operational layer on top of it: observability, alerting, logging, incident response, and production support. Security, authentication, access control, and device identity will be designed in from the start, not added later.

Customer-facing and third-party interfaces
You'll build the backend that serves the customer-facing interfaces our designers are shaping, so end-users can view and interact with their Starflow system at launch. Alongside that, you'll design and ship the APIs and SDKs that third-party developers will build against: clear contracts, sensible versioning, and documentation that holds up for people you may never meet.

A shared Cloud function
You'll establish the working patterns that make Cloud a two-person capability: code review both ways, architecture input both ways, and a codebase that both people on the team can fully speak to, change, and operate. You'll build the direct working relationships with embedded software, product, and design so Cloud interfaces serve what other teams are building, without those conversations needing to be organized for you.

How you'll work

You'll work most closely with Snorre, Starflow's Lead Cloud Software Developer, and the two of you will co-own the codebase and the technical direction. In practice that means pairing on the hard architectural calls before anything gets built for production, reviewing each other's code as a matter of course, and dividing real ownership of the platform so that either of you can carry it alone when needed. You'll spar on design decisions as equals: bringing your own view, holding it with substance, and changing it when the better argument wins.

Beyond Cloud, your work is what makes the platform something other teams build on. You'll define the API and device-communication contracts that embedded software depends on, build the backend that serves the interfaces product and design are shaping, and keep those interfaces documented and stable enough that other teams integrate against them without a walkthrough.

The pace is real, and the work is broad. In a single week you might harden a piece of the platform for scale, ship a customer-facing feature, instrument a service so it tells you when it breaks, and decide deliberately what is good enough to revisit later. You'll make those cost-and-value trade-offs constantly, often without a full picture, building the tooling and workflow you need as you go rather than waiting for it to exist. If that kind of end-to-end ownership is where you do your best work, this is the right place.

Who we're looking for

You are someone who takes ownership of the full picture: not just what you ship, but how it behaves in production, how it scales, and what happens when something goes wrong at the worst possible time. The breadth is the appeal, not a compromise.

You take production seriously from the first line

Your backends are tested, observable, and secure by default. You talk about past systems in terms of how they behaved under load, what broke, and what you changed. The monitoring is part of the build, not a later pass.

You run toward operational ownership

On-call, incidents, and production support are a normal part of the work for you. You've diagnosed real failures under pressure, you know what you changed so they didn't recur, and "I built it, I run it" is how you naturally think about it.

You work in the open

Your reasoning is legible to the people you work with. You give and take code review without friction, hold architectural opinions strongly enough to defend them and loosely enough to update them, and find having a strong peer to spar with more productive than working alone.

You're fluent in the cloud and make shipping routine

You've built and run production systems on a major cloud platform, with CI/CD and automated-test pipelines behind them, and you use infrastructure-as-code by default. Our stack is AWS-first, so you're either already fluent there or ready to get there fast.

Starflow is building a seamless platform that brings together solar panels, home batteries, EV chargers, and the grid. At the core is a smart hybrid inverter — designed to become the central control unit of the modern home, capable of monitoring, managing, and optimizing energy use automatically.

With advanced hardware and open software architecture, the system will adapt to each home in real time. It’s being developed to help lower energy bills, enable storage and bring everything together in one intuitive interface. Easy to install, built to last, and ready for the energy needs of tomorrow.

Clean energy, made effortless. Quiet in presence. Powerful in action. Fully in sync with how we want to live. We’re building what energy should feel like. And this is just the beginning.