We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content.
We need to parse the posting.
Content:
"Are you looking for a place where meaningful moments are made together? We make vacation dreams come true for travelers around the world in a supportive, friendly, and beautiful work environment. As a Coordinator Customer Relations, you will assist in providing our Owners/guests with experiences and events to make memorable vacation memories, where meaningful moments are made together. Where Great Benefits Lead To a Life Fulfilled. Competitive Pay Medical/Dental/Vision/401K opportunities Travel discounts Credit Union Membership Tuition Reimbursement Professional Counseling & Family Support Growth and Development Opportunities Benefit eligibility will vary by position"
That's about benefits and maybe intro.
Then "As a Coordinator Customer Relations, a typical day will include:" then list bullet points:
- Communicates with preview tour customer via telephone before their scheduled arrival and tour date.
- You will offer Concierge-style services to guests coming to stay with us on a promotional vacation package.
- Provides detailed information about property amenities.
- Engages customers in conversation regarding their stay, property services, and area attractions/offerings.
- Identifies special customer needs and arranges to have those needs fulfilled upon customer arrival.
- Addresses customers's Addresses customers' service needs in a professional, positive, and timely manner.
Then "Guest Experience And Company Standards" then bullet points:
- Welcome and greet guests and anticipate and address their needs.
- Interact with colleagues and guests professionally and promptly.
- Enjoy talking with guests by phone and/or in person with excellent written and verbal communication skills.
- Always follow company policies and safety procedures.
Then "To Become a Coordinator Customer Relations" then bullet points:
- Available to work a flexible schedule to include weekends and holidays.
- Reach overhead and below the knees, perform bending, twisting, pulling, and stooping, and be able to stand, sit, or walk for an extended period of time.
- Lift/Carry/Push/Pull Items that Weigh up to 10lbs without assistance.
- Position may require background and drug screening contingent on company policy in accordance with applicable legal requirements.
Then EEO line to drop.
We need to map to sections.
About the role: maybe the intro paragraph describing role and environment. Could be "About the role". Use
About the role
then
...
.
Responsibilities: The typical day list and Guest Experience standards maybe responsibilities. Could combine.
Requirements: maybe the "To Become a Coordinator Customer Relations" bullet points (physical requirements, schedule flexibility, background check). Could be Requirements.
Qualifications: Not explicitly given; maybe none.
Skills: maybe communication skills etc. Could be extracted from bullet points: excellent written and verbal communication skills, etc.
Benefits: The list after "Where Great Benefits Lead To a Life Fulfilled." includes Competitive Pay Medical/Dental/Vision/401K opportunities Travel discounts Credit Union Membership Tuition Reimbursement Professional Counseling & Family Support Growth and Development Opportunities Benefit eligibility will vary by position. So we have benefits.
Pay: The posting mentions "Competitive Pay" but not specific amount. According to rule: do NOT create Pay section unless posting actually states them. It says "Competitive Pay" but no specific figure. Is that considered stating them? It says "Competitive Pay" as a phrase, but not a number. The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Competitive Pay" as a benefit, but not a specific amount. However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." The phrase "Competitive Pay" is stating that pay is competitive, but not a specific figure. Might be considered stating pay exists. However they also said "Prefer a few substantive sections over many thin ones." Might be okay to include Pay section with just that statement? But they also said never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "Competitive Pay" is not filler; it's a statement. So we could include Pay section with
Competitive Pay
. However they also have Benefits section that includes many items; Pay could be separate.
Schedule: The posting mentions "Available to work a flexible schedule to include weekends and holidays." That's schedule info. So we can include Schedule section with that bullet.
Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule.
We need to avoid repeating job title as heading. Not include Job ID.
We need to use
- for any list of duties/requirements/benefits. For prose use
.
We need to preserve all substantive information; do not invent or summarize away detail.
Let's extract each piece.
About the role: The first sentences: "Are you looking for a place where meaningful moments are made together? We make vacation dreams come true for travelers around the world in a supportive, friendly, and beautiful work environment. As a Coordinator Customer Relations, you will assist in providing our Owners/guests with experiences and events to make memorable vacation memories, where meaningful moments are made together. Where Great Benefits Lead To a Life Fulfilled."
We could combine into a paragraph.
Responsibilities: The typical day list (6 items) plus Guest Experience standards (4 items). Could combine into one list under Responsibilities.
Requirements: The "To Become a Coordinator Customer Relations" bullet points (4 items). Could be requirements.
Skills: The communication skills bullet: "Enjoy talking with guests by phone and/or in person with excellent written and verbal communication skills." Also maybe "Interact with colleagues and guests professionally and promptly." Could be considered skill. But we already have those in responsibilities. Might be better to put skills separate: excellent written and verbal communication skills, professional interaction, etc. However to avoid duplication, we could keep skills as a short list: excellent written and verbal communication skills; ability to interact professionally; etc. But we need to preserve all substantive information; if we move some items to skills, we must not lose them elsewhere. Could duplicate? Better to keep responsibilities as duties, and skills as separate list of abilities needed.
Let's parse:
From "Guest Experience And Company Standards":
- Welcome and greet guests and anticipate and address their needs.
- Interact with colleagues and guests professionally and promptly.
- Enjoy talking with guests by phone and/or in person with excellent written and verbal communication skills.
- Always follow company policies and safety procedures.
These could be considered responsibilities as well. But we can assign some to skills: excellent written and verbal communication skills; professional interaction; following policies.
But we need to avoid duplication. Perhaps better to treat the "Guest Experience And Company Standards" as responsibilities (they are duties). Then skills could be just "excellent written and verbal communication skills". However that seems thin.
Alternatively, we could combine responsibilities and skills into one section "Responsibilities" and not have a separate Skills section. The instruction says to include a section ONLY when the posting has real, specific content for it. If we don't have distinct skills beyond those already covered, we could omit Skills section.
Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule.
Check if we have content for each.
About the role: yes.
Responsibilities: typical day list + Guest Experience standards.
Requirements: To Become a Coordinator Customer Relations bullet points.
Benefits: list after "Where Great Benefits Lead To a Life Fulfilled."
Pay: "Competitive Pay" statement.
Schedule: "Available to work a flexible schedule to include weekends and holidays."
We must not include filler like "Benefit eligibility will vary by position" - that's okay as part of benefits.
Now format.
We need
About the role
then ...
.
For lists: .
We need to preserve all substantive information; do not invent or summarize away detail.
Let's craft About the role paragraph:
"Are you looking for a place where meaningful moments are made together? We make vacation dreams come true for travelers around the world in a supportive, friendly, and beautiful work environment. As a Coordinator Customer Relations, you will assist in providing our Owners/guests with experiences and events to make memorable vacation memories, where meaningful moments are made together. Where Great Benefits Lead To a Life Fulfilled."
That's all.
Now Responsibilities: combine typical day list and Guest Experience standards.
Typical day list items:
- Communicates with preview tour customer via telephone before their scheduled arrival and tour date.
- You will offer Concierge-style services to guests coming to stay with us on a promotional vacation package.
- Provides detailed information about property amenities.
- Engages customers in conversation regarding their stay, property services, and area attractions/offerings.
- Identifies special customer needs and arranges to have those needs fulfilled upon customer arrival.
- Addresses customers' service needs in a professional, positive, and timely manner.
Guest Experience standards:
- Welcome and greet guests and anticipate and address their needs.
- Interact with colleagues and guests professionally and promptly.
- Enjoy talking with guests by phone and/or in person with excellent written and verbal communication skills.
- Always follow company policies and safety procedures.
We need to keep the exact phrasing. Ensure we keep punctuation.
Now Requirements: To Become a Coordinator Customer Relations bullet points:
- Available to work a flexible schedule to include weekends and holidays.
- Reach overhead and below the knees, perform bending, twisting, pulling, and stooping, and be able to stand, sit, or walk for an extended period of time.
- Lift/Carry/Push/Pull Items that Weigh up to 10lbs without assistance.
- Position may require background and drug screening contingent on company policy in accordance with applicable legal requirements.
Note: The first bullet about schedule overlaps with Schedule section; but we have schedule as separate. Might duplicate. However we could move schedule bullet to Schedule section and not include in Requirements. But the bullet is under "To Become a Coordinator Customer Relations". It is a requirement. However we also have schedule info elsewhere. To avoid duplication, we could keep schedule bullet under Requirements and not have separate Schedule section, but we have schedule info also in that bullet. The rule: we should not create Schedule section unless posting actually states them. It does state schedule flexibility. So we could have Schedule section with that bullet. Then we should not duplicate it in Requirements. So we need to decide where to place schedule info. Since it's a requirement, but also schedule. The instruction: "Prefer a few substantive sections over many thin ones." Could combine schedule into Requirements. But they also said never create Schedule section unless posting actually states them. It does state schedule, but we could still include Schedule section. However to avoid thin sections, maybe we put schedule under Requirements and not have separate Schedule section. However we also have Benefits, Pay, etc. The schedule bullet is just one line; making a separate Schedule section with one bullet might be thin but still substantive. The instruction: "Prefer a few substantive sections over many thin ones." So maybe better to include schedule within Requirements to avoid a thin Schedule section. But we also have Pay section which is just "Competitive Pay". That's also thin. Could combine Pay into Benefits? But they said only create Pay section if posting actually states them. It does state "Competitive Pay". Could be thin but still substantive. However we could also incorporate Pay into Benefits as part of benefits list (they already listed Competitive Pay as part of benefits). Actually the benefits list includes "Competitive Pay Medical/Dental/Vision/401K opportunities". So Pay is already part of benefits line. So we could omit separate Pay section and just keep Benefits section that includes Competitive Pay. That would avoid thin Pay section.
Thus sections: About the role, Responsibilities, Requirements, Benefits.
We need to check if we have any other distinct content for Skills: maybe not needed.
Thus we will have:
About the role
...
Respons