Controls Engineer, Energy Management

What they’re looking for

• You have worked in the protocols that move data between machines and between systems (MQTT, OPC UA, REST APIs) and you can say why you would pick one over another for a given job rather than reaching for whichever one you used last.
• You write and read code in at least one language well enough to prototype an integration, test a point map against a live device, and review what the software team ships. Python or Go preferred.
• You read a one-line and a panel schedule and can say what the protection, the breakers and the sources will actually do under a fault.
• You have designed a data contract between two systems: the objects, the fields, the units, the update rates, and what a consumer does when a value goes stale. You held both sides to it.
• You have written the control narrative for a system where two controllers had to agree, and you owned what happened when they disagreed.
• You sit between the controls world and the software world and you are fluent in both. You have taken a control requirement from an electrical engineer and turned it into something a software team could actually build, and you have pushed back on a software design because it would not survive the field.
• You have pushed back on a vendor's scope, or on your own company's assumption, with a number rather than an opinion.
• Bonus: Microgrid and behind-the-meter control (grid-forming BESS, PV plant controllers, turbine and genset dispatch). Utility and industrial protocols (DNP3, IEC 61850 GOOSE, IEC 60870-5-104, Modbus TCP). Schema-driven contracts (OpenAPI, JSON Schema). Automated Level 4 and Level 5 commissioning.
• We are committed to pay equity and transparency.

Skills mentioned

Component & hardware replacement · Patching & MACs · Scheduling · Commissioning testing (L1–L5)