Transmission Utility Forester (Maintenance)

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. No job title heading. No Job ID etc. Remove boilerplate. We need to parse the description. Let's extract content: Description: "We are currently seeking a Transmission Utility Forester (Maintenance) to support Dominion Energy in Virginia. This is a field position, and candidates must have experience with environmental compliance in relation to land clearing and linear construction projects. We are looking for an energetic professional who enjoys working outdoors and values the freedom of working independently. If you enjoy a fast-paced environment and the challenges of a rewarding profession, consider a career in environmental compliance with AMS. Some of the most important characteristics of a Transmission Utility Forester (Maintenance) is that you are open-minded and able to engage in safe, constructive interactions with the public. You are accountable for advancing a culture of safety and excellence while providing quality and value to our customers and clients." That's about the role. What We Offer: list of benefits. What You Will Do: responsibilities. What You Need To Have: requirements/qualifications. What Would Be Amazing To Have: preferred qualifications/skills. WORKING ENVIRONMENT: maybe part of responsibilities or description but not a separate heading unless we have specific content. Could be part of responsibilities or qualifications? It's more about environment; maybe we can include under Responsibilities? But we have to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content. About the role: introductory paragraph(s) describing role, field position, etc. Responsibilities: "What You Will Do" list. Requirements: "What You Need To Have" (mandatory). Qualifications: maybe "What Would Be Amazing To Have" (preferred) could be Qualifications or Skills. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). So we can have Qualifications for preferred qualifications, Skills for specific skills like tree identification, map reading, communication, computer skills, travel ability. But we need to avoid duplication. Let's decide: - About the role: description paragraph. - Responsibilities: bullet list from "What You Will Do". - Requirements: bullet list from "What You Need To Have" (mandatory). - Qualifications: bullet list from "What Would Be Amazing To Have" (preferred). - Skills: maybe we can extract specific skills from Requirements and Preferred? But we already have those. Could combine? The instruction says prefer a few substantive sections over many thin ones. So maybe we don't need Skills separate if covered. But we need to include sections only when posting has real specific content. We have content for About the role, Responsibilities, Requirements, Qualifications, Benefits. Pay: "Industry competitive pay." That's specific? It says "Industry competitive pay." That's somewhat vague but it's a statement about pay. It's not "commensurate with experience" etc. It's a specific statement: Industry competitive pay. That could be considered Pay section content. Should we include Pay? It says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. "Industry competitive pay." is a statement about pay, albeit generic but it's stated. I'd include Pay section with that sentence. Benefits: we have a list under "What We Offer". That's specific. Schedule: not mentioned explicitly. No schedule info. So omit Schedule. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. We need to use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. We must not repeat job title as heading. Not include Job ID etc. We must preserve all substantive information; do not invent or summarize away detail. We need to extract each bullet precisely. Let's pull out details. About the role prose: combine the introductory paragraph(s) before "What We Offer". Let's capture: "We are currently seeking a Transmission Utility Forester (Maintenance) to support Dominion Energy in Virginia. This is a field position, and candidates must have experience with environmental compliance in relation to land clearing and linear construction projects. We are looking for an energetic professional who enjoys working outdoors and values the freedom of working independently. If you enjoy a fast-paced environment and the challenges of a rewarding profession, consider a career in environmental compliance with AMS. Some of the most important characteristics of a Transmission Utility Forester (Maintenance) is that you are open-minded and able to engage in safe, constructive interactions with the public. You are accountable for advancing a culture of safety and excellence while providing quality and value to our customers and clients." That's the about role. Responsibilities: list from "What You Will Do". Let's extract each bullet: - Provide oversight of ROW clearing operations. - Conduct Danger Tree assessments and supervise removals. - Ensure safe and reliable electric service delivery to the public. - Act as the subject matter expert regarding utility vegetation management (UVM), for clients, landowners, and other stakeholders. - Ensure tree crews are following proper safety and arboricultural practices and procedures. - Address customer concerns related to vegetation in and adjacent to utility easements. - Negotiate with customers for tree removal as prescribed. - Perform QA/QC inspections on completed vegetation management work. - Identify vegetative threats to safe & reliable electric service and develop action plans to mitigate. We need to keep exact phrasing. Requirements: "What You Need To Have". List: - Associate or bachelor’s degree in forestry OR one(1) year direct UVM experience. - Solid, local tree identification skills. - Ability to read maps. - Willingness to work alone, outdoors in various weather conditions and terrain. - Superb written and verbal communication skills. - Basic computer skills (Microsoft Office, smartphones). - The ability to travel throughout the region up to 100% during the work week. Note: there is a typo "one(1) year". Keep as is. Qualifications: "What Would Be Amazing To Have". List: - 1-5 years prior UVM, Forestry or related outdoor experience. - Certification as an ISA Arborist, Registered Forester, or other related certificates/licenses a plus. - Prior experience using GIS software preferred. - A strong desire to grow and develop your career and knowledge in the UVM industry with AMS. - Bi-lingual speaking (English and Spanish). Benefits: "What We Offer". List: - Industry competitive pay. - Company vehicle with fuel card for work purposes. - Day 1 of Employment: Medical/Dental/Vision/VOYA/Paid Holidays/EAP (Full-Time Employees). - After 3 months: 401K, life insurance, short and long-term disability, Paid Maternity Leave, Vacation Accrual. - Paid Sick Time. - Weekly Pay Cycle. - Participation in Referral Bonus Program. - Boot and clothing program (Full-Time Employees). - Ongoing training and assistance with obtaining industry certifications. Pay: we have "Industry competitive pay." Already listed as a benefit but also could be separate Pay section. However we already have it as a benefit item. The instruction: do not create Pay/Schedule/Benefits sections unless posting actually states them. It does state "Industry competitive pay." So we could have a Pay section with that sentence. But we also have it in Benefits list. Might be duplication. Better to keep Pay separate with that sentence, and Benefits list without that line? But we must preserve ALL substantive information; we cannot remove the pay statement from Benefits if we move it. We could keep it in Benefits and also have Pay section repeating? That would duplicate info, which is not prohibited but maybe not ideal. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is not removing info, but it's repeating. Might be okay but better to avoid duplication. We could keep Pay section with that sentence, and Benefits list without that line (i.e., remove "Industry competitive pay." from Benefits). However that would be removing info from Benefits list (the pay statement). But we would still have it in Pay section, so info preserved overall. That's acceptable as we are not removing, just relocating. The instruction didn't forbid moving content between sections as long as all info present. So we can put pay statement in Pay section, and Benefits list excludes that line. Thus Benefits list will be: - Company vehicle with fuel card for work purposes. - Day 1 of Employment: Medical/Dental/Vision/VOYA/Paid Holidays/EAP (Full-Time Employees). - After 3 months: 401K, life insurance, short and long-term disability, Paid Maternity Leave, Vacation Accrual. - Paid Sick Time. - Weekly Pay Cycle. - Participation in Referral Bonus Program. - Boot and clothing program (Full-Time Employees). - Ongoing training and assistance with obtaining industry certifications. Now we need to output HTML fragment with headings

  and content. Structure:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Qualifications

  • ...
  ...

  Benefits

  • ...
  ...

  Pay

  Industry competitive pay.

  Check that we didn't include Schedule. Make sure no extra whitespace or markdown. Now verify we preserved all substantive information: - About the role: we captured all sentences before "What We Offer". Did we miss any? The description also includes "Some of the most important characteristics of a Transmission Utility Forester (Maintenance) is that you are open-minded and able to engage in safe, constructive interactions with the public. You are accountable for advancing a culture of safety and excellence while providing quality and value to our customers and clients." That's included. - Responsibilities: captured all bullet points. - Requirements: captured all bullet points. - Qualifications: captured all bullet points. - Benefits: captured all except the pay line. - Pay: captured the pay line. Check for any other info like "WORKING ENVIRONMENT" and "PHYSICAL" sections. Those are substantive but we didn't assign a heading. Should we include them? The instruction list of allowed headings includes only those specific ones; we could incorporate that info into Responsibilities or Requirements? But it's not duties/requirements; it's about environment and physical demands. Could be considered part of Requirements (working conditions) or maybe we could add a section like "Working Environment" but not in allowed list. The instruction says: "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 list? 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 should not add other headings. We could incorporate WORKING ENVIRONMENT and PHYSICAL into Requirements or Responsibilities as bullet points. That would preserve info. Let's do that: add bullet points under Requirements (or maybe a separate section like "Working Conditions" but not allowed). Better to add under Requirements as they are requirements about environment and physical ability. However Requirements currently is about mandatory qualifications; we could add those as bullet points under Requirements. That would preserve all info. Similarly, "Company Overview" and "Applicants must