You build the software systems that make the modern electrical grid work. The grid is undergoing the most significant transformation since electrification — generation is shifting from a small number of large fossil plants to a vast number of distributed renewable sources, demand patterns are changing as transportation electrifies, storage is becoming a meaningful part of the system, and the operating logic that worked for the old grid breaks down in the new one. Software is doing much of the heavy lifting in making the new system function.
The problems are intellectually substantial. Optimal dispatch of generation across a system with intermittent renewables, storage, and conventional plants is a real-time optimisation problem at scale. Forecasting renewable generation accurately enough to plan grid operations requires combining weather modelling, machine learning, and physical knowledge of the assets. Distribution-system management as solar panels and EVs proliferate at the grid edge requires reimagining systems that were designed for one-way power flow. Energy markets — the auctions that match generation and demand minute by minute — require sophisticated software to clear correctly.
The companies doing this work span established utility software vendors, ISOs and RTOs (the entities that operate wholesale grids), the utilities themselves, and a growing ecosystem of climate-tech startups building everything from VPP (virtual power plant) platforms to grid-edge intelligence to energy-market analytics. The work culture is generally closer to enterprise software than to consumer tech, with the seriousness that comes from working on systems that affect physical infrastructure.
Kitsune can talk through anything on this page — whether it might suit you, what to do next, questions this page doesn't answer. Everything here is yours to read either way.
The domain knowledge requirement is heavy. Grid operations are a deep field with their own vocabulary, conventions, and physics. A great software engineer who joins the field needs 1–2 years to become genuinely productive on the substance. The companies that try to hire pure software talent without supporting the domain learning typically build software that grid operators won't use. The engineers who thrive are the ones who lean into learning the domain alongside the software work.
The pace is slower than consumer tech. Grid software has reliability and security requirements that consumer tech doesn't. Deployment is careful. Iteration is incremental. Engineers who came expecting startup velocity sometimes leave because the cadence is more like enterprise software than like Silicon Valley. People who stay describe the trade-off as worthwhile because the impact is more concrete.
The field intersects with energy policy in ways most software work doesn't. The rules of energy markets, the design of capacity payments, the rules around demand response — these are policy questions, and they shape what software can and can't do. The most senior engineers in the field tend to develop policy literacy whether or not they intended to.
Standard software engineering credentials (computer science degree, equivalent self-taught experience, bootcamp + portfolio) plus deliberate accumulation of domain knowledge. Internships at grid software companies, utilities with tech teams, or climate-tech startups are valuable. Some engineers come in through electrical engineering and add software skills; some come from finance or operations research backgrounds with strong quantitative skills. The field is hiring across all these paths and the demand currently exceeds supply.
Engineers who come in expecting a pure-software role and underinvest in grid domain learning will find more of their entry-level work AI-competable. Engineers who lean into the domain acquire protection that pure SWE AI tools cannot replicate.
Strong demand as grid digitalisation scales. Domain expertise is the differentiator; AI tools accelerate the SWE layer but cannot shortcut 1–2 years of grid domain learning. The most valuable engineers in this role will be grid-knowledgeable software engineers, not software generalists.
People drawn to Grid Software Engineerare often drawn to these — in the order they're closest. The ones marked sit in a different field entirely.