Power Systems Software Engineer

Title: Power Systems Software Engineer

Location: (REMOTE)- IF local to Indianapolis, IN – Hybrid preferred

Duration: 6-12 months

Ideal Start date: August, no later than Sept 8^th

Background or Drug Screen required: YES

Project Details:

• Develop a software tool to streamline transmission outage coordination and power system analysis.
• Build a prototype connecting EMS models and pulling data from MISO for operational planning.
• Automate outage coordination studies and utility/security analysis across Minnesota, Wisconsin, and Michigan.
• Integrate data from EMS, PI, CIMSpy, and CROW.
• Automate VSAT and TSAT studies, batch processing, scenario creation, and contingency analysis.
• Develop GUI tools, APIs, dashboards, reports, and visualization capabilities.
• Support case preparation, outage application, stressed base cases, transfer definitions, and fault scenarios.
• STABLE project is intended to automate end-to-end outage coordination workflows and evaluate interregional and load-pocket transfer capabilities.
• Contractor support is needed to accelerate development, bridge resource gaps, and meet project milestones.
• Conversion is not currently a possibility.

Musts:

• Extensive software/coding experience.
• Strong power systems engineering experience.
• Experience with power system stability studies and modeling.
• Experience with VSAT and TSAT.
• Approximately 6–7 years of experience preferred, but junior candidates may be considered.
• Ability to develop, integrate, test, and maintain production-grade software.
• Strong analytical and problem-solving skills.
• Ability to work with complex power system data and outage analysis.

Pluses:

• Experience with EMS, PI, CIMSpy, or CROW.
• Experience with DSATools.
• Experience automating power system studies and outage coordination.
• Python/Tkinter or similar GUI development experience.
• Experience with APIs, dashboards, visualization, and reporting.
• Experience with .RAW/.PFB case conversions and HVDC modeling.
• Experience with node-breaker models.
• Experience with security-constrained redispatch and load forecasting.
• Experience with automated regression testing and benchmarking.
• Experience identifying proxy constraints or interface risks.