General Foreman
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use - for lists,
for prose
- Do NOT repeat job title as heading (page already shows it)
- Do NOT put Job ID/requisition numbers as headings — fold minor metadata into short
or drop
- Preserve ALL substantive information; do NOT invent or summarize away detail
- Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions
- Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD")
- Never create Pay/Schedule/Benefits sections unless posting actually states them
- Prefer few substantive sections over many thin ones
- Output ONLY HTML fragment — no /, no markdown code fences
Now analyze the posting:
Position Title: General Foreman (don't repeat as heading)
Location: Seneca, SC
Job Category: Utility Construction/Operations
Date Posted: 09/01/2026
Salary Interval: Salary Exempt (this is pay info, but not specific salary amount; it's a classification. Might include in a short p or in a Pay section? The rule: never create Pay section unless posting actually states them. It says "Salary Interval: Salary Exempt". That's a pay classification. Could include in a short p under a "Pay" heading? But the rule says never create Pay/Schedule/Benefits sections unless posting actually states them. It does state "Salary Interval: Salary Exempt". That's a statement about pay. But it's not a salary range. Might be considered a pay detail. However, the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "Salary Interval: Salary Exempt". That is a statement about pay. But also there is "Competitive wages and benefits" in description. And "Bi-weekly Pay" in benefits. So there is some pay info. But the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "Salary Interval: Salary Exempt". That's a pay detail. But also "Bi-weekly Pay" is a schedule/pay detail. However, the rule also says "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". "Salary Exempt" is not filler; it's a classification. But is it substantive? Might be better to include in a short paragraph under "About the role" or a "Pay" section. But the rule says prefer few substantive sections over many thin ones. I could include pay info in a short paragraph under "About the role" or "Position Details". But the user wants sections like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". I should only include sections that have real content.
Let's identify sections:
1. About the role: The description includes company background, role overview, work conditions. That's substantive.
2. Responsibilities: The "ESSENTIAL FUNCTIONS" list is responsibilities.
3. Requirements: The "Position Requirements" list.
4. Benefits: The "COMPANY BENEFITS" section is detailed.
5. Pay: There's "Salary Interval: Salary Exempt" and "Bi-weekly Pay" and "Competitive wages". Could create a Pay section with that info.
6. Schedule: There's "Travel to job sites, including overnight out-of-town assignments; overtime may be required" and "Work outdoors in all weather and terrain conditions". That's schedule/conditions. Could be part of "About the role" or a "Schedule" section. But the rule says never create Schedule section unless posting actually states them. It does state travel, overtime, outdoor work. That's schedule/conditions. Might be included in "About the role" or a "Work Conditions" section. But the allowed headings are specific: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Schedule" is allowed. The posting includes schedule info: travel, overnight, overtime, outdoor work. So I could create a Schedule section.
But also "Qualifications" and "Skills" might overlap with Requirements. The posting has "Position Requirements" which includes experience, leadership, knowledge, ability to read plans, communication, driver's license, attendance, ability to work outdoors and travel. That's both requirements and qualifications/skills. I could split into Requirements and Qualifications, but the rule says prefer few substantive sections. I'll keep "Requirements" as the heading for that list.
Also "Skills" could be separate but not needed.
Now, metadata: Location, Job Category, Date Posted, Salary Interval. These are minor metadata. Fold into a short
or drop. I'll include a short paragraph at top with location, category, date posted, salary interval.
Application instructions: remove.
EEO boilerplate: remove.
Now structure:
- Start with a
for metadata: "Location: Seneca, SC | Job Category: Utility Construction/Operations | Date Posted: 09/01/2026 | Salary Interval: Salary Exempt"
- Then
About the role
with prose describing company and role.
- Then Responsibilities
with - for each essential function.
- Then
Requirements
with - for each requirement.
- Then
Benefits
with - for each benefit category and items. The benefits are grouped: Your Career, Your Success, Your Well-Being, Your Work-Life Balance. I'll list each as sub-items or just list all bullet points. Could use nested lists but simpler: each benefit as a bullet. But the grouping is nice. I'll keep grouping by using
with - for each group, and within each group a nested
for items. That's allowed.
- Then Pay
with or
for pay details: "Salary Interval: Salary Exempt", "Bi-weekly Pay", "Competitive wages". Could be a short paragraph.
- Then Schedule
with - for schedule details: travel, overnight, overtime, outdoor work.
But note: The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state benefits extensively, so Benefits section is fine. Pay: states "Salary Interval: Salary Exempt" and "Bi-weekly Pay" and "Competitive wages". That's stating pay. Schedule: states travel, overnight, overtime, outdoor work. That's schedule. So include them.
But also "Qualifications" and "Skills" are not separate; they're covered in Requirements.
Now, ensure no duplicate headings. Use only
for headings.
Now write HTML.
Let's draft:
Location: Seneca, SC | Job Category: Utility Construction/Operations | Date Posted: 09/01/2026 | Salary Interval: Salary Exempt
About the role
ElectriCom, a utility construction company founded in 1960 in Paoli, Indiana, has experienced continuous growth since its inception. We take pride in our strong family-focused culture, both in the workplace and in our customer relationships. We seek employees who want to grow with a progressive company and who value quality, safety, and teamwork. ElectriCom offers competitive wages and benefits, along with opportunities for advancement and skill development.
We are seeking a General Foreman to oversee multiple crews on telecommunications and utility construction projects. This role supports the Construction Manager in coordinating field operations and ensuring safety, quality, and production across multiple projects. It also provides field leadership, supports Foremen, resolves job-site challenges, and ensures crews have the resources needed to work safely and efficiently. Work is performed outdoors in all weather conditions, and travel to job sites—including overnight out-of-town assignments—is required.
Responsibilities
- Supervise and support multiple crews on aerial and underground fiber-construction projects
- Coordinate daily and weekly work activities to meet production goals
- Maintain safe job sites and ensure compliance with company and industry standards
- Provide direction, training, and technical support to Foremen and field crews
- Conduct job-site visits to monitor progress, quality, and safety
- Assist with resolving field issues and utility conflicts
- Communicate project updates with the Construction Manager and other stakeholders
- Work outdoors in all weather and terrain conditions
- Travel to job sites, including overnight out-of-town assignments; overtime may be required
- Participate in required training and perform traffic control as needed
Requirements
- 5+ years of experience as a Foreman in utility, telecom, or construction
- Strong leadership skills with the ability to manage multiple crews
- Knowledge of aerial and underground fiber-construction methods and equipment
- Ability to read and interpret plans, maps, and job specifications
- Strong communication and problem-solving skills
- Valid driver’s license required; CDL preferred
- Reliable attendance and commitment to safe work practices
- Ability to work outdoors and travel as needed
Benefits
- Your Career
- Certified Apprentice Programs
- Focused Construction Training
- Opportunities for advancement and skill development
- Your Success
- 401(k) with Company Match up to 6%
- Competitive Medical, Dental, and Vision Coverage, including a $0-cost health benefit plan option
- Health Savings Account (HSA) with Company Contributions & Match
- Your Well-Being
- Company-Paid Life & AD&D Insurance
- Company-Paid Virtual Doctor Service (Teladoc)
- Company-Paid Long-Term Disability
- Company-Paid Short-Term Disability after 3 years of employment
- Additional Voluntary Life Insurance & Voluntary Short-Term Disability
- Your Work-Life Balance
- Paid Vacation (PTO) plus Paid Holidays
- Bi-weekly Pay
- Per diem eligibility
Pay
Salary Interval: Salary Exempt. Bi-weekly pay. Competitive wages.
Schedule
- Work outdoors in all weather and terrain conditions
- Travel to job sites, including overnight out-of-town assignments
- Overtime may be required
Check for any missing info: The posting also mentions "Participate in required training and perform traffic control as needed" already in responsibilities. Good.
Now ensure no markdown code f
for prose - Do NOT repeat job title as heading (page already shows it) - Do NOT put Job ID/requisition numbers as headings — fold minor metadata into short
or drop - Preserve ALL substantive information; do NOT invent or summarize away detail - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions - Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") - Never create Pay/Schedule/Benefits sections unless posting actually states them - Prefer few substantive sections over many thin ones - Output ONLY HTML fragment — no /, no markdown code fences Now analyze the posting: Position Title: General Foreman (don't repeat as heading) Location: Seneca, SC Job Category: Utility Construction/Operations Date Posted: 09/01/2026 Salary Interval: Salary Exempt (this is pay info, but not specific salary amount; it's a classification. Might include in a short p or in a Pay section? The rule: never create Pay section unless posting actually states them. It says "Salary Interval: Salary Exempt". That's a pay classification. Could include in a short p under a "Pay" heading? But the rule says never create Pay/Schedule/Benefits sections unless posting actually states them. It does state "Salary Interval: Salary Exempt". That's a statement about pay. But it's not a salary range. Might be considered a pay detail. However, the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "Salary Interval: Salary Exempt". That is a statement about pay. But also there is "Competitive wages and benefits" in description. And "Bi-weekly Pay" in benefits. So there is some pay info. But the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "Salary Interval: Salary Exempt". That's a pay detail. But also "Bi-weekly Pay" is a schedule/pay detail. However, the rule also says "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". "Salary Exempt" is not filler; it's a classification. But is it substantive? Might be better to include in a short paragraph under "About the role" or a "Pay" section. But the rule says prefer few substantive sections over many thin ones. I could include pay info in a short paragraph under "About the role" or "Position Details". But the user wants sections like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". I should only include sections that have real content. Let's identify sections: 1. About the role: The description includes company background, role overview, work conditions. That's substantive. 2. Responsibilities: The "ESSENTIAL FUNCTIONS" list is responsibilities. 3. Requirements: The "Position Requirements" list. 4. Benefits: The "COMPANY BENEFITS" section is detailed. 5. Pay: There's "Salary Interval: Salary Exempt" and "Bi-weekly Pay" and "Competitive wages". Could create a Pay section with that info. 6. Schedule: There's "Travel to job sites, including overnight out-of-town assignments; overtime may be required" and "Work outdoors in all weather and terrain conditions". That's schedule/conditions. Could be part of "About the role" or a "Schedule" section. But the rule says never create Schedule section unless posting actually states them. It does state travel, overtime, outdoor work. That's schedule/conditions. Might be included in "About the role" or a "Work Conditions" section. But the allowed headings are specific: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Schedule" is allowed. The posting includes schedule info: travel, overnight, overtime, outdoor work. So I could create a Schedule section. But also "Qualifications" and "Skills" might overlap with Requirements. The posting has "Position Requirements" which includes experience, leadership, knowledge, ability to read plans, communication, driver's license, attendance, ability to work outdoors and travel. That's both requirements and qualifications/skills. I could split into Requirements and Qualifications, but the rule says prefer few substantive sections. I'll keep "Requirements" as the heading for that list. Also "Skills" could be separate but not needed. Now, metadata: Location, Job Category, Date Posted, Salary Interval. These are minor metadata. Fold into a short
or drop. I'll include a short paragraph at top with location, category, date posted, salary interval. Application instructions: remove. EEO boilerplate: remove. Now structure: - Start with a
for metadata: "Location: Seneca, SC | Job Category: Utility Construction/Operations | Date Posted: 09/01/2026 | Salary Interval: Salary Exempt" - Then
About the role
with prose describing company and role. - ThenResponsibilities
with- for each essential function.
- Then
Requirements
with- for each requirement.
- Then
Benefits
with- for each benefit category and items. The benefits are grouped: Your Career, Your Success, Your Well-Being, Your Work-Life Balance. I'll list each as sub-items or just list all bullet points. Could use nested lists but simpler: each benefit as a bullet. But the grouping is nice. I'll keep grouping by using
- with
- for each group, and within each group a nested
- for items. That's allowed.
- Then
- for schedule details: travel, overnight, overtime, outdoor work.
But note: The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state benefits extensively, so Benefits section is fine. Pay: states "Salary Interval: Salary Exempt" and "Bi-weekly Pay" and "Competitive wages". That's stating pay. Schedule: states travel, overnight, overtime, outdoor work. That's schedule. So include them.
But also "Qualifications" and "Skills" are not separate; they're covered in Requirements.
Now, ensure no duplicate headings. Use only
for headings. Now write HTML. Let's draft:
Location: Seneca, SC | Job Category: Utility Construction/Operations | Date Posted: 09/01/2026 | Salary Interval: Salary Exempt
About the role
ElectriCom, a utility construction company founded in 1960 in Paoli, Indiana, has experienced continuous growth since its inception. We take pride in our strong family-focused culture, both in the workplace and in our customer relationships. We seek employees who want to grow with a progressive company and who value quality, safety, and teamwork. ElectriCom offers competitive wages and benefits, along with opportunities for advancement and skill development.
We are seeking a General Foreman to oversee multiple crews on telecommunications and utility construction projects. This role supports the Construction Manager in coordinating field operations and ensuring safety, quality, and production across multiple projects. It also provides field leadership, supports Foremen, resolves job-site challenges, and ensures crews have the resources needed to work safely and efficiently. Work is performed outdoors in all weather conditions, and travel to job sites—including overnight out-of-town assignments—is required.
Responsibilities
- Supervise and support multiple crews on aerial and underground fiber-construction projects
- Coordinate daily and weekly work activities to meet production goals
- Maintain safe job sites and ensure compliance with company and industry standards
- Provide direction, training, and technical support to Foremen and field crews
- Conduct job-site visits to monitor progress, quality, and safety
- Assist with resolving field issues and utility conflicts
- Communicate project updates with the Construction Manager and other stakeholders
- Work outdoors in all weather and terrain conditions
- Travel to job sites, including overnight out-of-town assignments; overtime may be required
- Participate in required training and perform traffic control as needed
Requirements
- 5+ years of experience as a Foreman in utility, telecom, or construction
- Strong leadership skills with the ability to manage multiple crews
- Knowledge of aerial and underground fiber-construction methods and equipment
- Ability to read and interpret plans, maps, and job specifications
- Strong communication and problem-solving skills
- Valid driver’s license required; CDL preferred
- Reliable attendance and commitment to safe work practices
- Ability to work outdoors and travel as needed
Benefits
- Your Career
- Certified Apprentice Programs
- Focused Construction Training
- Opportunities for advancement and skill development
- Your Success
- 401(k) with Company Match up to 6%
- Competitive Medical, Dental, and Vision Coverage, including a $0-cost health benefit plan option
- Health Savings Account (HSA) with Company Contributions & Match
- Your Well-Being
- Company-Paid Life & AD&D Insurance
- Company-Paid Virtual Doctor Service (Teladoc)
- Company-Paid Long-Term Disability
- Company-Paid Short-Term Disability after 3 years of employment
- Additional Voluntary Life Insurance & Voluntary Short-Term Disability
- Your Work-Life Balance
- Paid Vacation (PTO) plus Paid Holidays
- Bi-weekly Pay
- Per diem eligibility
Pay
Salary Interval: Salary Exempt. Bi-weekly pay. Competitive wages.
Schedule
- Work outdoors in all weather and terrain conditions
- Travel to job sites, including overnight out-of-town assignments
- Overtime may be required
Pay
withor
- for pay details: "Salary Interval: Salary Exempt", "Bi-weekly Pay", "Competitive wages". Could be a short paragraph.
- Then
Schedule
with - for schedule details: travel, overnight, overtime, outdoor work.
But note: The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state benefits extensively, so Benefits section is fine. Pay: states "Salary Interval: Salary Exempt" and "Bi-weekly Pay" and "Competitive wages". That's stating pay. Schedule: states travel, overnight, overtime, outdoor work. That's schedule. So include them.
But also "Qualifications" and "Skills" are not separate; they're covered in Requirements.
Now, ensure no duplicate headings. Use only
- for each group, and within each group a nested
- for each benefit category and items. The benefits are grouped: Your Career, Your Success, Your Well-Being, Your Work-Life Balance. I'll list each as sub-items or just list all bullet points. Could use nested lists but simpler: each benefit as a bullet. But the grouping is nice. I'll keep grouping by using
- for each requirement.
- Then