Original job description
About Enurgen
Enurgen is building DUET, a generational platform for utility-scale solar that turns raw fleet telemetry into recovered revenue. We close the gap between what conventional monitoring can see and what it can diagnose, and across a portfolio it adds up to a lot.
At our core is DUET (DUal-sided Energy Tracer), a 3D, physics-based energy yield model spun out of SUNLAB at the University of Ottawa and built on 10+ years of R&D. The DUET Platform runs per-timestep model-vs-field comparisons across the full 30-year asset lifetime, from design through construction to operations, automating detection, prioritization, and reporting at the component level. An AI agent on top enriches the analysis with context and patterns across portfolios.
The software engineering work
This is the work closest to the equipment: on-prem software that keeps running when the WAN doesn't, ingesting OPC UA and MQTT/Sparkplug B straight from site SCADA infrastructure. Plant operators lean on it hardest in the moments the cloud isn't reachable, so it has to be right and it has to be there.
This is a software engineering role. You'll be writing the software that talks to SCADA systems, not configuring them.
What you'll do
Own the collector's protocol adapters (OPC UA and MQTT/Sparkplug B today) and add new connection kinds as we push further into on-site collection
Harden the parts operators depend on: the alarm engine, local rollups, and idempotent ingest that survives a network partition
Help shape how we collect data on-site as latency requirements push us closer to the equipment. This is a direction we're actively exploring, not a fixed roadmap
Extend loss attribution and issue detection workflows with our R&D team, from the data collection side
Work directly with customer OT and controls teams when the problem benefits from it
What we're looking forRequired
5+ years building production software, ideally systems, embedded, or industrial
Strong systems thinker. AI changed the leverage, so you architect solutions before reaching for code
Strong Go, or deep systems experience in a comparable language and the appetite to make Go your home
Hands-on experience with industrial protocols: OPC UA, Modbus, DNP3, or MQTT/Sparkplug B
Track record of building greenfield software in a startup-shaped environment: small team, fast iteration, real customers
Strong written and verbal communication, including with non-engineering stakeholders
Strong pluses
Any one of these moves you up the list:
SCADA or data collection experience in renewables. Wind counts fully; the concepts transfer
OLAP / time-series database experience. We run ClickHouse at the edge and in the cloud
OT security frameworks: NERC CIP, IEC 62443
Ignition or a comparable SCADA platform
Performance-sensitive or low-latency systems work
Not required
A solar background specifically. Wind and other renewables transfer directly. You'll pick up plant physics; we don't expect you to walk in with it.
Front-end experience. Useful, not required.
How we work
Small, fast increments. Getting something real in front of operators usually beats polishing it longer in isolation.
Tight feedback loops. We learn from short experiments with real customers, not speculative roadmaps.
Focus over breadth. Fewer things, done well.
Engineers paired with coding agents. AI is part of how we write code, debug, document, and analyze data. It's built into the workflow, not bolted on the side.
High-touch and Slack-driven. Threads carry the work async, huddles when priorities move fast. No meetings to fill calendars.
Small enough that nobody hides. Everyone ships to production, and everyone talks to customers.
Engineering and R&D at the same table. The decisions are sharper for it.
Location
Remote or hybrid. Office in Ottawa, Ontario, Canada. Openness to occasional travel is a nice to have.
