SCADA Engineer

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the job posting. Key sections: - About the role: The first paragraph(s) describing role: "Nexus Engineering Group is employee-owned... As a SCADA Engineer, you’ll help design, analyze, and deliver electrical substation projects..." Also "As a SCADA Engineer, you will develop and support supervisory control and data acquisition (SCADA) systems..." Also "You will work alongside protection & controls engineers..." Also "Why Nexus" bullet list: employee ownership, early-career, etc. Also "What you can expect:" bullet list. Thus we can have an "About the role" section containing prose summarizing role and why Nexus. - Responsibilities: The "What You’ll Do" bullet list. - Requirements: The "Required Qualifications" bullet list (including required qualifications). Also maybe "Preferred Qualifications" could be separate but we can combine into Requirements? The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can have both Requirements and Qualifications separate if content exists. But we need to avoid thin sections. We have required qualifications list; we also have preferred qualifications list. Could treat "Requirements" as required qualifications, and "Preferred Qualifications" maybe as "Qualifications" heading? Or we could combine both under "Requirements". However we have also "Skills" maybe from required qualifications like proficiency with AutoCAD etc. But we can keep simple: About the role, Responsibilities, Requirements (including required and preferred), Benefits (since benefits listed), maybe Pay? The posting mentions salary range but says "The posted salary range represents the anticipated base pay..." but does not give actual numbers. It says may vary etc. It does not give a specific range; it's generic. According to rules: do NOT include Pay section unless posting actually states them (specific numbers). It does not state a specific range, just says "The posted salary range represents the anticipated base pay..." but no numbers. So we should not include Pay. Schedule: The posting mentions "Flexible work arrangements where business needs allow" and "Hybrid environment". Not a specific schedule. So we should not include Schedule. Benefits: The posting lists benefits: Employee Stock Ownership Plan (ESOP), Medical, dental, vision coverage, plus life and disability insurance, 401(k) with company match and discretionary bonus opportunities, Paid time off, holidays, and paid parental leave, Professional development and career advancement..., Wellness benefits and a flexible schedule where business needs allow. That's specific enough for Benefits section. Thus sections: About the role, Responsibilities, Requirements, Benefits. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not repeat job title as heading. Do not include Job ID etc. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from the posting within those sections. We need to be careful to not omit any substantive info. Let's extract. About the role: Should include description of Nexus Engineering Group being employee-owned, full-service, built by people who do the work. Role description: help design, analyze, deliver electrical substation projects for utility and power delivery clients — exposure across full breadth of substation engineering. Develop and support SCADA systems, RTU integration, substation automation, communication networks that help clients monitor and operate critical electrical infrastructure safely and reliably. Work alongside protection & controls engineers, designers, project managers, and clients to deliver integrated automation solutions across transmission, distribution, and industrial facilities. Why Nexus: employee-owned via ESOP, value you help create comes back to you; invest in early-career engineers and give them real work from the start. What you can expect: Employee ownership (ESOP) — build equity in the firm as it grows; Broad exposure across substation disciplines — physical design, P&C, studies, and field work — to help you find your path; Mentorship from senior engineers who review your work and help you grow; Full-service EPCm exposure, from concept through startup, across a diverse client base; Career paths that grow with you — toward technical leadership, project management, or discipline leadership; Flexible work arrangements where business needs allow. We need to include all that as prose or maybe bullet list? The instruction: Use

  • for any list of duties/requirements/benefits. For "What you can expect:" it's a list; we could treat as a list under About the role or maybe separate section? But we already have About the role; we could embed that list as
    • . However the instruction says use
      • for any list of duties/requirements/benefits. "What you can expect:" is a list of expectations, not duties/requirements/benefits exactly but could be considered benefits? It's more about what you can expect. Might be okay to keep as prose. But to preserve all detail, we could make a list. But we already have Benefits section for benefits; expectations could be considered part of About the role. We'll keep as prose maybe with
        • for the bullet list under "What you can expect:" as it's a list. Better: In About the role section, we can have a paragraph describing role, then a
          • for the "What you can expect:" list. Now Responsibilities: The "What You’ll Do" list items. We'll output as
            • each. Requirements: We have required qualifications list. Also we have preferred qualifications list. Could combine into Requirements section with subheadings? But we cannot add extra headings besides the allowed ones. We could separate into Requirements (required) and Qualifications (preferred). Since we have both, we could make two sections: Requirements and Qualifications. That would be okay if we have substantive content for each. Let's see if we have enough content for Qualifications (preferred). Yes we have a list of preferred qualifications. So we can have Requirements (required) and Qualifications (preferred). That follows allowed headings. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits. Now we need to ensure we don't include filler like "commensurate with experience". Not present. Now we need to extract each bullet precisely. Let's copy the required qualifications bullet list: - Bachelor's degree in Electrical Engineering, Electrical Engineering Technology, or related field - 3+ years of SCADA, automation, controls, power delivery, utility, or industrial systems experience. - Experience with RTU configuration, control systems integration, or substation automation projects. - Experience interpreting electrical schematics, wiring diagrams, and communication drawings. - Knowledge of SCADA and communication protocols including DNP3, Modbus, IEC-61850, or similar. - Familiarity with substation automation systems, relays, RTUs, HMIs, and communication networks. - Experience with AutoCAD, AutoCAD Electrical, or equivalent design software. - Proficiency with Microsoft Office applications. - Strong troubleshooting, analytical, organizational, and communication skills. - Ability to work effectively in a team-oriented environment Preferred qualifications bullet list: - Engineer-in-Training (EIT) certification. - Professional Engineer (PE) license or progress toward licensure. - Experience with SEL RTACs, SEL relays, Schweitzer Engineering Laboratories equipment, GE, ABB, Siemens, or similar utility automation platforms. - Experience supporting transmission or distribution utility clients. - Experience with networking, cybersecurity, and industrial communication systems. - Commissioning or startup experience. Now Benefits bullet list from later: - Employee Stock Ownership Plan (ESOP) — an ownership stake and a share in the long-term success of Nexus - Medical, dental, and vision coverage, plus life and disability insurance - 401(k) with company match and discretionary bonus opportunities - Paid time off, holidays, and paid parental leave - Professional development and career advancement — training, certifications, licensure support, tuition assistance, and mentorship - Wellness benefits and a flexible schedule where business needs allow Now About the role content: We need to include all prose from the beginning and the "Why Nexus" and "What you can expect:" list. Let's extract the prose: "Nexus Engineering Group is employee-owned, full-service, and built by the people who do the work. As a SCADA Engineer, you’ll help design, analyze, and deliver electrical substation projects for utility and power delivery clients — with exposure across the full breadth of substation engineering. As a SCADA Engineer, you will develop and support supervisory control and data acquisition (SCADA) systems, RTU integration, substation automation, and communication networks that help clients monitor and operate critical electrical infrastructure safely and reliably. You will work alongside protection & controls engineers, designers, project managers, and clients to deliver integrated automation solutions across transmission, distribution, and industrial facilities." Then "Why Nexus You’ll own a piece of what you build. Nexus is employee-owned through our ESOP, so the value you help create comes back to you — not just outside shareholders. We invest in early-career engineers and give them real work from the start." Then "What you can expect:" list as above. We need to ensure we don't duplicate sentences. There's repetition of "As a SCADA Engineer". We'll keep as is. Now format. We'll output:

              About the role

              Nexus Engineering Group is employee-owned, full-service, and built by the people who do the work. As a SCADA Engineer, you’ll help design, analyze, and deliver electrical substation projects for utility and power delivery clients — with exposure across the full breadth of substation engineering. As a SCADA Engineer, you will develop and support supervisory control and data acquisition (SCADA) systems, RTU integration, substation automation, and communication networks that help clients monitor and operate critical electrical infrastructure safely and reliably. You will work alongside protection & controls engineers, designers, project managers, and clients to deliver integrated automation solutions across transmission, distribution, and industrial facilities.

              Why Nexus You’ll own a piece of what you build. Nexus is employee-owned through our ESOP, so the value you help create comes back to you — not just outside shareholders. We invest in early-career engineers and give them real work from the start.

              What you can expect:

              • Employee ownership (ESOP) — build equity in the firm as it grows
              • Broad exposure across substation disciplines — physical design, P&C, studies, and field work — to help you find your path
              • Mentorship from senior engineers who review your work and help you grow
              • Full-service EPCm exposure, from concept through startup, across a diverse client base
              • Career paths that grow with you — toward technical leadership, project management, or discipline leadership
              • Flexible work arrangements where business needs allow
              Then Responsibilities:

              Responsibilities

              • Design, configure, and support SCADA, RTU, HMI, and automation systems for utility and substation projects.
              • Develop SCADA architecture, communication diagrams, I/O lists, point databases, and system integration documentation.
              • Develop and review wiring diagrams, control schematics, communication drawings, and network layouts.
              • Coordinate with Protection & Controls engineers to integrate relay data, alarms, status points, and control functions into SCADA systems.
              • Support communication protocols such as DNP3, Modbus, IEC-61850, and Ethernet-based industrial networks.
              • Perform system testing, factory acceptance testing (FAT), site acceptance testing (SAT), and commissioning support.
              • Interface directly with clients, vendors,