Underground Foreperson

The user wants me to reformat a job posting into clean semantic HTML. I need to follow the rules carefully: 1. Use

for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) 2. Use

• for lists,

  for prose 3. Do NOT repeat job title as heading 4. Do NOT put Job ID/requisition numbers as headings 5. Preserve ALL substantive information 6. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions) 7. Include a section ONLY when there's real specific content - never emit heading with filler/placeholder text 8. Never create Pay/Schedule/Benefits sections unless posting actually states them 9. Output ONLY HTML fragment - no /, no markdown code fences Let me analyze the posting: - Job title: "Underground Foreperson" (don't repeat as heading) - Job Type: Full-Time +, Non-Exempt (could go in a short p or Schedule section) - Pay: "Competitive Hourly" - this is stated, so Pay section is appropriate - Benefits: listed (Company-sponsored Retirement Plan, Health Insurance, Employee Assistance Program, Life/long-term/short-term disability insurance) - Benefits section appropriate - Essential Functions & Responsibilities: long list - Responsibilities section - Minimum Qualifications: list - Requirements/Qualifications section - Education & Experience: list - Qualifications/Education section - Pre-Screen: drug screen, background, MVR check - could be part of Requirements - License & Certifications: CDL required - Requirements - Physical Requirements: detailed breakdown - Requirements/Physical Requirements section - ADA accommodation contact - boilerplate, remove - E-Verify - boilerplate, remove - Equal Opportunity Employer - boilerplate, remove - Important Information For Applicants - mostly boilerplate, but some compensation info: "Compensation determination is based on market data, job scope and individual qualifications. We offer a competitive total rewards package inclusive of health and welfare and retirement benefits, as well as paid time off and holiday pay benefits." This adds to Pay/Benefits. I need to structure sections logically. The posting has: - About the role (intro paragraph) - Pay (Competitive Hourly) - Benefits (list) - Responsibilities (long list) - Requirements/Qualifications (multiple subsections: Minimum Qualifications, Education & Experience, License & Certifications, Physical Requirements, Pre-Screen) I'll create sections: About the role, Pay, Benefits, Responsibilities, Requirements (with sub-lists for different requirement types). Note: The rules say use

  for section headings like "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". I should use those exact headings where appropriate. Let me draft:

  About the role

  This position ensures the productivity of daily operations, working closely with management to determine recruiting/hiring needs, deadlines, and safety protocols to enforce among the crew. The Foreperson is responsible for troubleshooting routine job site issues and engages all employees/contractors on required training, managing, and mentoring.

  Pay

  Competitive hourly wage. Compensation determination is based on market data, job scope, and individual qualifications.

  Benefits

  • Company-sponsored Retirement Plan
  • Health Insurance (Medical/Dental/Vision)
  • Employee Assistance Program
  • Life, long-term/short-term disability insurance
  • Paid time off and holiday pay

  Responsibilities

  • Plans, coordinates, and assigns daily work for the crew after receiving/interpreting orders from a General Foreperson/Line Clearance Supervisor.
  • Conducts field training/retraining, instructing crew on new or revised job units.
  • Enforces safe work practices as specified by experience, judgment, company policy, and OSHA; conducts safety training in accordance with company policies and procedures.
  • Discusses with property owner/customer(s) issues such as obtaining access, power interruption, work to be done, and responsibility for apparent property damage; refers controversial cases to the General Foreperson.
  • Obtains oral or written permission from property owners to perform required work.
  • Promotes and maintains good customer and public relations through effective completion of assigned work and appropriate behavior of employees on the crew.
  • May be delegated authority to investigate incident reports, damage claims, etc., and to settle minor damage claims.
  • Maintains accurate records, timesheets, and reports related to crew operation performance.
  • Controls crew costs, including effective use of people-power, work methods, and equipment operation.
  • Furnishes General Foreperson and utility representative with reports of orders completed, units of work completed, crew time, minor damage repairs and distribution, etc.
  • Periodically furnishes reports on incidents, truck breakdowns, private property damage, new employee follow-up, etc.
  • Cooperates with customers, police, and fire departments when blocking streets or driveways.
  • Sets up barriers, warning signs, flags, markers, etc., to protect employees and safeguard the public from hazards.
  • In emergencies, determines action to be taken to eliminate hazards to life and property.
  • Inspects and makes or provides for necessary repairs to tools, trucks, and other equipment.
  • Maintains good housekeeping on the truck and at work location.
  • Responsible for DOT maintenance and inspection requirements on all required vehicles.
  • Keeps informed regarding new equipment, specifications, standard practices, operating procedures, and customer and company employee relations policies and practices, including EEO and AA policies; requests repair or replacement when necessary.

  Requirements

  Minimum Qualifications

  • Understanding of drawings and symbols representing lines, voltages, line equipment, etc.
  • Excellent communication and leadership skills.
  • Organization skills and ability to multi-task.
  • Capable of adjusting to field requirements and taking independent action without close supervision.
  • Ability to safely drive an approved company vehicle.
  • Ability to work with hands above head for extended periods.
  • Weight should not exceed approximately 300 pounds (due to equipment capacity).
  • No fear of heights.
  • Willingness to travel for storm work.

  Education & Experience

  • Must be 18 years or older.
  • High School Diploma or GED equivalent preferred.
  • Driver's License required.

  License & Certifications

  • Valid Commercial Driver's License (CDL) required.

  Pre-Employment Screening

  • Pre-employment drug screen.
  • Background check.
  • Motor Vehicle Record (MVR) check.

  Physical Requirements

  • Rare (less than 10%): crawling, climbing, gripping, lifting up to 50 lbs.
  • Occasional (up to 33%): standing, stooping, kneeling, squatting, body-twisting, sense of touch, manual dexterity, lifting over 10 lbs. to 50 lbs., reaching, range-of-motion, lifting, carrying, pushing, pulling, climbing ladders, climbing stairs, balancing.
  • Frequent (up to 66%): walking, sitting, climbing on/off truck, reading, lifting up to 10 lbs.
  • Continuous (up to 100%): speaking clearly, seeing distant, seeing, hearing-speech-range, depth-perception, color vision.

  Job Type: Full-Time, Non-Exempt.

  I should not include the ADA contact, E-Verify, EEO statements, unsolicited resumes note, etc. Those are boilerplate. Also note: The rules say "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." There's no Job ID here. The "Job Type: Full-Time +, Non-Exempt" I'll include as a short p at the end or in a Schedule section? The rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." It states Job Type, so maybe a Schedule section? But the example headings include Schedule. However, the posting doesn't have a detailed schedule, just "Full-Time +, Non-Exempt". I'll fold into a short p at the end or in About the role. I'll add a short p after Requirements. Also, the posting says "Pay: Competitive Hourly" and later "Compensation determination is based on market data...". I'll combine in Pay section. Now, ensure I use only

  for section headings. The rules say "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid

  for subsections, but to be safe, I'll use

  for main sections and maybe

  for subsections? The instruction says "use

  for section headings" and lists examples. It doesn't explicitly forbid other heading levels, but to follow the spirit, I'll use

  for all section headings, and for subsections I could use

  or just bold text. However, the example shows only

  . I'll use

  for main sections and for subsections I'll use

  but that might be against the rule. Better to keep flat: use

  for each major section, and within Requirements, use

  with bold labels or separate lists with

  headings. But the rule says "use

  for section headings". It doesn't say you can't use other tags. I'll use

  for the main sections: About the role, Pay, Benefits, Responsibilities, Requirements. Then within Requirements, I'll use

  for subcategories? The instruction says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It implies those are the section headings. So I should have those as

  . For subsections, I can use

  or just . I'll use

  for clarity, but to be safe, I'll use

  only for the main sections and use

  Minimum Qualifications

  etc. However, the rule says "use

  for section headings". It doesn't say "only use

  ". I think using

  for subsections is fine. But the output should be a clean HTML fragment. I'll use

  for main sections and

  for subsections. Alternatively, I could make each subsection a separate

  ? That would be too many. The rule says "Prefer a few substantive sections over many thin ones." So I'll keep Requirements as one section with sub-lists. I'll structure as:

  About the role

  ...

  Pay