Field Technician, Leak Survey
Heath · Portland, OR · 1 mo ago
EngineeringFull-time
We need to output only HTML fragment, no markdown fences. Use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. Let's parse.
Job description includes:
- About the role: maybe "Position Overview" etc. We can treat "Position Overview" as About the role.
- Responsibilities: "What You’ll Do" list.
- Requirements: "Job Requirements" list.
- Qualifications: maybe not separate; but we could combine with Requirements? The instruction says use headings for those categories if content exists. We have "Job Requirements" includes required and preferred. Could treat as Requirements. Qualifications maybe not separate; we could omit if no distinct content.
- Skills: maybe "Proficient using technology..." etc. Could be part of Requirements. But we could create Skills section if there is distinct skill content. The posting mentions "Proficient using technology (smartphone, tablet)", "Ability to use simple hand tools", "Ability to read and understand utility maps", "Works well within a group as well as individually". Those could be Skills.
- Benefits: there is a "Benefits & Compensation" section with details.
- Pay: there is "Pay & Financial" subsection within Benefits & Compensation. Could create Pay section.
- Schedule: not explicitly mentioned; maybe not.
We must not create sections with filler like "not specified". So only include sections where we have concrete info.
We need to preserve all substantive information; do not invent or summarize away detail. Must not repeat job title as heading. Do not put Job ID/requisition numbers as headings.
We must remove boilerplate: EEO, etc. At end there is "Heath Consultants Incorporated is an Equal Opportunity Employer. #INDJE" - remove.
Also remove navigation/cookie/legal etc. Not present.
We need to output only HTML fragment.
Structure: maybe:
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. Let's parse.
Job description includes:
- About the role: maybe "Position Overview" etc. We can treat "Position Overview" as About the role.
- Responsibilities: "What You’ll Do" list.
- Requirements: "Job Requirements" list.
- Qualifications: maybe not separate; but we could combine with Requirements? The instruction says use headings for those categories if content exists. We have "Job Requirements" includes required and preferred. Could treat as Requirements. Qualifications maybe not separate; we could omit if no distinct content.
- Skills: maybe "Proficient using technology..." etc. Could be part of Requirements. But we could create Skills section if there is distinct skill content. The posting mentions "Proficient using technology (smartphone, tablet)", "Ability to use simple hand tools", "Ability to read and understand utility maps", "Works well within a group as well as individually". Those could be Skills.
- Benefits: there is a "Benefits & Compensation" section with details.
- Pay: there is "Pay & Financial" subsection within Benefits & Compensation. Could create Pay section.
- Schedule: not explicitly mentioned; maybe not.
We must not create sections with filler like "not specified". So only include sections where we have concrete info.
We need to preserve all substantive information; do not invent or summarize away detail. Must not repeat job title as heading. Do not put Job ID/requisition numbers as headings.
We must remove boilerplate: EEO, etc. At end there is "Heath Consultants Incorporated is an Equal Opportunity Employer. #INDJE" - remove.
Also remove navigation/cookie/legal etc. Not present.
We need to output only HTML fragment.
Structure: maybe:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Skills
- ... ...
Benefits
- ... ...
Pay
- ... ...
or drop it." The company description may be considered minor metadata? It's substantive but maybe part of About the role. We'll include it in About the role paragraph. Thus About the role paragraph: combine company intro and position overview. Let's craft:
Since 1933, Heath Consultants has been a trusted leader in protecting communities through natural gas safety services. As a Leak Survey Field Technician, you play a vital role in protecting life, property, and the environment. You will inspect natural gas systems, detect potential leaks using advanced equipment, and ensure compliance with safety regulations. Your work directly supports public safety and environmental protection in the communities we serve.
Responsibilities: list from "What You’ll Do": - Inspect natural gas distribution systems - Conduct leak surveys using specialized detection equipment - Accurately document findings and complete compliance reports - Follow strict safety protocols and federal and local regulations - Communicate professionally with homeowners and members of the public - Work Outdoors & Stay Active: Walk approximately 4–7 miles per day; Bend, kneel, and lift up to 25 pounds; Work in a variety of weather conditions; Remain on your feet for extended periods - Operate Specialized Equipment: Use industry-leading gas detection technology to identify potential leaks. We could split into separate li items. Requirements: from "Job Requirements": Required: - High school diploma or GED - Valid driver’s license with a safe driving record - Ability to pass a DOT drug screen and background check - Ability to stand, walk, bend, and stoop on varying terrain, and to lift heavy items - Ability to walk 4–7 miles per day in all weather conditions - Strong reliability and accountability - Proficient using technology (smartphone, tablet) - Ability to use simple hand tools - Ability to read and understand utility maps - Works well within a group as well as individually Preferred — But Not Required: - Customer service experience - No industry experience necessary — we value work ethic, dependability, and a safety-first mindset We could include both required and preferred in same list, maybe differentiate? But we can just list all. Skills: maybe extract from requirements: Proficient using technology, Ability to use simple hand tools, Ability to read and understand utility maps, Works well within a group as well as individually, Strong reliability and accountability, etc. But we already have them in Requirements; we might not need separate Skills if overlapping. However instruction: Prefer a few substantive sections over many thin ones. Could combine Skills into Requirements. But we have headings list; we can omit Skills if not distinct. Let's see if there is distinct skill content beyond requirements: The "What Success Looks Like" mentions initiative, sound judgment, technical competence, customer-focused, detail-oriented, trustworthy, prioritization, communication, time-management skills. Those could be skills. But they are more about success traits. Could be considered Skills. However we might just include them in Requirements or maybe a separate Skills section. Given we already have many items in Requirements, adding Skills may be thin. Better to omit Skills section. Benefits: from "Benefits & Compensation": - Weekly pay - Monthly phone allowance up to $40 - 401(k) with company match - $1,500 employee referral bonus - Medical, dental, and vision insurance - Life insurance - Paid time off - Paid company holidays - Paid training and industry certifications - Overtime eligibility (non-exempt position) Also earlier: "Weekly Pay — You are paid weekly. No waiting for a monthly deposit." That's pay. Pay: we could separate Pay section: Weekly pay, Monthly phone allowance up to $40, 401(k) with company match, $1,500 employee referral bonus, Overtime eligibility. But Benefits already includes weekly pay etc. To avoid duplication, we could have Benefits section covering all benefits, and Pay section maybe just weekly pay? But that would duplicate. Better to have Benefits section that includes all compensation and benefits, and omit separate Pay section. However the instruction says use headings for Benefits, Pay, Schedule if posting actually states them. The posting states Pay & Financial subsection; we could still have Pay section with details like weekly pay, monthly phone allowance, 401(k) match, referral bonus, overtime eligibility. Benefits section could then include health insurance, PTO, holidays, paid training, etc. That avoids duplication. Let's extract Pay details: - Weekly pay (paid weekly) - Monthly phone allowance up to $40 - 401(k) with company match - $1,500 employee referral bonus - Overtime eligibility (non-exempt position) Benefits details: - Medical, dental, and vision insurance - Life insurance - Paid time off - Paid company holidays - Paid training and industry certifications Also maybe "Health & Time Off" includes medical etc. We'll create two sections. Schedule: not mentioned; omit. Now ensure we preserve all substantive information: we need to include also the "Why Heath?" bullet points: Weekly Pay, Paid Training & Industry Certifications, Work That Matters. Those are covered in Pay/Benefits/About the role? Weekly Pay covered in Pay; Paid Training covered in Benefits (Paid training and industry certifications); Work That Matters covered in About the role (protecting life, property, environment). Good. Also include "What Success Looks Like" maybe as part of Requirements or Skills? Could be added to Requirements as soft skills. We'll add to Requirements list. Now craft HTML. We'll need to escape any special characters? Not needed. Let's produce:About the role
Since 1933, Heath Consultants has been a trusted leader in protecting communities through natural gas safety services. As a Leak Survey Field Technician, you play a vital role in protecting life, property, and the environment. You will inspect natural gas systems, detect potential leaks using advanced equipment, and ensure compliance with safety regulations. Your work directly supports public safety and environmental protection in the communities we serve.
Responsibilities
- Inspect natural gas distribution systems
- Conduct leak surveys using specialized detection equipment
- Accurately document findings and complete compliance reports
- Follow strict safety protocols and federal and local regulations
- Communicate professionally with homeowners and members of the public
- Walk approximately 4–7 miles per day
- Bend, kneel, and lift up to 25 pounds
- Work in a variety of weather conditions
- Remain on your feet for extended periods
- Operate industry-leading gas detection technology to identify potential leaks
Requirements
- High school diploma or GED
- Valid driver’s license with a safe driving record
- Ability to pass a DOT drug screen and background check
- Ability to stand, walk, bend, and stoop on varying terrain, and to lift heavy items
- Ability to walk 4–7 miles per day in all weather conditions
- Strong reliability and accountability
- Proficient using technology (smartphone, tablet)
- Ability to use simple hand tools
- Ability to read and understand utility maps
- Works well within a group as well as individually
- Customer service experience (preferred)
- Demonstrates initiative, sound judgment, technical competence, customer focus, detail orientation, trustworthiness, prioritization, communication, and time‑management skills
Benefits
- Medical, dental, and vision insurance
- Life insurance
- Paid time off
- Paid company holidays
- Paid training and industry certifications
Pay
- Weekly pay
- Monthly phone allowance up to $40
- 401(k) with company match
- $1,500 employee referral bonus
- Overtime eligibility (non‑exempt position)