Guest Room Attendant
Naples Beach Club, A Four Seasons Resort · Naples, FL · 1 mo ago
On-siteCustomer ServiceFull-time
We need to output only HTML fragment, with headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can include other headings? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need separate sections for Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which content maps.
We have:
- About The Role (heading in source). Contains description: "Cleans guest rooms to exacting standards." Then "Essential Functions What you will do:" list of duties. Then "Non-essential Functions Assists with responsibilities and duties in the absence or heavy volume in the areas of Lobby Attendant and House Attendant."
Thus we can put that under
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Remove boilerplate like EEO, legal, navigation, etc. Must preserve substantive info. We need to parse the posting. Content: - About Four Seasons (intro) – maybe not needed as heading? Not in list of allowed headings. Could be part of a
before sections? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can include other headings? It says use for section headings (e.g. ...). Likely we should only use those headings for sections we include. The intro about Four Seasons could be a
before first heading. - About the location: description of Naples Beach Club. Could be part of About the role? Not exactly. Might be considered "About the role"? Actually "About The Role" heading present. So we should have
About the role
and include the description of role and location? The location description is separate but could be part of role context. We'll include it under About the role as prose. - Essential Functions: list of duties. Should go under Responsibilities (or maybe under About the role?). The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need separate sections for Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which content maps.
We have:
- About The Role (heading in source). Contains description: "Cleans guest rooms to exacting standards." Then "Essential Functions What you will do:" list of duties. Then "Non-essential Functions Assists with responsibilities and duties in the absence or heavy volume in the areas of Lobby Attendant and House Attendant."
Thus we can put that under About the role
(or maybe Responsibilities). But we have both About the role and Responsibilities as possible headings. The source already has "About The Role". We could treat that as About the role section, and then Responsibilities could be a subsection? But instruction says use for section headings (e.g. About the role, Responsibilities...). It doesn't forbid having both About the role and Responsibilities. However we should avoid thin sections. Maybe combine About the role and Responsibilities into one section? But we need to follow instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are possible headings we can use. It doesn't say we must use all. We should include sections only when posting has real specific content. So we need to decide which headings have content.
Let's map:
- About the role: we have description of role and location. So we can have About the role.
- Responsibilities: we have essential functions list (duties). Could be separate.
- Requirements: we have "What You Bring": high school education or equivalent experience, prior experience preferred but not required, ability to read, write and speak English, flexible schedule, ability to work weekends and holidays, must possess legal work authorization in the United States. That's requirements.
- Qualifications: maybe overlapping with requirements. Could treat "Prior experience preferred but not required" as qualification? But we already have requirements. Could combine.
- Skills: not explicitly listed. Could infer ability to read/write/speak English, attention to detail, etc. Not explicit. Might not have specific skills section.
- Benefits: we have "What We Offer": list of benefits: Lucrative salary! Market-leading benefits package that includes: Medical, Dental, Vision, and 401K with employer matching all starting at 30 days! Time off plans starting on the day of hire! Opportunity to be part of cohesive team... Complimentary and discounted hotel stays around the world! Wellbeing and mental health initiatives... Embracement and promotion of diversity... Complimentary employee meals and beverages! Tuition reimbursement! Also links to learn more (but we remove navigation). So we have benefits content.
- Pay: The posting says "Lucrative salary!" but no specific amount. That's vague. According to 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. "Lucrative salary!" is not a specific number, but it's still a statement about pay. Is that considered filler? It's vague but still mentions salary. The instruction says avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". "Lucrative salary!" is not exactly those but still vague. Might be considered filler? The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state something about salary (lucrative salary!). So we could include Pay section with that statement. However we also have Benefits section that includes "Lucrative salary!" as part of benefits. Might be redundant. Better to put salary under Benefits? But they said Benefits section for benefits like medical etc. Pay separate for salary. Since they mention "Lucrative salary!" we could include Pay section with that phrase. But we need to avoid filler; "Lucrative salary!" is somewhat filler but it's the only pay info. I'd lean to include Pay section with that statement.
- Schedule: we have "Ability to work weekends and holidays." and "flexible schedule". That's schedule info. So we can include Schedule section with that.
- Skills: Not explicit; we could omit.
- Qualifications: Could be same as Requirements; maybe we can omit Qualifications to avoid thin sections.
Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule.
We need to ensure we don't include boilerplate like EEO, legal, navigation, social media links, etc. Also remove duplicated lines.
Now craft HTML.
We'll start with a
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are possible headings we can use. It doesn't say we must use all. We should include sections only when posting has real specific content. So we need to decide which headings have content. Let's map: - About the role: we have description of role and location. So we can have About the role. - Responsibilities: we have essential functions list (duties). Could be separate. - Requirements: we have "What You Bring": high school education or equivalent experience, prior experience preferred but not required, ability to read, write and speak English, flexible schedule, ability to work weekends and holidays, must possess legal work authorization in the United States. That's requirements. - Qualifications: maybe overlapping with requirements. Could treat "Prior experience preferred but not required" as qualification? But we already have requirements. Could combine. - Skills: not explicitly listed. Could infer ability to read/write/speak English, attention to detail, etc. Not explicit. Might not have specific skills section. - Benefits: we have "What We Offer": list of benefits: Lucrative salary! Market-leading benefits package that includes: Medical, Dental, Vision, and 401K with employer matching all starting at 30 days! Time off plans starting on the day of hire! Opportunity to be part of cohesive team... Complimentary and discounted hotel stays around the world! Wellbeing and mental health initiatives... Embracement and promotion of diversity... Complimentary employee meals and beverages! Tuition reimbursement! Also links to learn more (but we remove navigation). So we have benefits content. - Pay: The posting says "Lucrative salary!" but no specific amount. That's vague. According to 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. "Lucrative salary!" is not a specific number, but it's still a statement about pay. Is that considered filler? It's vague but still mentions salary. The instruction says avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". "Lucrative salary!" is not exactly those but still vague. Might be considered filler? The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state something about salary (lucrative salary!). So we could include Pay section with that statement. However we also have Benefits section that includes "Lucrative salary!" as part of benefits. Might be redundant. Better to put salary under Benefits? But they said Benefits section for benefits like medical etc. Pay separate for salary. Since they mention "Lucrative salary!" we could include Pay section with that phrase. But we need to avoid filler; "Lucrative salary!" is somewhat filler but it's the only pay info. I'd lean to include Pay section with that statement. - Schedule: we have "Ability to work weekends and holidays." and "flexible schedule". That's schedule info. So we can include Schedule section with that. - Skills: Not explicit; we could omit. - Qualifications: Could be same as Requirements; maybe we can omit Qualifications to avoid thin sections. Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. We need to ensure we don't include boilerplate like EEO, legal, navigation, social media links, etc. Also remove duplicated lines. Now craft HTML. We'll start with a
for introductory Four Seasons description? The instruction says use
for prose. We can include a brief intro about Four Seasons and location as prose before first heading. But we must not repeat job title (which is not given explicitly). The posting didn't show job title; it's likely "Room Attendant" or similar but not in text. So fine. We'll produce:
Four Seasons is powered by our people... (the intro paragraph). Then location description as another
maybe. Then
About the role
with prose summarizing role: "Cleans guest rooms to exacting standards." plus maybe mention essential functions? But we have separate Responsibilities. Better: About the role could include the brief description and location. Then Responsibilities list. Let's extract location paragraph: "About the location: A rare gem on Florida’s Gulf Coast of Southwest Florida, Naples Beach Club, a Four Seasons Resort, is an exclusive collection of 156 luxurious beachfront private residences and a 222-room hotel all within a 125-acre walkable coastal village in the heart of Old Naples. Honoring local heritage and artfully reimagined for modern-day elegance, the resort includes residents-only facilities and amenities, a luxury spa and state-of-the-art well-being/fitness center, exquisite and diverse fine dining outlets, outdoor pursuits to include a tennis center, and an 18-hole golf course, bowling and movie theater experiences, and an exclusive private club. The first of its kind, the Naples Beach Club, a Four Seasons Resort, is paradise found." We'll put that as aunder About the role. Now Responsibilities: list of essential functions and non-essential functions. We'll create
- for each duty.
Essential functions list:
- Prepares the guest room for arrival and daytime service.
- Removes dirty towels and sheets and replaces them with clean ones from the Linen Closet.
- Cleans, dusts, and sanitizes all areas of the Guest Room (bedroom, living room, dining room and bathroom) according to procedure.
- Makes bed.
- Vacuums carpet and cleans marble and tile areas.
- Removes Rooms service trays, dishes and carts to service landings.
- Replaces used cups, saucers, spoons and glasses from the Minibar with clean china, glasses and cutlery from the Room Attendant pantry.
- Removes garbage from bins in bedroom and bathroom.
- Submits all maintenance issues in guestrooms, Public Areas and Back of house areas to the Engineering department through designated work systems and brings them to the attention of the Housekeeping management.
- Add special touches to the guestrooms to enhance the guest experience. For example micro fiber cloth, book marks, cable ties
- Restocks used amenities such as shampoo, lotions, cotton balls, stationery, pens and coffee, tea and sugar sachets.
- Complies with Four Seasons’ Category One and Category Two Work Rules and Standards of Conduct as set forth in EmPact.
- Works harmoniously and professionally with co-workers and supervisors.
Non-essential: Assists with responsibilities and duties in the absence or heavy volume in the areas of Lobby Attendant and House Attendant.
We'll include that as a list item.
Now Requirements: from "What You Bring":
- High school education or equivalent experience.
- Prior experience preferred but not required.
- Ability to read, write and speak English.
- A successful candidate will have a flexible schedule, ability to work weekends and holidays.
- Must possess legal work authorization in the United States.
We could split schedule into Requirements? But schedule also separate. We'll keep schedule separate.
Thus Requirements list includes high school, prior experience preferred, English ability, legal work authorization.
Now Benefits: list from "What We Offer":
- Lucrative salary! (maybe we move to Pay)
- Market-leading benefits package that includes: Medical, Dental, Vision, and 401K with employer matching all starting at 30 days!
- Time off plans starting on the day of hire!
- An opportunity to be a part of a cohesive team in an inclusive work environment!
- Complimentary and discounted hotel stays around the world!
- Wellbeing and mental health initiatives and focused company!
- Embracement and promotion of diversity in our workplace!
- Complimentary employee meals and beverages!
- Tuition reimbursement!
We'll make a
- for benefits.
Pay: "Lucrative salary!" as a
. Schedule: "Ability to work weekends and holidays." and "flexible schedule". We'll make a
maybe combine: "Flexible schedule with ability to work weekends and holidays." Now ensure we don't include any boilerplate like EEO, legal, social media links, etc. Also remove duplicated lines: The posting had repeated EEO statements; we omit. Now produce HTML fragment. We need to output only HTML, no markdown fences. Let's craft:
Four Seasons is powered by our people. We are a collective of individuals who crave to become better, to push ourselves to new heights and to treat each other as we wish to be treated in return. Our team members around the world create amazing experiences for our guests, residents, and partners through a commitment to luxury with genuine heart. We know that the best way to enable our people to deliver these exceptional guest experiences is through a world-class employee experience and company culture. At Four Seasons, we believe in recognizing a familiar face, welcoming a new one and treating everyone we meet the way we would want to be treated ourselves. Whether you work with us, stay with us, live with us or discover with us, we believe our purpose is to create impressions that will stay with you for a lifetime. It comes from our belief that life is richer when we truly connect to the people and the world around us.