Substation Technician C (GTC)

We need to output HTML fragment with sections: Use

for headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes Position Summary, Essential Functions, Minimum Requirements, Physical Demands, Work Environment, Competencies, About Us, About The Team. We need to map to headings: "About the role" could be Position Summary. "Responsibilities" could be Essential Functions. "Requirements" could be Minimum Requirements. "Qualifications" maybe not separate; we could combine with Requirements? But we need to follow instruction: use those headings only if content exists. We have content for Position Summary, Essential Functions, Minimum Requirements, Physical Demands, Work Environment, Competencies, About Us, About The Team. However headings list does not include Physical Demands, Work Environment, Competencies, About Us, About The Team. We could still use those headings? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we need to map content to those headings. If a section doesn't have content, we omit it. So we need to decide which of those headings have content. - About the role: Position Summary fits. - Responsibilities: Essential Functions fits. - Requirements: Minimum Requirements fits. - Qualifications: maybe we could put some of the competencies or knowledge? But Qualifications could include knowledge of substation structural drawings, ability to learn heavy equipment, etc. However Minimum Requirements already includes many. Could split but we should not invent. Better to not create Qualifications if no distinct content beyond Requirements. But we could treat "Knowledge of substation structural drawings..." as qualifications. However it's under Minimum Requirements list. Might be okay to keep under Requirements. - Skills: Could list competencies (Safety, Self-Motivated, etc.) as Skills. - Benefits: Not mentioned. No benefits specifics. So omit. - Pay: Not mentioned. Omit. - Schedule: Not mentioned (though mentions overtime, travel, schedule changes). Could we put schedule info under Schedule? The posting mentions "Schedules can change frequently and with short notice." "Willing to work over-time or long hours during emergency conditions". That's schedule-related. So we could create a Schedule section with that info. It's specific content. So include Schedule. Thus sections: About the role, Responsibilities, Requirements, Skills, Schedule. We need to use

