Civil Superintendent - Battery Storage - Georgia
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive info.
We need to parse the posting.
Key parts:
- Intro paragraph about company, employee-owned, etc. That's about the role? Actually it's company description. Could be "About the role" or "About the company". The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" heading and include the description of role and company.
- Job Summary: "In this role, you will help lead safe, high-quality field execution..." That's part of responsibilities maybe. Could be under Responsibilities.
- Key Responsibilities: list of bullet points.
- Preferred Qualifications: paragraph and list.
- Minimum Qualifications: bullet points.
- Certifications: OSHA 10 certification.
- Work Environment/Physical Demands: details.
- Salary Plan CNS: Construction Services Job Grade 016 (maybe Pay? Not explicit salary number). It says Salary Plan CNS: Construction Services Job Grade 016. That's not a specific salary figure; it's a grade. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state Salary Plan CNS: Construction Services Job Grade 016. That is some pay info but not a number. Might be considered Pay section? The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state a Salary Plan and Job Grade. That is pay-related info. Should we include a Pay section? Probably yes, we can include a Pay
with that info. However they said "Prefer a few substantive sections over many thin ones." Might combine Pay with something else? But we can include Pay.
- Benefits: later paragraph about benefits portfolio: health care, flexible work schedules, paid vacation, etc. That's substantive. So we can include Benefits section.
- Schedule: Not explicitly stated besides full-time. It says Full time/Part time: Full-Time. That's schedule info. Could include Schedule section with "Full-Time". However they said never create Schedule section unless posting actually states them. It does state Full-Time. So we can include Schedule.
But we need to avoid filler like "commensurate with experience". Not present.
We need to remove boilerplate: EEO, legal, accommodation request, etc. Also remove "Job Segment:" etc.
We need to preserve all substantive info: company description, job summary, responsibilities, preferred qualifications, minimum qualifications, certifications, work environment/physical demands, pay grade, benefits, schedule (full-time), maybe relocation eligible: No, visa sponsorship: No etc. Those are metadata but could be folded into short p or dropped. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
Pay
with that info. However they said "Prefer a few substantive sections over many thin ones." Might combine Pay with something else? But we can include Pay. - Benefits: later paragraph about benefits portfolio: health care, flexible work schedules, paid vacation, etc. That's substantive. So we can include Benefits section. - Schedule: Not explicitly stated besides full-time. It says Full time/Part time: Full-Time. That's schedule info. Could include Schedule section with "Full-Time". However they said never create Schedule section unless posting actually states them. It does state Full-Time. So we can include Schedule. But we need to avoid filler like "commensurate with experience". Not present. We need to remove boilerplate: EEO, legal, accommodation request, etc. Also remove "Job Segment:" etc. We need to preserve all substantive info: company description, job summary, responsibilities, preferred qualifications, minimum qualifications, certifications, work environment/physical demands, pay grade, benefits, schedule (full-time), maybe relocation eligible: No, visa sponsorship: No etc. Those are metadata but could be folded into short p or dropped. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a shortor drop it." So we could include a short paragraph with metadata like "Relocation eligible: No; Visa Sponsorship Available: No; Full-Time; etc." But maybe better to drop them as minor. However they said preserve ALL substantive information; do NOT invent or summarize away detail. Metadata like relocation eligible, visa sponsorship, full-time are substantive? Might be considered minor but still info. We could include them in a short
under maybe "About the role" or separate. We need to avoid duplication. Let's craft sections:
About the role
Join the Overland Contracting (a Black & Veatch company) construction team and build with pride. As a 100% employee‑owned company, every role matters — you own your work, your impact, and your future. We lead with care, and safety is non‑negotiable and embedded into every role, site and decision, ensuring our teams return home safe, every day. From field engineering to project management to quality and startup, you’ll work with cutting‑edge technology, learn from seasoned experts, and grow through real‑world, hands‑on experience. With a strong backlog across power, water, grid, and industrial markets, you’ll have the stability to grow and the opportunity to shape what comes next.
Maybe also include job summary: "In this role, you will help lead safe, high-quality field execution by partnering closely with subcontractor supervision, craft teams, and field engineering. You will provide the technical guidance, coordination, and project information needed to keep work moving safely, efficiently, and on schedule. You will play a key role in communicating expectations, resolving field issues, monitoring subcontractor performance, and ensuring work is completed in alignment with safety, quality, schedule, and contractual requirements." We could incorporate that into About the role or Responsibilities. Probably better to have About the role include company description and job summary. Then Responsibilities:Responsibilities
- ... each bullet from Key Responsibilities list.
under About the role or separate "Details". But we don't have a heading for metadata; we could just include a short paragraph after About the role: "
Relocation eligible: No • Visa Sponsorship: Not available • Full‑Time position
". That preserves info. Now ensure we don't repeat job title as heading. Not using. Now output only HTML fragment. Let's construct. We'll have sections:About the role
...
Relocation eligible: No • Visa Sponsorship: Not available • Full‑Time position
Responsibilities
- ...
Preferred Qualifications
Ideal candidates will bring a degree in Construction Management, Engineering, or a related field, along with training or experience in safety, cost, quality, schedule reporting, construction management, and contract administration.
- ...
Minimum Qualifications
- ...
Work Environment & Physical Demands
...
Benefits
...
Pay
Salary Plan CNS: Construction Services Job Grade 016
Schedule
Full‑Time
Check for any duplicated content: Ensure we didn't include boilerplate like EEO, legal, accommodation request, etc. We removed those. Now verify we kept all substantive info: - Company description and employee-owned: included in About the role. - Job summary: included in About the role (we added after first paragraph? Actually we