Founding forward deployed engineer

What we are building

At Elergi we are on a mission to stop the grid being the limit on what the world can build. Almost everything ahead of us runs on electricity: data centres, reindustrialisation, the energy transition. All of it has to reach the grid first, and that is where it stops. In some markets the connection queue holds twice everything already installed. In the Netherlands the queued batteries alone are three times peak load; in Europe's data centre hubs, a project waits seven to ten years for an answer.

Grid connections are about more than just copper. What projects are waiting for is an approval, and someone has to work it out: model the network, run the power flow and stability cases, find where the system fails under load, and size the fix. Manually, one project at a time, while the queue underneath keeps changing and invalidating it. We build agentic AI that does this work on the real physics, across thousands of scenarios, and returns a result an engineer can defend.

We are gathering a team of unusually good people. Between us we have founded companies and taken one from zero to the Nasdaq; mapped and modelled real grids; and worked in consulting, private equity, and AI startups from Stockholm to San Francisco. We like building at a furious pace, and solving problems that are hard.

We are obsessed with our customers, with what would make their work easier and their decisions better. We span several nationalities, we ski, we sing, and we want both the company and its culture to soar.

The role

The software engineer and power systems engineer, in one person and on site. You would write code and be the one sitting with planners while it runs. A first deployment is not a handover; it's where the product gets built.

What you'd do

• Go to the utility: get their grid model, their conventions, and their data into our system, and make the first real studies run
• Build what the deployment needs: importers, adapters, and checks against the results they already trust
• Turn each of those into something the core product ships, so the next deployment starts further along than the last
• Sit with planners while they use it, and bring back what actually broke rather than what was said in the meeting
• Own the answer end to end for your accounts, including the times it is wrong

Requirements

• You write production code and would be comfortable owning a service. Python is what we use
• Enough power systems to be useful in the room: you know what a load flow case is and why the contingency list matters, or you can get there in a month
• You have put software into an environment you do not control, with their data, their network, and their rules
• You would rather be on site than on a ticket, and you are willing to travel. Utilities and system operators are not all in Stockholm

Process

1. 01 Intro, 30 minutes What you have built, what we are building, and whether this is worth more of both our time.
2. 02 Deep dive, 1 hour Your own work in detail. What you actually did, what you would do differently.
3. 03 Technical, 1 hour A real problem of ours, worked through together rather than a puzzle from a book.
4. 04 Final, 1 hour The people you would work with day to day, and the questions you still have for us.

We read every application ourselves. If this is the problem you want to work on, we would be glad to meet you.

Apply