• for any list of duties/requirements/benefits. For prose use

  . So we need to convert lists to

  • . For About the role (Position Summary) it's prose paragraph(s). We'll put in

    . Responsibilities (Essential Functions) includes a list of duties: "Works safely while performing construction, maintenance or repair, testing, adjusting and troubleshooting of substation equipment/systems. This work which includes, but is not limited to, work involving the following:" then a list of items separated by commas and line breaks. We'll turn that into

    • each item. Requirements (Minimum Requirements) is a list of bullet-like statements separated by periods. We'll turn each into
    • . Skills (Competencies) is a list of competencies separated by commas. We'll turn each into
    • . Schedule: includes statements about schedules changing frequently, willing to work overtime, long hours during emergency conditions, 90% Travel Required, etc. We'll turn into
      • . We must preserve all substantive information, not invent or summarize away detail. Must not repeat job title as heading. Must not put Job ID etc. Must remove boilerplate: EOE/Minorities/Females/Vet/Disabled Pike is a Non-union Company, NOTE about job description not all-inclusive, About Us, About The Team (these are not in allowed headings; we should omit them because they'd be extra sections not in list? The instruction says prefer a few substantive sections over many thin ones. It didn't forbid other headings, but said use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings; we could still add other headings but they'd deviate from examples. Safer to stick to those headings and omit About Us etc. However we must preserve ALL substantive information; omitting About Us would lose info. But maybe About Us is considered boilerplate? It's descriptive of company; maybe not essential to job. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." About Us is not listed as boilerplate to remove. But they also said "Prefer a few substantive sections over many thin ones." Could still include About Us under a heading like "About the role"? No. Could we incorporate About Us into About the role? Not appropriate. Could we create a section "About the company"? Not in allowed headings. Might be okay to add a heading like "About the company" but they didn't forbid other headings, just gave examples. However they said "use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This could be interpreted as you should use those headings for those sections; you could also use other headings if needed, but they gave examples. Safer to include About Us and About The Team as separate sections with

        but not in the list? Might be considered adding extra sections, which they said prefer few substantive sections over many thin ones. About Us and About The Team are substantive but could be combined into a single "About the company" section. However not in examples. I'd decide to omit About Us and About The Team to keep to allowed headings, risking loss of info. But the instruction says "Preserve ALL substantive information". That seems higher priority. So we need to preserve About Us and About The Team info. How to incorporate? Could we put them under "About the role"? Not really. Could we create a section "About the company" using

        About the company? The instruction didn't forbid; it just gave examples. I think it's acceptable to add a heading like "About the company". However they said "use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive. So we can add other headings as needed. We'll include About the company (combining About Us and About The Team) as a section. Thus sections: About the role, Responsibilities, Requirements, Skills, Schedule, About the company. Now we need to output only HTML fragment, no /, no markdown. Let's extract content precisely. Position Summary paragraph: "Substation Technician C is a non-exempt position on the construction, maintenance and repair of substation equipment / systems. Substation Technician C has a 2-4 year working knowledge of 525 kv and below substation equipment, apparatus, and wiring. This position requires work in confined spaces and elevated work areas, and works with various pieces of construction equipment specific to the trade. A Substation Technician C may work independently or with others and occasionally work long hours during emergency conditions. This position works at various locations. The position may also be required to travel to another state depending on customer demands." We'll put that in

        . Essential Functions: Start: "Essential Functions Works safely while performing construction, maintenance or repair, testing, adjusting and troubleshooting of substation equipment/systems. This work which includes, but is not limited to, work involving the following:" then list items separated by commas and line breaks. Let's list them: - Concrete Foundations, ground grids, and steel erection - Buswork (High and Low Voltage) - Airbreak / Hookstick Switches - Control Cable - Terminations (High / Low Voltage) - Control Buildings - Conduit and duck banks - Capacitor bank installations 23kv- 230 kv - Transformers, regulators and circuit breakers - Circuit Switchers, motor-operated and manual switches - Responsible for maintaining Company vehicles, test equipment and tools in good working conditions. - Frequently works with energized high voltage systems requiring skill and care to protect the lives of themselves and others. We need to ensure each item is a

        . Some items have internal commas; that's fine. Minimum Requirements list: Let's extract each requirement sentence. "Able to perform rigorous physical labor." "Must be capable of climbing and working at heights up to 125 feet above ground." "Must possess or be capable of obtaining a Commercial Drivers’ License." "Must supply own personal hand tools required by the company for this work." "Must supply own safety toed work boots." "Must be capable of lifting in excess of 50 lbs." "Must be capable of working in confined spaces/areas." "Must be able to work independently or with others." "Must be capable of learning to operate various types of heavy equipment :Bucket, derrick and boom trucksBackhoes, excavators and skid steer loadersArticulating Man-liftsPressure DiggersTrenchersTrack Crawler Loader/BackhoeRough Terrain Telescopic Forklifts" "Willing to work over-time or long hours during emergency conditions and/or when requested. Schedules can change frequently and with short notice." "90% Travel Required" "Capable of following Company safety rules and policies." "Must gain knowledge of construction standard practices, techniques, quality requirements, applicable codes and standards." "Must be capable of working in close proximity of energized substation equipment." "Knowledge of substation structural drawings (i.e. elevations, plan views, section views, grounding details, and foundation plans)." "Able to work for extended periods in various locations, when requested." "Willing to work over-time when requested." "Willing to work outside of the normal work schedule including weekends, holidays, and overtime as required for the position." Note some duplicates: "Willing to work over-time when requested." appears twice? We'll keep once. Physical Demands: paragraph: "The physical demands described here are representative of those that must be met by an employee to successfully perform the essential functions of this job. While performing the duties of this job, the employee is regularly required to talk or hear. The employee is frequently required to stand; walk; use hands to finger, handle and feel; and reach with hands and arms." We could put Physical Demands under Requirements? But we have no heading for it. Could incorporate into Requirements? Might be okay to add a section "Physical Demands" but not in examples. However we already have many sections; maybe we can incorporate Physical Demands into Requirements as it's about physical ability. But we already have Requirements list; we could add those sentences as list items under Requirements. However the instruction says use

        • for any list of duties/requirements/benefits. Physical Demands is a list of demands; could be added to Requirements. But we must preserve all info; adding to Requirements is fine. Work Environment: paragraph: "While performing the duties of this job, the employee is frequently exposed to fumes or airborne particles, moving mechanical parts and vibration. The employee is occasionally exposed to a variety of extreme conditions at construction job sites. The noise level in the work environment and job sites can be loud. This position is performed in outside weather conditions." Could also be added to Requirements or maybe to Schedule? Not ideal. Could create a section "Work Environment". Not in examples but we could add. However we already have many sections; maybe we can incorporate into Requirements as well? It's about environment, not requirements. Could add a section "