Utility BESS Technician II - (Marana, AZ)

We need to output HTML fragment with sections: About the role? Actually the posting includes "About NovaSource" description, then "Basic Job Functions", "Experience", "Education", "Physical Requirements", "Required Skills/Competencies", "Essential Responsibilities", "Reporting Relationships", "Travel", "Benefits", "Office Physical Requirements", then EEO etc. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove "NovaSource is committed to compliance..." etc. Also remove "Potential candidates will meet..." etc. Also remove "US: Diversity Statement – Equal Employment Opportunity" etc. We need to include sections only when posting has real, specific content. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we need to map content to these headings appropriately. The instructions: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should use those exact headings when appropriate. Not repeat job title as heading. Do not put Job ID etc. We need to decide which sections to include based on content. We have: - About NovaSource: description of company. Could map to "About the role"? Actually "About the role" is more about the job, but we have company description. Could still use "About the role" heading and put company overview there? Might be okay. But maybe better to use "About the role" for role description (Basic Job Functions). However we have separate sections for responsibilities etc. The instruction says use those headings as examples; we can use them if we have content. We need to decide which sections to include. We have content for: - Basic Job Functions (duties) -> could be Responsibilities. - Experience -> Requirements/Qualifications. - Education -> Qualifications. - Physical Requirements -> maybe Requirements? Could be separate but we might not have a specific heading for Physical Requirements; we could include under Requirements or Qualifications? The instruction says we can use those headings; we can also add other headings? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings; not that we cannot use others, but likely we should stick to those. However we have Physical Requirements content; we could put under Requirements or Qualifications? Might be better to include a "Requirements" section covering experience, education, physical requirements, skills. But we also have separate "Required Skills/Competencies". Could combine. We also have "Essential Responsibilities" which is more detailed duties. We have "Reporting Relationships" maybe not needed. We have "Travel" -> could be Schedule? Actually travel is not schedule; but we could include under Schedule if there is schedule info (none). There's no explicit schedule (like shift, hours). So we should not create Schedule section unless posting actually states them. It does not state schedule, so we should not include Schedule. Pay: Not mentioned explicitly; only "Competitive Pay + Paid Time Off (PTO)" under Benefits. So we have pay mentioned as "Competitive Pay". That is specific enough? It says "Competitive Pay + Paid Time Off (PTO)". That is a statement about pay. So we can include a Pay section with that content. However we also have Benefits section with details. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Pay is stated as "Competitive Pay". So we can include Pay section with that line. Benefits section is definitely present. Thus we will have sections: - About the role (company overview + maybe basic job functions? But we also have Responsibilities separate.) Better to follow typical structure: About the role (company overview), Responsibilities (Essential Responsibilities + Basic Job Functions), Requirements (Experience + Education + Physical Requirements), Qualifications (maybe certifications?), Skills (Required Skills/Competencies), Benefits, Pay. We must not repeat job title as heading. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details, not just summary. We need to output only HTML fragment, no /, no markdown. We need to use

for each section heading, then content: use

for prose,

