Jobs · Engineering

Senior SCADA Engineer, Solar/Storage (BESS) Operations Engineering (Field/OEM)

Invenergy · Washington, DC · 4 wk ago
RemoteRemoteEngineeringFull-time
We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. Content: - Intro about Invenergy (company description). Could be "About the role"? Actually "Position Overview" is description. Could be "About the role" heading. - Responsibilities: list of duties. - Required Qualifications: bullet list? It says "Required Qualifications 5-8 years of industry experience supporting renewable energy generation equipment Eligible to work in the United States without the need for employer visa sponsorship now or in the future". That's two items. - Preferred Qualifications: long list of specifics. - Base Pay: salary range and bonus. - Benefits: mention medical, dental, vision insurance, 401k, profit sharing, paid time off, etc. - Schedule: not mentioned. So we should not include Schedule section. - Skills: maybe we can extract from Preferred Qualifications as skills? Could create a Skills section summarizing technical skills. But we must not invent content; we can list the specific skills mentioned. The Preferred Qualifications includes many specific experiences; we could treat them as Skills. However we also have Required Qualifications. Could combine into Requirements and Qualifications sections? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have multiple sections: About the role (position overview), Responsibilities, Requirements (maybe required qualifications), Qualifications (maybe preferred qualifications), Skills (maybe technical skills), Benefits, Pay. We must not repeat job title as heading. No Job ID. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can group them. We must not include boilerplate like EEO, equal opportunity, etc. Remove that. Also remove "This position will be open for application for at least 3 calendar days..." etc. That's metadata; we can drop or fold into short p. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include a short p for that posting duration note, but maybe better to drop it as it's not substantive? It's about application window; could be considered metadata. Probably drop. We need to output only HTML fragment, no /, no markdown fences. Let's structure:

About the role

Position Overview As a SCADA Engineer, you will work as part of a growing SCADA team that is responsible for maintaining current SCADA infrastructure, integrating new SCADA infrastructure, and providing technical support to a large operating fleet of renewable energy projects throughout North America, Latin America, and Europe.

