People & Culture Total Rewards Manager
Evermore Orlando Resort · Orlando, FL · 1 mo ago
On-siteHuman ResourcesFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes "About Evermore" description, then "Key Responsibilities", then "Education, Skills, And Experience", then "Physical Requirements", then "Evermore Culture". Also benefits are mentioned in culture section: "We offer our Team Members competitive pay, along with a range of benefits including FREE Life Insurance, FREE Short-Term Disability, FREE Long-Term Disability. Additionally, we provide affordable health benefits, including Medical, Dental, and Vision coverage for your dependents. Furthermore, we offer a 401K with employer match, a robust paid time off policy, parental and grandparent leave, as well as family and pet bereavement leave. We also have unique policies in support of our team and significant relationships in their lives."
Thus we have Benefits content. Pay is mentioned as "competitive pay" but no specific amount; we should not create Pay section unless posting actually states them. It says "competitive pay" but no specifics; that is vague. According to rules: 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. "competitive pay" is vague but still states that they offer competitive pay. Is that considered filler? It's not a specific number, but it's a statement. The rule says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state they offer competitive pay, plus benefits details. So we can include a Benefits section with the details. Pay section maybe not needed because no specific pay amount. Could combine pay into Benefits? But they said prefer a few substantive sections over many thin ones. We could include Benefits section covering pay and benefits. However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." Since they state benefits, we can create Benefits section. Pay is not specific; we could omit Pay section. Schedule not mentioned.
Thus sections: About the role? The intro about Evermore could be considered "About the role"? Actually the posting starts with "About Evermore Shape the Next Generation of Vacations!" That's more about the company. Could treat as "About the role" or maybe we should not repeat job title. The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use About the role for the introductory paragraph about Evermore and the role? The role is People Benefits Manager? Not explicitly titled but implied. We'll use About the role to describe the role and company.
Then Responsibilities (Key Responsibilities). Then Requirements (Education, Skills, And Experience). Then Physical Requirements (maybe under Requirements? but we can make a separate Physical Requirements section). Then Benefits (from Evermore Culture). Also maybe Culture section could be included but we already used Benefits; culture could be omitted as not required. But we could include Culture as a section if we want, but they said prefer few substantive sections. Culture is substantive but maybe we can incorporate into About the role? However the culture description is separate; we could include a Culture section. But we already have Benefits; we could also include Culture. However we must avoid thin sections. Culture is a few sentences; could be okay.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from each section.
Let's extract:
About Evermore: description of resort, location, amenities, etc. Also mention "Our team members are true trailblazers..." etc. That's substantive.
Key Responsibilities: list many bullet-like sentences. We need to convert to