• for lists. We need to preserve all substantive information: that means we should not omit details like specific duties, etc. We need to include them. We must remove boilerplate: EEO statements, legal compliance, diversity statement, etc. Also remove "Office Physical Requirements" maybe? That is similar to Physical Requirements but for office; but we have Physical Requirements for field role. The "Office Physical Requirements" is generic and maybe boilerplate? It's about office positions; but the role is field technician. Might be considered boilerplate? It's not directly about the role; but it's still in posting. However it's not EEO/legal; it's about office physical requirements. Might be considered not essential? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Office Physical Requirements is not those; but it's maybe generic. However we already have Physical Requirements for the role; we could keep that and ignore Office Physical Requirements as duplicate/less relevant. Might be considered duplicated lines? Not exactly duplicate but similar. Safer to omit Office Physical Requirements as it's generic and not specific to role. Also remove "NovaSource is committed to compliance..." etc. Also remove "Potential candidates will meet the education and experience requirements..." etc. Also remove "US: Diversity Statement – Equal Employment Opportunity" and following paragraphs. Also remove "Reporting Relationships" maybe? It's not boilerplate but could be considered metadata; but it's substantive? It's about reporting structure. Might be kept? The instruction: we can include sections only when posting has real, specific content. Reporting Relationships is specific content. However we don't have a heading for it in our allowed list. Could we include it under Requirements? Not really. Could we add a custom heading? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests using those. To be safe, we could incorporate Reporting Relationships into Responsibilities or Requirements? It's not exactly either. Might be okay to omit as it's not critical? But we must preserve ALL substantive information. So we cannot omit Reporting Relationships if it's substantive. However maybe it's considered minor metadata? The instruction says: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." Reporting Relationships might be considered minor metadata? It's about who you report to. Could be folded into a short

  under Responsibilities or About the role. The instruction says fold minor metadata into a short

  or drop it. So we can include a short paragraph under maybe About the role or Responsibilities. Similarly Travel: "Travel will be required depending on the needs of the Company." That's minor metadata; we can fold into a short

  under Responsibilities or Benefits? Probably under Responsibilities. Thus we will include sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. We need to ensure we don't create sections with filler like "commensurate with experience". We have specific content. Now let's extract content. About NovaSource paragraph: "NovaSource Power Services is the world’s #1-ranked solar operations and maintenance (O&M) provider and insight-driven total asset optimization partner for renewables asset owners ready to fuel smart growth. With over 20 years of operating experience and a presence on 5 continents, NovaSource has the global reach and strategic capabilities to achieve our clients’ renewables goals around the world. NovaSource’s comprehensive approach to total asset optimization in addition to O&M services includes value engineering, performance analysis, strategic supply chain management, and advanced monitoring systems. The company operates in key global markets managing over 30GW of solar power plants. NovaSource’s expertise extends beyond solar and includes battery energy storage systems (BESS), offering a complete suite of services for the evolving renewable energy landscape." We'll put that under About the role. Responsibilities: combine Basic Job Functions and Essential Responsibilities. Basic Job Functions: "Responsible for assigned aspects of the maintenance and operation of utility scale BESS power plant. Duties include monitoring BESS Plant operation through SCADA, commissioning, testing, inspecting, troubleshooting, repairing, and modifying AC and DC BESS systems, including inverters, BESS module arrays, transformers, switchgear, and metering systems." Essential Responsibilities list many items. We'll need to list them as

  • . Let's extract Essential Responsibilities bullet points: - Perform to quarterly key performance indicators, such as actual versus expected energy generation, on-time planned maintenance, and support overall plant and equipment efficiency. - Ensure a safe work environment by promoting strict adherence to company protocols. - Responsible for personal safety, quality and schedule adherence. - Comply with Job Hazard Analysis, Pre-Job Brief and Lock-Out-Tag-Out procedures. - With supervision be responsible for a variety of PM work including measuring, reading, testing and performing maintenance procedures on all site components. - Communicate effectively and professionally with internal and external stakeholders. - Assist in planning and executing on-site projects, installations, commissioning, quality inspections, and performance testing. - Assist with writing and enforcing work and equipment testing instructions and procedures, including normal and maintenance operating procedures. - Ensure work orders are complete in their entirety. - Ensure all documentation and required reports are reviewed, complete, submitted and filed. - Attend, participate in and pass all assigned training in safety, environmental and other areas as assigned. - Maintain work area and site housecleaning to 5S standards. - Verify SCADA site configuration. - Adhere to Company vehicle maintenance standards and safety standards. - Other duties as assigned. Also Basic Job Functions could be included as a paragraph or list. We'll combine: maybe a paragraph summarizing Basic Job Functions then list Essential Responsibilities. Requirements: include Experience, Education, Physical Requirements. Experience: "2+ years of experience in a related position or Journey level certification. Experience in operating and maintaining power plant electrical systems, SCADA and controls systems operation, troubleshooting advanced electrical components, and using procedures to perform equipment preventative and corrective maintenance preferred." Education: "High School Diploma or equivalent required. College or technical degree preferred. Electrical certifications, state, journeyman, etc. a plus. Equivalent training in military, utility, or power industry a plus." Physical Requirements: "Bending, kneeling, twisting, the ability to lift up to 70 pounds, the ability to climb ladders, and wear PPE for extended periods of time. Ability to work in high and low temperatures, sun exposure, and navigate on uneven ground on foot. Ability to differentiate between different colors to manage color-coded wiring. Good hand-eye coordination." We could also include "Valid Driver’s License." maybe under Requirements or Skills? It's listed under Required Skills/Competencies? Actually it's under Required Skills/Competencies? Let's see: after Physical Requirements, there is "Required Skills/Competencies" list includes many items, ending with "Valid Driver’s License. Ability to complete NovaSource Technician Qualification Standards successfully within 90 days of hire." So Driver's License is part of Required Skills/Competencies. Thus Requirements section will have Experience, Education, Physical Requirements as subpoints maybe as
    . Qualifications: maybe we can treat certifications etc. But we already included certifications under Education. Could combine Education and Qualifications. However we need a Qualifications section per instruction; we could put certifications, journeyman, etc. But we already have them in Education. To avoid duplication, we