HV SCADA Engineer II (Remote)
SOLV Energy · Oklahoma, United States · 1 mo ago
RemoteRemoteEngineering$96k–$120k/yrFull-time
We need to output HTML fragment with sections: About the role? The posting includes a job description summary and description. We need to use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO, legal, application instructions, etc. Must preserve all substantive info.
We need to parse content:
- Job Description Summary: "SOLV Energy is a leading provider... Job Description Summary: The HV SCADA Engineer II will provide intermediate level engineering support for the design, configuration, testing, and commissioning of high voltage (HV) SCADA systems on utility scale renewable and substations projects, supporting EPC delivery under established standards and supervision. This role can be fully remote or located in one of our offices in Bend, OR, San Diego, CA, or Raleigh, NC. Specific location details and expectations will be discussed during the interview process."
That's about the role. Could be "About the role" section.
- Job Description: includes responsibilities list: bullet points after "Position Responsibilities and Duties:" then many sentences. We'll extract responsibilities as list items.
- Objectives or Goals to Measure Performance: could be considered "Performance Objectives" but not in allowed headings. Could be part of Responsibilities? Probably not needed. We could include under Responsibilities or maybe not. The instruction: Prefer a few substantive sections over many thin ones. We have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map content:
About the role: summary.
Responsibilities: list of duties.
Requirements: maybe "Minimum Skills or Experience Requirements" includes education, experience, abilities. Could be Requirements.
Qualifications: maybe overlapping with Requirements; but we can combine. However we need to decide: Use Requirements for education/experience, Skills for technical skills list. Qualifications maybe for certifications? Not present. Could skip Qualifications if no specific content.
Skills: list of technical skills: programming languages, software, protocols, etc.
Benefits: present: medical, dental, vision, basic life and disability insurance, 401(k), vacation, sick and holiday pay.
Pay: Compensation Range: $96,160 - $120,200 Pay Rate Type: Salary.
Schedule: Not explicitly given; maybe travel 20% onsite, remote possible. Could infer schedule? Not given explicit schedule like full-time, hours. Might not include Schedule section if no specific content. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. Pay is stated, Benefits stated, Schedule not explicitly stated (no mention of work hours, shift, etc). So we omit Schedule.
We also need to include location info maybe in About the role.
We must not include boilerplate: EEO, legal, unsolicited recruiter info, Job Number, etc.
We must preserve all substantive info: ensure we don't lose any details.
Let's extract details:
About the role:
- SOLV Energy is a leading provider of infrastructure services to the power industry, designing, building and maintaining utility scale solar, battery storage and high voltage substation projects nationwide.
- The HV SCADA Engineer II will provide intermediate level engineering support for the design, configuration, testing, and commissioning of high voltage (HV) SCADA systems on utility scale renewable and substations projects, supporting EPC delivery under established standards and supervision.
- This role can be fully remote or located in one of our offices in Bend, OR, San Diego, CA, or Raleigh, NC. Specific location details and expectations will be discussed during the interview process.
Responsibilities (list):
- Review and understand SCADA system requirements for substations connected to utility scale renewable energy projects including but not limited to; Solar PV, Battery Energy Storage Systems and Wind.
- Support HV SCADA system design development and drawings to meet project specifications.
- Verify substation points lists for accuracy against relay and meter settings files.
- Program and commission substation RTACs, Phasor Data Concentrators, and HMI systems.
- Coordinate network settings and IP assignments for substation equipment with plant network provider.
- Troubleshoot communication issues between substation devices and connected controllers.
- Provide technical support for diverse substation equipment configurations.
- Communicate effectively with customers, vendors, and field technicians for on-site commissioning and installation support.
- Compare project drawings to site conditions to ensure installation is correct.
- Travel for this position is required. Estimated to be 20% of job duties will be onsite.
- Identify and learn appropriate software and hardware used and supported by the organization.
- Work with project management to report project status, risks, and mitigation measures.
- Promote and adhere to a culture of NERC compliance and governance with respect to programming and commissioning standards, documentation, reporting, knowledge transfer and training.
- Provide continuous feedback to product development teams to improve the SOLV SCADA Platform.
- Ensure a safe working environment through strict adherence to and enforcement of company and industry safety standards.
Objectives or Goals to Measure Performance: Could be considered performance metrics; but not in allowed headings. Could be omitted or maybe included under Responsibilities? Might be considered part of responsibilities but it's separate. However we must preserve all substantive info; if we omit, we lose info. Could we incorporate into Responsibilities as additional bullet points? The instruction: Use
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO, legal, application instructions, etc. Must preserve all substantive info.
We need to parse content:
- Job Description Summary: "SOLV Energy is a leading provider... Job Description Summary: The HV SCADA Engineer II will provide intermediate level engineering support for the design, configuration, testing, and commissioning of high voltage (HV) SCADA systems on utility scale renewable and substations projects, supporting EPC delivery under established standards and supervision. This role can be fully remote or located in one of our offices in Bend, OR, San Diego, CA, or Raleigh, NC. Specific location details and expectations will be discussed during the interview process."
That's about the role. Could be "About the role" section.
- Job Description: includes responsibilities list: bullet points after "Position Responsibilities and Duties:" then many sentences. We'll extract responsibilities as list items.
- Objectives or Goals to Measure Performance: could be considered "Performance Objectives" but not in allowed headings. Could be part of Responsibilities? Probably not needed. We could include under Responsibilities or maybe not. The instruction: Prefer a few substantive sections over many thin ones. We have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map content:
About the role: summary.
Responsibilities: list of duties.
Requirements: maybe "Minimum Skills or Experience Requirements" includes education, experience, abilities. Could be Requirements.
Qualifications: maybe overlapping with Requirements; but we can combine. However we need to decide: Use Requirements for education/experience, Skills for technical skills list. Qualifications maybe for certifications? Not present. Could skip Qualifications if no specific content.
Skills: list of technical skills: programming languages, software, protocols, etc.
Benefits: present: medical, dental, vision, basic life and disability insurance, 401(k), vacation, sick and holiday pay.
Pay: Compensation Range: $96,160 - $120,200 Pay Rate Type: Salary.
Schedule: Not explicitly given; maybe travel 20% onsite, remote possible. Could infer schedule? Not given explicit schedule like full-time, hours. Might not include Schedule section if no specific content. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. Pay is stated, Benefits stated, Schedule not explicitly stated (no mention of work hours, shift, etc). So we omit Schedule.
We also need to include location info maybe in About the role.
We must not include boilerplate: EEO, legal, unsolicited recruiter info, Job Number, etc.
We must preserve all substantive info: ensure we don't lose any details.
Let's extract details:
About the role:
- SOLV Energy is a leading provider of infrastructure services to the power industry, designing, building and maintaining utility scale solar, battery storage and high voltage substation projects nationwide.
- The HV SCADA Engineer II will provide intermediate level engineering support for the design, configuration, testing, and commissioning of high voltage (HV) SCADA systems on utility scale renewable and substations projects, supporting EPC delivery under established standards and supervision.
- This role can be fully remote or located in one of our offices in Bend, OR, San Diego, CA, or Raleigh, NC. Specific location details and expectations will be discussed during the interview process.
Responsibilities (list):
- Review and understand SCADA system requirements for substations connected to utility scale renewable energy projects including but not limited to; Solar PV, Battery Energy Storage Systems and Wind.
- Support HV SCADA system design development and drawings to meet project specifications.
- Verify substation points lists for accuracy against relay and meter settings files.
- Program and commission substation RTACs, Phasor Data Concentrators, and HMI systems.
- Coordinate network settings and IP assignments for substation equipment with plant network provider.
- Troubleshoot communication issues between substation devices and connected controllers.
- Provide technical support for diverse substation equipment configurations.
- Communicate effectively with customers, vendors, and field technicians for on-site commissioning and installation support.
- Compare project drawings to site conditions to ensure installation is correct.
- Travel for this position is required. Estimated to be 20% of job duties will be onsite.
- Identify and learn appropriate software and hardware used and supported by the organization.
- Work with project management to report project status, risks, and mitigation measures.
- Promote and adhere to a culture of NERC compliance and governance with respect to programming and commissioning standards, documentation, reporting, knowledge transfer and training.
- Provide continuous feedback to product development teams to improve the SOLV SCADA Platform.
- Ensure a safe working environment through strict adherence to and enforcement of company and industry safety standards.
Objectives or Goals to Measure Performance: Could be considered performance metrics; but not in allowed headings. Could be omitted or maybe included under Responsibilities? Might be considered part of responsibilities but it's separate. However we must preserve all substantive info; if we omit, we lose info. Could we incorporate into Responsibilities as additional bullet points? The instruction: Use - for any list of duties/requirements/benefits. So we could add those objectives as list items under Responsibilities as they are duties/goals. That would preserve them.
Thus under Responsibilities we can include also:
- Assigned HV SCADA design, programming, and commissioning tasks are completed accurately and on schedule.
- SCADA configurations and testing activities comply with utility, NERC, and SOLV standards.
- Adherence to Company policies and procedures
- Understanding of and adherence to safety and quality procedures and practices
- Communication and data integration issues are resolved with increasing independence.
- Professional technical skills and industry knowledge continue to develop over time.
- Staff development and training
- Positive feedback is received from project teams, field personnel, and stakeholders.
- Effective utilization of project management, scheduling, and task management tools.
But note some are phrased as objectives; still okay.
Minimum Skills or Experience Requirements (Requirements):
- Bachelor’s degree in Electrical Engineering, Controls Engineering, or related technical discipline preferred.
- 2 - 4 years of SCADA engineering experience (experience working with substation SCADA systems preferred).
- Ability to read and understand engineering design drawings including but not limited to; Electrical Single-line, Equipment Layout Drawings, Communications Diagrams & Panel Drawings.
- Knowledge of power distribution protection equipment including protection relays and power meters.
- Experience coordinating with Utility Companies for point of demarcation, interconnect agreements, design standards compliance, etc
- Experience with programming languages including but not limited to; C, C++, Java, Python, Structured Text (IEC61131-3) desired.
- Experience working with SEL’s acSELerator RTAC and acSELerator Quickset software
- Experience with Ignition SCADA software or other HMI design software
- Knowledge of design, installation and commissioning of SCADA networks using; Fiber Optics, Serial RS-232 / RS-485, and Ethernet TCP/IP.
- Experience working with industry recognized PLC equipment including but not limited to Schweitzer Engineering RTAC Platform, Allen Bradley Control / CompactLogix platform, GE / Emerson RX3i, or similar PLC environments.
- Experience with basic PV solar monitoring, functions, and designs desired but not required. (Technical experience in related fields will be considered).
- Understanding of industrial automation protocols (Modbus RTU/TCP, DNP3, OPC UA and DA).
- Understanding of power plant operating procedures.
- Ability to work with sub-contractors and field personnel.
- Experience with various project management, scheduling, and task management tools.
- Excellent communications skills.
Physical Demands and Environmental Conditions: This is substantive info about work conditions. Not covered by allowed headings. Could be placed under Responsibilities? Not exactly. Could be a separate section but not in allowed list. However we could incorporate into About the role? Might be okay to add a section "Working Conditions" but not allowed. The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples but we should use those headings. It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should limit to those headings. It doesn't say we cannot add other headings, but likely they expect only those. Safer to stick to those.
Thus we need to fit Physical Demands somewhere. Could be part of Responsibilities? Not really. Could be part of About the role? Might be okay to add a paragraph under About the role describing work environment. The About the role section can contain prose (
) and we can include that info there.
Thus About the role paragraph can include: SOLV Energy description, role summary, location, and also physical demands and environmental conditions.
We must preserve all substantive info; we can embed physical demands in About the role.
Now Skills: we need to list technical skills: programming languages, software, protocols, etc. Many of those are already in Requirements; but we can separate: Requirements for education/experience, Skills for technical proficiencies.
Thus we need to parse Requirements: education, years experience, ability to read drawings, knowledge of protection equipment, experience coordinating with utilities, ability to work with subcontractors, experience with project management tools, excellent communication skills.
Skills: programming languages, SEL software, Ignition SCADA, network design, PLC equipment, PV solar monitoring (desired), industrial automation protocols, power plant operating procedures.
We must avoid duplication but preserve all info; duplication is okay if it's same content but we should not invent. Could list both.
Now Benefits: list.
Pay: compensation range and salary type.
Now we need to output HTML fragment only.
Structure:
About the role
...
Responsibilities
- ...
...
Requirements
- ...
...
Skills
- ...
...
Benefits
- ...
...
Pay
...
No Schedule.
Make sure not to include any boilerplate like EEO, legal, Job Number, unsolicited recruiter, etc.
Check for any leftover boilerplate: The posting includes "SOLV Energy Is an Equal Opportunity Employer..." etc. Must remove.
Also remove "Applicants must be legally authorized to work in the U.S. without requiring employer sponsorship now or in the future." That's substantive? It's a requirement about work authorization. Could be included under Requirements maybe. It's a requirement. Should we include? It's substantive. It's not boilerplate; it's a requirement. So we should include under Requirements.
Also "SOLV Energy does not accept unsolicited candidate introductions..." is boilerplate/legal; remove.
Now ensure we preserve location info: remote or offices in Bend, OR; San Diego, CA; Raleigh, NC.
Now check for any duplicated lines: we must not repeat same content unnecessarily but okay.
Now craft the HTML.
Let's write About the role paragraph:
SOLV Energy is a leading provider of infrastructure services to the power industry, designing, building and maintaining utility scale solar, battery storage and high voltage substation projects nationwide. The HV SCADA Engineer II will provide intermediate level engineering support for the design, configuration, testing, and commissioning of high voltage (HV) SCADA systems on utility scale renewable and substations projects
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples but we should use those headings. It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should limit to those headings. It doesn't say we cannot add other headings, but likely they expect only those. Safer to stick to those.
Thus we need to fit Physical Demands somewhere. Could be part of Responsibilities? Not really. Could be part of About the role? Might be okay to add a paragraph under About the role describing work environment. The About the role section can contain prose (
) and we can include that info there. Thus About the role paragraph can include: SOLV Energy description, role summary, location, and also physical demands and environmental conditions. We must preserve all substantive info; we can embed physical demands in About the role. Now Skills: we need to list technical skills: programming languages, software, protocols, etc. Many of those are already in Requirements; but we can separate: Requirements for education/experience, Skills for technical proficiencies. Thus we need to parse Requirements: education, years experience, ability to read drawings, knowledge of protection equipment, experience coordinating with utilities, ability to work with subcontractors, experience with project management tools, excellent communication skills. Skills: programming languages, SEL software, Ignition SCADA, network design, PLC equipment, PV solar monitoring (desired), industrial automation protocols, power plant operating procedures. We must avoid duplication but preserve all info; duplication is okay if it's same content but we should not invent. Could list both. Now Benefits: list. Pay: compensation range and salary type. Now we need to output HTML fragment only. Structure:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Skills
- ... ...
Benefits
- ... ...
Pay
...
No Schedule. Make sure not to include any boilerplate like EEO, legal, Job Number, unsolicited recruiter, etc. Check for any leftover boilerplate: The posting includes "SOLV Energy Is an Equal Opportunity Employer..." etc. Must remove. Also remove "Applicants must be legally authorized to work in the U.S. without requiring employer sponsorship now or in the future." That's substantive? It's a requirement about work authorization. Could be included under Requirements maybe. It's a requirement. Should we include? It's substantive. It's not boilerplate; it's a requirement. So we should include under Requirements. Also "SOLV Energy does not accept unsolicited candidate introductions..." is boilerplate/legal; remove. Now ensure we preserve location info: remote or offices in Bend, OR; San Diego, CA; Raleigh, NC. Now check for any duplicated lines: we must not repeat same content unnecessarily but okay. Now craft the HTML. Let's write About the role paragraph: SOLV Energy is a leading provider of infrastructure services to the power industry, designing, building and maintaining utility scale solar, battery storage and high voltage substation projects nationwide. The HV SCADA Engineer II will provide intermediate level engineering support for the design, configuration, testing, and commissioning of high voltage (HV) SCADA systems on utility scale renewable and substations projects