Electric Distribution Director, Energy
Halff · Houston, TX · 1 mo ago
HybridManagementFull-time
We need to output HTML fragment with sections for headings where there is real content. Use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We must not repeat job title as heading. No Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions.
We need to preserve all substantive information.
We need to decide which sections to include based on content.
From posting:
- About the role: description of role, impact, etc. Could be "About the role" heading.
- Responsibilities: bullet list under "What You Will Do". That's responsibilities.
- Requirements: bullet list under "What You Will Need". That's requirements.
- Qualifications: maybe "Preferred Qualifications". Could be separate "Qualifications" or "Preferred Qualifications". The instruction says use headings like Qualifications. We can have a Qualifications section for preferred qualifications.
- Skills: maybe not explicit separate list; but we could embed skills within responsibilities/requirements. However we could create a Skills section if there is explicit skill list. There is "Excellent communication, leadership, negotiation, and team-building skills." plus "Valid driver's license". Could be skills. But we can also include under Requirements. The instruction: prefer a few substantive sections over many thin ones. So maybe combine Skills into Requirements or Qualifications. But we have separate headings allowed; we can decide to not create Skills if not enough distinct content.
- Benefits: there is "We Offer Excellent Benefits, Including But Not Limited To ..." list. So Benefits section.
- Pay: "Salary is competitive and commensurate with experience." That's vague; we should not create Pay section if content is just "commensurate with experience" (which is placeholder). The instruction: 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. Since Pay is only "competitive and commensurate with experience", that's placeholder; we should NOT create Pay section.
- Schedule: no mention of schedule; do not create.
Thus sections: About the role, Responsibilities, Requirements, Qualifications (preferred), Benefits.
We need to use
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We must not repeat job title as heading. No Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions.
We need to preserve all substantive information.
We need to decide which sections to include based on content.
From posting:
- About the role: description of role, impact, etc. Could be "About the role" heading.
- Responsibilities: bullet list under "What You Will Do". That's responsibilities.
- Requirements: bullet list under "What You Will Need". That's requirements.
- Qualifications: maybe "Preferred Qualifications". Could be separate "Qualifications" or "Preferred Qualifications". The instruction says use headings like Qualifications. We can have a Qualifications section for preferred qualifications.
- Skills: maybe not explicit separate list; but we could embed skills within responsibilities/requirements. However we could create a Skills section if there is explicit skill list. There is "Excellent communication, leadership, negotiation, and team-building skills." plus "Valid driver's license". Could be skills. But we can also include under Requirements. The instruction: prefer a few substantive sections over many thin ones. So maybe combine Skills into Requirements or Qualifications. But we have separate headings allowed; we can decide to not create Skills if not enough distinct content.
- Benefits: there is "We Offer Excellent Benefits, Including But Not Limited To ..." list. So Benefits section.
- Pay: "Salary is competitive and commensurate with experience." That's vague; we should not create Pay section if content is just "commensurate with experience" (which is placeholder). The instruction: 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. Since Pay is only "competitive and commensurate with experience", that's placeholder; we should NOT create Pay section.
- Schedule: no mention of schedule; do not create.
Thus sections: About the role, Responsibilities, Requirements, Qualifications (preferred), Benefits.
We need to use for each section heading.
Inside each section, use
for prose,
- for lists.
We must preserve all substantive information: need to include details from About the role paragraph, responsibilities bullet list, requirements bullet list, preferred qualifications bullet list, benefits list.
Also include some other prose like company overview? The posting includes Company Overview, Halff Electric Distribution Advantage, Halff Electric Distribution Services, Company Overview etc. Those are substantive; we need to preserve all substantive information. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include those sections as well. But we only have allowed headings list; we could embed them under About the role or maybe create additional sections? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive? It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. However we must preserve all substantive information; we can include extra prose under those headings, like under About the role we can include company overview, advantages, services etc. That would preserve info. Thus we will create sections:
About the role
... include the introductory paragraph about role, plus company overview, advantage, services details.
Responsibilities
- ... each bullet from "What You Will Do"
Requirements
- ... each bullet from "What You Will Need"
Qualifications
Preferred Qualifications:
- ... each bullet from "Preferred Qualifications"
Benefits
- ... each bullet from benefits list
will contain the intro paragraph plus company overview, advantage, services list. We must format as HTML: use
for prose,
- for lists.
We need to avoid duplicate content: ensure we don't repeat same info.
Now construct HTML.
Start with
About the role
Thencombine intro paragraph sentences. After that maybe
for company overview. Then
for advantage. Then
- for services list.
Make sure to not include any heading for Services; just list inside About the role.
Now Responsibilities
Responsibilities
- with each bullet.
Requirements
Requirements
- .
Qualifications
Qualifications