SCADA Engineer - Level 2

We need to produce HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate (EEO, legal, etc). Must not invent or summarize away detail. Must not include sections with filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. Let's see what info we have: - Title: SCADA Engineer – Level 2 (but we don't repeat as heading) - Department: Engineering - Location: Houston, TX - Supervisor: Director of SME - FLSA Status: Exempt - Position Status: Permanent, Full-Time - Work Status: Remote - Summary: The SCADA Engineer Level 2 supports SCADA system design, development, and deployment for utility-scale solar PV and BESS projects. This role requires hands-on experience with SCADA programming, industrial protocols, IT networks, and cybersecurity. The Engineer Level 2 will work closely with senior engineers to configure and troubleshoot SCADA systems, ensuring reliable plant operation and secure data communication. This position reports to the Director of SME or another management personnel that the CEO of the Company may designate. This position is (remote) located in Houston, TX and hours are Monday through Friday, from 8:00am to 5:00pm or 9:00am to 6:00pm local time. This position is expected to travel up to 30%. Applicants must be authorized to work for any employer in the United States. We are unable to sponsor or take over sponsorship of an employment visa at this time. - Essential Job Function & Responsibilities: list of bullet points (but they are in paragraph with line breaks). We need to extract duties. - Technical & Engineering Expertise: more duties. - Stakeholder Engagement & Coordination: duties. - Continuous Learning & Skill Development: duties. - Required Qualification: bullet list. - EXAMPLES OF PHYSICAL DEMANDS: not needed? It's substantive but maybe not required sections; we could include under Requirements? But we should preserve all substantive info. However we must not create sections that are not in the list of allowed headings. The allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can put physical demands under Requirements or Qualifications? Probably under Requirements (experience, education) or Skills. But we need to decide. We have info about schedule: hours Monday-Friday 8am-5pm or 9am-6pm local time. That's schedule info. So we can include a Schedule section. Pay: Not mentioned explicitly; there is a note about salary range required by California Pay Transparency Act but says it's for Irvine, CA and may differ. That's not a specific salary range for this posting; it's generic. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does not state a specific salary range; it mentions that the salary range shared is for Irvine, CA and may differ. That's not a concrete figure. Likely we should not include Pay section because no actual numbers given. So omit Pay. Benefits: Not mentioned explicitly; there is mention of "full range of medical, dental, and/or other benefits" but that's generic. It says "An additional discretionary bonus structure or incentives may be offered as part of the overall compensation package, in addition to the full range of medical, dental, and/or other benefits, dependent on the level and position offered." That's still generic, not specific. Probably we should not include Benefits section because no concrete benefits listed. The instruction: never create Benefits sections unless posting actually states them. It does mention benefits in general but not specific. I'd argue it's not specific enough; better to omit. Thus sections: About the role (summary), Responsibilities (essential job function & responsibilities + technical & engineering expertise + stakeholder engagement + continuous learning), Requirements (required qualification + physical demands + work authorization etc?), Qualifications (maybe education/certifications?), Skills (maybe specific skills like programming relays, protocols, IT networks, cybersecurity, Visio, etc). But we need to avoid duplication. Let's map: - About the role: summary paragraph. - Responsibilities: list of duties from Essential Job Function & Responsibilities, Technical & Engineering Expertise, Stakeholder Engagement & Coordination, Continuous Learning & Skill Development. - Requirements: maybe work authorization, travel %, location, remote status, hours? Actually schedule is separate. Requirements could include: 2+ years experience, Bachelor's degree, hands-on experience with relays, SCADA protocols, IT networks, cybersecurity, electrical generation, Visio, certifications (CCNA preferred), authorized to work in US, no visa sponsorship, travel up to 30%, remote work (Houston, TX). Also physical demands maybe. - Qualifications: maybe education and certifications? But we already included degree in Requirements. Could separate: Qualifications: Bachelor's degree in Electrical, Software, or Systems Engineering; Certifications: Networking certifications (CCNA preferred). But we need to avoid duplication. Perhaps better: Requirements: experience and skills; Qualifications: education and certifications. Skills: specific technical skills (programming relays, SCADA protocols, IT networks, cybersecurity, Visio). However the instruction says prefer a few substantive sections over many thin ones. So we might combine into fewer sections: About the role, Responsibilities, Requirements (including experience, education, certifications, skills, physical demands, work auth, travel). That may be enough. But we need to include Schedule section because we have schedule info. So we will have About the role, Responsibilities, Requirements, Schedule. We must not include Benefits or Pay. Now we need to format using

