HR Generalist: Benefits, Wellness & Leave Management Specialist
AKG of America · Mebane, NC · 1 mo ago
Human ResourcesFull-time
We need to output HTML fragment with sections: About the role (maybe "About the role") as h3, Responsibilities, Requirements, maybe Benefits, Pay, Schedule if present. The posting includes no explicit Pay or Schedule details. It mentions "Full-time" job type but not schedule details. So we should not create Pay or Schedule sections. Benefits? The posting includes benefits administration but not a benefits section describing employee benefits (like health insurance, etc). There's no explicit "Benefits" heading describing what the employee gets. So we should not create a Benefits section unless the posting actually states them. It does not list employee benefits like health, dental, etc. So we skip Benefits.
We need to include sections only when there is real specific content. We have About the Role (the description after "About the Role"). We have Responsibilities (Key Responsibilities). We have Requirements (Minimum Qualifications, Knowledge, skills, and abilities, Physical Demands). Also maybe "Why Join AKG" could be a section? Not in the list of allowed headings; allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Why Join AKG" is not allowed; we could treat it as part of About? But we should not invent headings. The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only use those headings if content exists. "Why Join AKG" is not in list, so we should not create a heading for it; we could incorporate its content into About the role or maybe drop? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Why Join AKG" is substantive but not a standard heading; we could embed it under About the role as a paragraph. That's acceptable.
We also have "Equal Employment Opportunity and Accommodation Statement" and disclaimer which are boilerplate EEO etc; we should remove them. Also safety standard and AKG Way maybe not boilerplate but could be considered part of responsibilities? It's about safety and values; could be considered part of About the role or maybe we keep as part of About? It's substantive but not a standard heading; we could include under About the role as paragraphs.
We need to output only HTML fragment, no /, no markdown fences.
Structure:
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only use those headings if content exists. "Why Join AKG" is not in list, so we should not create a heading for it; we could incorporate its content into About the role or maybe drop? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Why Join AKG" is substantive but not a standard heading; we could embed it under About the role as a paragraph. That's acceptable.
We also have "Equal Employment Opportunity and Accommodation Statement" and disclaimer which are boilerplate EEO etc; we should remove them. Also safety standard and AKG Way maybe not boilerplate but could be considered part of responsibilities? It's about safety and values; could be considered part of About the role or maybe we keep as part of About? It's substantive but not a standard heading; we could include under About the role as paragraphs.
We need to output only HTML fragment, no /, no markdown fences.
Structure:
About the role
... (combined About the Role text plus Why Join AKG plus Safety Standard and AKG Way maybe)
Responsibilities
- ... each responsibility bullet
Requirements
- ... each requirement bullet