Utility Field Technician – Power Pole Data Collection

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

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. From posting: - About This Opportunity: description of role, location, primary field areas. Could be "About the role". We'll put that. - What To Know Before Applying: includes field assignments details, vehicle requirements, orientation. Could be part of responsibilities or maybe separate but we can include under Responsibilities? The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content accordingly. We have: - Responsibilities: "What You Can Expect To Do" list of duties. - Requirements: "WHAT WE’RE LOOKING FOR" includes education, experience, abilities, etc. Also "Physical Requirements". Could be under Requirements. - Qualifications: maybe overlapping with Requirements; but we can treat Requirements as qualifications. However we need to decide if we need both Requirements and Qualifications sections. The instruction says prefer a few substantive sections over many thin ones. So we can combine education/experience/abilities into Requirements, and maybe Skills separate? But we have skills listed: ability to work independently, attention to detail, using mobile devices, reading maps, communication, etc. Those could be Skills. But they are also in Requirements. To avoid duplication, we can put them under Skills. However we must preserve all substantive information; we can split but ensure no duplication? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication, but better to avoid redundancy. We could put education/experience under Requirements, and abilities/skills under Skills. Physical Requirements could be under Requirements or maybe a separate section but we don't have a heading for Physical Requirements; we could include under Requirements. Benefits: "What We Offer" includes compensation, medical/dental/vision, 401k, paid holidays, education assistance, mileage reimbursement. Also "Competitive compensation." That's benefits. Pay: they say "Compensation is commensurate with experience and education." That's vague; we should not create Pay section unless posting actually states them. It says "Compensation is commensurate with experience and education." That's not a specific number or range; it's placeholder. According to rule: 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. For Benefits, they do state specific benefits: medical/dental/vision, 401k, paid holidays, vacation, sick time, education assistance, mileage reimbursement. So we can create Benefits section with those details. Pay: they only say "Competitive compensation." and later "Compensation is commensurate with experience and education." That's placeholder; we should not create Pay section. Schedule: they mention assignments may require driving an hour or more one way and staying overnight Monday through Thursday when necessary. Also orientation one week. But schedule not explicitly given like full-time, shift. The job type is Full-time. Could we create Schedule section? The posting does not give specific schedule details beyond full-time and occasional overnight. That's somewhat vague but still schedule info. However rule: never create Schedule section unless posting actually states them. It does state "Full-time" and mentions overnight stays. That is schedule info. Could be considered schedule. But we might avoid creating Schedule section if it's thin. Better to include schedule info under About the role or Responsibilities? Probably under About the role we can mention full-time and travel. But we have to decide. We need to output only HTML fragment, no markdown. Let's craft sections:

About the role

Utility Field Technician – Power Pole Data Collection located in Huntington, WV, serving communities throughout Western West Virginia, Eastern Kentucky, and Southern Ohio. Sigma Technologies seeks a field‑based technician to collect information and document overhead power‑distribution infrastructure. The role involves year‑round outdoor work, travel throughout the region, and independent work management. New hires attend a paid one‑week in‑person orientation and training at headquarters in Perrysburg, Ohio.

Responsibilities

• Conduct field surveys of overhead power‑distribution facilities.
• Locate, inspect, photograph, measure, and document utility poles, power lines, transformers, attachments, and related infrastructure.
• Record pole conditions, equipment information, attachment details, clearances, and surrounding field conditions.
• Use maps, mobile devices, GIS‑based applications, and electronic data‑collection tools to locate facilities and document information.
• Upload accurate photographs, measurements, field notes, and other required project information.
• Plan daily routes and manage assigned work efficiently throughout the designated field area.
• Communicate with project management, engineering, and design teams regarding field conditions, access concerns, or missing information.
• Follow all company, customer, traffic, and field‑safety requirements.
• Perform other related duties as assigned.

Requirements

• High school diploma or equivalent required.
• Previous experience in utilities, power distribution, telecommunications, construction, surveying, inspection, GIS, or field data collection is preferred but not required.
• Ability to work independently, manage daily assignments, and remain productive with limited direct supervision.
• Strong attention to detail and the ability to accurately document field conditions.
• Comfort using mobile devices, email, maps, electronic forms, and data‑collection applications.
• Ability to read maps, follow assigned routes, and navigate rural or unfamiliar locations.
• Clear and professional verbal and written communication skills.
• Reliable personal transportation, a valid driver’s license, and automobile insurance meeting Sigma’s minimum requirements.
• Ability to successfully complete required background, drug, and driving‑record checks.
• Authorization to work in the United States without sponsorship.

Physical Requirements