for section headings. Use

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

  for prose. We must preserve all substantive information. Let's extract details. About the role: summary paragraph: "The SCADA Engineer Level 2 supports SCADA system design, development, and deployment for utility-scale solar PV and BESS projects. This role requires hands-on experience with SCADA programming, industrial protocols, IT networks, and cybersecurity. The Engineer Level 2 will work closely with senior engineers to configure and troubleshoot SCADA systems, ensuring reliable plant operation and secure data communication. This position reports to the Director of SME or another management personnel that the CEO of the Company may designate. This position is (remote) located in Houston, TX and hours are Monday through Friday, from 8:00am to 5:00pm or 9:00am to 6:00pm local time. This position is expected to travel up to 30%. Applicants must be authorized to work for any employer in the United States. We are unable to sponsor or take over sponsorship of an employment visa at this time." But note schedule info is also in summary; we might move schedule to separate Schedule section. However the summary includes schedule; we could keep schedule in About the role but then also have Schedule section duplicate. Better to separate: About the role summary without schedule/hours/travel? But we need to preserve all info; we can keep schedule info in Schedule section and not repeat in About the role. Let's craft About the role: core description without schedule/hours/travel/visa/auth? Actually those are also substantive; maybe keep them in Requirements. Let's think. We have sections: About the role (general description), Responsibilities (duties), Requirements (experience, education, certifications, skills, physical demands, work auth, travel, location, remote status), Schedule (hours). That seems logical. Thus About the role: "The SCADA Engineer Level 2 supports SCADA system design, development, and deployment for utility-scale solar PV and BESS projects. This role requires hands-on experience with SCADA programming, industrial protocols, IT networks, and cybersecurity. The Engineer Level 2 will work closely with senior engineers to configure and troubleshoot SCADA systems, ensuring reliable plant operation and secure data communication. This position reports to the Director of SME or another management personnel that the CEO of the Company may designate." Now Responsibilities: list all duties from Essential Job Function & Responsibilities, Technical & Engineering Expertise, Stakeholder Engagement & Coordination, Continuous Learning & Skill Development. Let's extract bullet points: Essential Job Function & Responsibilities: - Hands-on experience with programming relays and control devices for power plant automation. - Configure and troubleshoot SCADA communication protocols such as Modbus, DNP3, and IEC 61850. - Assist in SCADA system architecture planning, integration, and cybersecurity implementation. - Work with IT networks and cybersecurity principles, ensuring SCADA system security compliance. - Assist in SCADA system documentation, including network diagrams, system configurations, and cybersecurity guidelines. Technical & Engineering Expertise: - Perform diagnostics and troubleshooting on SCADA communication failures, control system malfunctions, and network vulnerabilities. - Work with SCADA, EMS, and HMI tools to optimize remote monitoring and plant automation. - Provide technical support during site commissioning, factory acceptance tests (FAT), and remote troubleshooting efforts. Stakeholder Engagement & Coordination: - Collaborate with EPC contractors, vendors, and utilities to support SCADA project implementation. - Assist in preparing regulatory compliance documentation for SCADA system approvals. Continuous Learning & Skill Development: - Develop a stronger understanding of cybersecurity risks and IT networking best practices for SCADA systems. - Stay updated on SCADA technology advancements, automation improvements, and cybersecurity threats. We'll put each as

• . Now Requirements: include: - 2+ years of experience in SCADA, control systems, or IT networks. - Bachelor’s degree in Electrical, Software, or Systems Engineering. - Hands-on experience with or direct exposure to: * Programming relays and control devices. * SCADA systems and protocols (Modbus, DNP3, IEC 61850). * IT networks and cybersecurity principles. * Electrical generation and control systems for utility-scale solar or BESS projects. * Intermediate proficiency in Visio or similar tools. - Certifications: Networking certifications (CCNA preferred). - Applicants must be authorized to work for any employer in the United States. - Unable to sponsor or take over sponsorship of an employment visa at this time. - Expected to travel up to 30%. - Remote position located in Houston, TX. - Physical demands: (list from EXAMPLES OF PHYSICAL DEMANDS) * Stationary Position: frequently remains stationary up to 90% of the time and sitting up to 8 hours in a day * Move/Traverse: infrequently bend, stand, stoop and/or walk * Carry Weight: infrequently carry weight and/or lift objects (light to heavy) weighing up to 10 pounds * Hearing and Speech: frequently communicates with the ability to hear and talk on a regular basis with employees, coworkers, and all personnel matters; must be able to exchange accurate information in these situations * Sight: frequent use of sight to detect images on computer, office documents, and office objects near and far * Climb: occasionally ascends/descends on stairway to get to office upper and lower floors * Travel: up to 30% as needed We could combine travel mention already. We should preserve all substantive info; we can include physical demands as a list under Requirements. Now Schedule: hours Monday through Friday, from 8:00am to 5:00pm or 9:00am to 6:00pm local time. We should not include any boilerplate like EEO, legal, etc. Now produce HTML fragment:

  About the role

  ...

  Responsibilities

  • ...