But we also have company description at start: "Invenergy is North America’s largest privately held developer..." That's about company, not role. Could be included in About the role? Might be better to include as part of About the role or separate? The instruction says use headings for section headings e.g. About the role, Responsibilities... So we can put company description under About the role as context. We need to preserve all substantive information; we can include that company description in About the role. Thus About the role p includes both company description and position overview. Now Responsibilities: list each duty as
  • . Let's extract responsibilities bullet points: - Serve as Subject Matter Expert for OEM hardware and software capabilities. - Work closely with the Performance Analytics and Availability Engineering groups to validate system modifications/upgrades and maintain proper operation of the generation equipment (wind turbines, inverters, tracker controllers, data loggers, etc.). - Support operating facilities and the Invenergy Control Center with upkeep/troubleshooting of field equipment. - Employ analytical, conceptual, and creative thinking skills to troubleshoot/improve SCADA system reliability to drive overall business and systems performance. - Lead technical resolutions/troubleshooting through discussions with OEM/integrators and other engineering functions. - Work with other SCADA Engineers to integrate systems and provide telemetry to external entities. - Validate current SCADA architecture and ensure all additions and modifications are scalable. - Provide training/development support for engineers and site personnel. - Mentor team members on new SCADA technologies, tools, processes, and standards. - Drive contractual terms to best fit the needs of the organization and operational personnel. - Identify pending renewable energy platforms and software versions that may resolve issues or pose new challenges. - Identify the impact regulatory requirements will have on operating field devices/systems. That's all. Now Requirements: maybe "Required Qualifications". We'll make a section

    Requirements

    with
    • 5-8 years of industry experience supporting renewable energy generation equipment
    • Eligible to work in the United States without the need for employer visa sponsorship now or in the future
    Now Qualifications: maybe "Preferred Qualifications". We'll list each bullet. But the preferred qualifications list is long and includes many subcategories. We'll need to preserve all details. We can break into sub-sections? But we only have headings allowed; we could keep a single
      with many
    • items, each representing a bullet. However the original text includes sentences like "Power Plant Controller (PPC) experience including design/support/testing and troubleshooting primarily on the SEL RTAC platform but also GE RX3i PACSystems, GPM, and Allen-Bradley." That's one bullet. Then "Solar specific experience supporting/troubleshooting:" followed by list of items. That could be a bullet with sublist? But we cannot invent structure beyond
      • . We could keep as a single
      • containing the whole sentence, preserving details. Similarly for Energy Storage specific, Wind specific, General, etc. We also have "Experience with industrial protocols (DNP3, Modbus, OPC, SEL FM)" appears twice; we can keep both but maybe deduplicate? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Duplicated lines: we should remove duplicated lines. There's a duplicate "Experience with industrial protocols (DNP3, Modbus, OPC, SEL FM)" appears twice in Preferred Qualifications. We should keep only one instance. Also "Professional project management, team management, or leadership experience" is a bullet. "Experience with developing training content and delivering to small-to-medium size audiences" "Database Experience: MS SQL, PostgreSQL" "Experience testing and troubleshooting device communication issues within a SCADA network, including diagnosing and resolving connectivity issues using tools such as Wireshark, optimizing network performance, and ensuring reliable data transmission" We need to ensure we keep all unique items. Let's list them: 1. Power Plant Controller (PPC) experience including design/support/testing and troubleshooting primarily on the SEL RTAC platform but also GE RX3i PACSystems, GPM, and Allen-Bradley. 2. Solar specific experience supporting/troubleshooting: - Inverters (SMA, TMEIC, GE, Schneider Electric, Sungrow, Power Electronics, Kaco/Siemens) - Trackers (Nextracker, FTC, ATI) - HMI Platforms (GreenPowerMonitor, GE HDM, SEL RTAC, Inductive Automation Ignition, Isotrol Bluence) 3. Energy Storage specific experience supporting/troubleshooting: - Power Conversion Systems (Fluence, SMA, Power Electronics, DynaPower, Parker, Sinexcel, Delta) - HMI Platforms (Fluence, Inductive Automation Ignition, Powin Kobold, SEL RTAC, Energport) 4. Wind specific experience supporting/troubleshooting: - Control Systems (GE MarkVIe (ToolboxST, WorkstationST), Bachmann (Solution Center), Vestas, Siemens-Gamesa (WTC3) - HMI platforms (GE WindSCADA, Vestas VOB, SEL RTAC, Inductive Automation Ignition, Siemens-Gamesa WPS) 5. General Data Loggers / Switches (Moxa, Campbell Scientific, Red Lion, Hirschmann, Cisco) 6. Experience with industrial protocols (DNP3, Modbus, OPC, SEL FM) 7. Professional project management, team management, or leadership experience 8. Experience with developing training content and delivering to small-to-medium size audiences 9. Database Experience: MS SQL, PostgreSQL 10. Experience testing and troubleshooting device communication issues within a SCADA network, including diagnosing and resolving connectivity issues using tools such as Wireshark, optimizing network performance, and ensuring reliable data transmission Note: The original also had "Experience with industrial protocols (DNP3, Modbus, OPC, SEL FM)" twice; we keep one. Now Benefits: The posting says: "Invenergy offers a variety of other benefits including medical, dental and vision insurance, 401k, profit sharing, paid time off, etc." Also earlier: "In addition to base pay, the total annual compensation package may also include eligibility to participate in our bonus program(s) which are designed to reward individual and company performance." That's more about bonus, but we have Pay section for base pay and bonus. Benefits section can include medical, dental, vision insurance, 401k, profit sharing, paid time off. We should not include EEO etc. Pay: Base Pay 125,000.00 - 155,000.00 USD Annual Bonus: 10% - 25%. Also note about base pay range etc. We'll include that. Schedule: not present, so omit. Now we need to ensure we don't create sections with filler like "commensurate with experience". Not present. Now output HTML fragment. We'll wrap each section in

        and then content. For About the role: we can include two paragraphs: company description and position overview. Or combine into one

        . Let's do two

        for readability. Company description: "Invenergy is North America’s largest privately held developer, owner, and operator of power infrastructure. With 25 years of trusted execution, we deliver reliable, affordable energy through a diverse portfolio that includes natural gas, solar, land-based wind, energy storage, transmission, and domestic manufacturing. Headquartered in Chicago, we develop, own, and operate large scale projects that power communities and support the energy future." Position overview: "As a SCADA Engineer, you will work as part of a growing SCADA team that is responsible for maintaining current SCADA infrastructure, integrating new SCADA infrastructure, and providing technical support to a large operating fleet of renewable energy projects throughout North America, Latin America, and Europe." Now Responsibilities

          . Now Requirements
            . Now Qualifications
              with the items above. Now Benefits
                with medical, dental and vision insurance, 401k, profit sharing, paid time off. Now Pay

                with base pay and bonus. We should not include any extra text like "Base Pay 125,000.00 - 155,000.00 USD Annual Bonus: 10% - 25%". We'll put in

                . Now ensure we didn't miss any substantive info: The note about position open for at least 3 calendar days etc. We dropped; it's minor metadata. Could fold into short p but we can drop as per instruction: "fold minor metadata into a short

                or drop it." Dropping is okay. Now check for any other substantive info: "Invenergy LLC is an equal opportunity employer..." removed. Now ensure we didn't inadvertently include duplicated lines: we removed duplicate industrial protocols line. Now output. Let's craft HTML. Be careful to escape any special characters? Not needed. We'll output:

                About the role

                Invenergy is North America’s largest privately held developer, owner, and operator of power infrastructure. With 25 years of

Similar jobs