but we don't have a heading for Physical Requirements in allowed list. Could we put under Requirements? Already we have many items; we could add a sublist but we cannot add new heading not in list. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put physical requirements under Requirements as part of that list. But we already have many items; we could add them as list items under Requirements. However we already have a Requirements list; we can extend it. Let's move physical requirements into Requirements as additional bullet points. Thus Requirements list will include education, experience, abilities, and physical requirements. Now Skills: we could separate some abilities like using mobile devices, communication, etc. But we already have them in Requirements. To avoid duplication, maybe we should not create Skills section if it would be thin. The instruction: prefer a few substantive sections over many thin ones. So we can omit Skills section. Benefits: we have specific benefits.

Benefits

• Competitive compensation.
• Medical, dental, and vision plans with up to 80% of the premium sponsored by Sigma.
• 401(k) plan with company matching contributions of up to 5% of salary.
• Paid holidays, vacation, and sick time.
• Education and professional licensing assistance programs.
• Mileage reimbursement for the required use of a personal vehicle in accordance with company policy.

We should not create Pay or Schedule sections because they'd be thin or placeholder. Check for any other info: location, primary field areas already in About the role. Orientation mentioned there. Make sure we didn't miss any substantive info: "What To Know Before Applying" includes field assignments involve year-round outdoor work in heat, cold, rain, humidity, direct sunlight; work requires driving throughout eastern Kentucky and walking over mountainous, steep, uneven, muddy, wooded, or otherwise difficult terrain; reliable personal vehicle required, mileage reimbursement provided; reliable four-wheel-drive or all-wheel-drive vehicle strongly preferred; assignments may require driving an hour or more one way and staying overnight Monday through Thursday when necessary; new hires must attend initial one-week paid orientation. We have covered orientation in About the role; we haven't covered vehicle requirements, terrain, weather, etc. Those are important details. Should we include them somewhere? Could be under Responsibilities (maybe as part of duties) or under Requirements (as requirements). They are more about working conditions and requirements. Could be added to Requirements as bullet points: ability to work in various weather conditions, ability to drive over mountainous terrain, need for reliable personal vehicle, preference for 4WD/AWD, willingness to travel and stay overnight. Those are requirements. Let's add those to Requirements list. Also "Due to local terrain and road conditions, a reliable four-wheel-drive or all-wheel-drive vehicle is strongly preferred." That's a requirement/preference. Add bullet: "Reliable personal vehicle required; mileage reimbursement provided at company-designated rate. A reliable four-wheel-drive or all-wheel-drive vehicle is strongly preferred." Also "Assignments may require driving an hour, or more, one way and staying overnight Monday through Thursday when necessary." Add bullet. Also "Field assignments involve year-round outdoor work in heat, cold, rain, humidity, and direct sunlight." Add bullet. Also "The work requires driving throughout eastern Kentucky and walking over mountainous, steep, uneven, muddy, wooded, or otherwise difficult terrain." Add bullet. Now we have many bullets; that's fine. Now check for duplication: we already have bullet about reliable personal transportation, driver's license, insurance. We can keep that and add the vehicle preference. Now ensure we didn't miss any: "New hires must attend an initial one-week, in-person, paid orientation and training program at our headquarters in Perrysburg, Ohio." Already in About the role. Now "What You Can Expect To Do" we used as Responsibilities. Now "What We Offer" we used as Benefits. Now "About Sigma Technologies" we could include maybe under About the role? But it's company description; not required but could be included under About the role as extra. However the instruction: preserve ALL substantive information. The company description is substantive but not about the role. Could we add a separate section? Not in allowed headings. Could we add a paragraph under About the role after role description? That would be okay; it's still part of About the role section. But we must not repeat job title as heading; we already have About the role heading. Adding company info there is fine. Let's add a paragraph after the role description: "Sigma Technologies is a growing engineering and design firm supporting the power and telecommunications industries. For more than 25 years, our work has helped strengthen infrastructure and positively impact communities across the country. Our core values—Safety, Honesty, Truth, and Decency—guide our work and shape our culture. We are TeamSigma™." Now check for any other info: "Additional Information" includes disclaimer about not all-inclusive, etc. That's boilerplate; we should remove per instruction: remove legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The Additional Information includes disclaimer about not all-inclusive, not an employment agreement, etc. That's likely boilerplate; we should drop it. Also "Compensation is commensurate with experience and education." That's placeholder; we should not create Pay section; we already have Competitive compensation in Benefits; we could keep that phrase but it's vague. However we already have Competitive compensation bullet; that's okay. Now ensure we didn't include any boilerplate like EEO etc. We removed. Now produce HTML fragment. Let's craft final HTML:

About the role

Utility Field Technician – Power Pole Data