Electrical General Foreman

We need to output HTML fragment with sections only if content present. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to parse the posting. First paragraph: "Whether you’re a recent grad..." is about the company, maybe "About the role"? Actually it's about Rosendin, not role specifics. Could be "About the role" but maybe better as "About the role" includes description of role? The posting includes "Your Next Opportunity The General Foreman is responsible..." That's role description. So we can put that under

About the role

with paragraphs. Then "What You’ll Do" is responsibilities ->

Responsibilities

with

• each bullet. Then "What You Bring To Us" is requirements/qualifications/skills. We need to split maybe into Requirements and Skills. But we can combine into Requirements (or Qualifications). The instruction: prefer few substantive sections over many thin ones. So we could have one section for Requirements (or Qualifications) that includes all bullet points. Could also separate Skills but better to keep one. We have Benefits section: "Benefits Robust healthcare..." etc. So

  Benefits

  with
  • . Physical Demands And Work Environment: Not a standard heading; we could maybe include under Requirements? But it's not listed as allowed headings. The allowed headings are only those eight. We should not create other headings. So we need to decide where to put that info. Could be omitted? But we must preserve ALL substantive information. However we cannot create new headings not in list. Could we put it under a paragraph within an existing section? Possibly under Requirements or About the role? But it's not about role. Could be under Requirements as "Physical Demands". But that would be mixing. 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, 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 must fit all content into those sections. Physical Demands could go under Requirements or maybe under About the role? Probably under Requirements as it's a requirement of the job. We'll include as a

    within Requirements. Pay and Schedule: Not mentioned explicitly except "40-hour workweek is normal, however, if offered, working overtime may be included; electricians may work nights or weekends Overtime opportunities". That's schedule info. So we can create a Schedule section with that. Pay: Not mentioned besides "competitive compensation". That's vague; we should not create Pay section unless posting actually states them. It says "competitive compensation" but no specifics. According to rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. For Pay, we have only "competitive compensation" which is not specific; maybe we should not create Pay section. For Schedule, we have specifics about 40-hour workweek, overtime, nights/weekends. So we can create Schedule section. Benefits we have specifics: robust healthcare and retirement benefit package, opportunity for every skill level, contractor provided power tools, overtime opportunities, well rounded training for next levels, industry leading project opportunities, travel opportunities are available. So Benefits section. Now we need to remove boilerplate: EEO statements, duplicated lines, etc. Also remove "Rosendin is committed to creating a diverse environment..." repeated twice. Remove navigation etc. Now craft HTML. Structure:

    About the role

    Whether you’re a recent grad or a seasoned professional, you can experience meaningful career growth at Rosendin. Enjoy a true sense of ownership as you work with a proven industry leader on some of the most exciting and high-profile projects in the nation. We offer a wide range of job opportunities, competitive compensation, full benefits, an Employee Stock Ownership Plan and more. Why Rosendin? Committed. Innovative. Engaged. If you’re looking to take your career to the next level and work with some of the best and brightest in the industry, we want to hear from you. Since our founding over 100+ years ago, Rosendin has been driven to positively impact the communities where we live and work. We are an organization built on integrity and we have a culture that empowers people, embraces diversity, and inspires everyone to do their best.

    Your Next Opportunity The General Foreman is responsible for Rosendin; managing the labor, materials and production for electrical construction projects. Provide technical expertise in installing and troubleshooting electrical wiring and equipment. Work cooperatively with the general contractor and/or customer in managing the project, project schedule and employees. Monitor installations and ensure work is performed according Rosendin standards and project specifications.

    Then Responsibilities:

    Responsibilities

    • Responsible for supervision of all field production activities; provide assistance to the Foreman in planning the job, ordering materials and manpower.
    • Work with appropriate Project Managers and Superintendents to establish project goals at the beginning of the project and monitor success in reaching those objectives on an ongoing basis.
    • Review and monitor labor efficiencies, hours and ratios.
    • Project the labor needs for the duration of the project
    • Monitor codes and specifications, installation methods.
    • Prepare, review, distribute and/or maintain all required installation documentation.
    • Provide leadership and guidance to Foremen.
    • Work with the appropriate Project Managers and Superintendents to track and monitor material costs, storage, consumed and ordered to identify potential problems while minimizing cost and overruns to Rosendin
    • Achieve Rosendin productivity objectives by effectively managing and assigning tasks to crew members, while maintaining an accurate labor tracking log and communicating with other key project personnel
    • Utilize a proactive approach to anticipate and resolve potential issues.
    • Ensure the proper safety equipment, materials and tools are onsite to perform required work.
    • Maintain complete and accurate “as-builts” as per Rosendin procedures and project requirements.
    • Communicate effectively with a wide range of individuals including project owners, architects, general contractors, management, crew members, etc.
    • Adhere to project contract document changes and Rosendin change order notice-to-proceed policies.
    • Adhere to all Rosendin, state and federal safety policies and procedures.
    • Ensure all work performed meets with NEC, federal, state, county, local codes and contract documents.
    Then Requirements/Qualifications/Skills: We'll make a section

    Requirements

    (or Qualifications). Since we have many bullet points, we can put as
    • . Also include Physical Demands as a

      maybe after list. Content from "What You Bring To Us": - State Issued Electrical license, where applicable by state requirement - 5 years of Electrical Experience - A minimum of three to five years of experience working as an Electrical Foreman/General Foreman or in a similar role in electrical construction, design and cost management for commercial or industrial projects. - Advanced abilities in reading and interpreting electrical plans and specifications with in-depth knowledge of the NFPA codes. - Demonstrated track record of successful project leadership with experience managing sub-Foremen. - Capable of managing any type of private or public sector electrical construction project including new construction, tenant improvements, etc. - Solid understanding of the electrical codes and installation methods. - Well-versed in the installation of power systems: lighting, fire protection, security and data networks. - Knowledgeable regarding the build, installation and maintenance of control panels - Comfortable utilizing Electrical Single Line blueprints. - Experience in verifying the compliance and functionality of installations. - Knowledgeable in the identification and repair of faults in electrical apparatus and circuits. - Demonstrated ability to effectively order and track materials, perform cost projections and develop “as-builts”. - Strong knowledge and experience related to scheduling, material lead times, product knowledge and installation durations. We'll list each as

    • . Then Physical Demands And Work Environment: We'll put as a

      after the list, maybe with two paragraphs: Physical Demands and Working Environment. Physical Demands: list of abilities. We'll convert to a paragraph summarizing? But we must preserve ALL substantive information; we cannot summarize away detail. We could keep as a

      • but that's not a standard heading; but we can embed a
        inside the Requirements section? The instruction: Use
        • for any list of duties/requirements/benefits, and

          for prose. So we can use

          • for the physical demands list as well. That's okay. Thus after the requirements list, we can add another
            • for Physical Demands and another for Working Environment. But we need to keep within the same section? It's okay to have multiple lists. We'll add:

              Requirements

              • State Issued Electrical license, where applicable by state requirement
              • 5 years of Electrical Experience
              ... etc ...

              Physical Demands

              ? Not allowed. We could just continue with

              but we need to preserve list. Could use

              • directly after the previous list without a heading; that's okay as it's still a list of requirements. But to differentiate we could add a

                heading like "Physical Demands:" as prose then list. However headings besides h3 not allowed? Not specified; we can use

                for prose, so we can have a

                Physical Demands:

                then
                • ... That seems acceptable. Similarly for Working Environment. Thus:

                  Physical Demands:

                  • Perform ladder climbing, wire pulling, and conduit installation.
                  • Walks, climbs, lifts, squats, crawls, kneels, pushes, pulls, and reaches overhead on a routine and repetitive basis
                  • Maintain a standing position for long periods of time while performing repetitive actions such as grasping or manipulating wires.
                  • Lift 50 lbs. from the ground and pull 50 lbs. of force
                  • Must have use of feet, legs, hands, and arms to climb and/or balance on scaffolding or ladders
                  • Must have use of arms, hands, and fingers to reach, handle, and feel cable, wires, tools, and other equipment
                  • Must be able to work off of ladders, man lifts, or reach booms without fear of heights.
                  • Must be able to see and hear, or have corrected vision, both close and distant, and hearing
                  • Must be able to distinguish color-coded wires
                  • Must be able to adjust vision focus and use peripheral vision and depth perception.

                  Working Environment:

                  • While performing duties of this job, the employee may be exposed to: A variety of weather conditions including cold, snow, rain, heat, etc.
                  • High noise levels
                  • Work is sometimes noisy, cramped, and dirty
                  • Hazards include risk of electrical shock and other work-site accidents
                  • 40-hour workweek is normal, however, if offered, working overtime may be included; electricians may work nights or weekends
                  • Overtime opportunities
                  But note we already have Schedule section for overtime etc. We might duplicate. Better to put schedule info in Schedule section, not here. So we should extract schedule info: "40-hour workweek is normal, however,