Evening Housekeeper

We need to output HTML fragment only, with

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. Let's parse the posting. Job title: Evening Housekeeper. Location: Canandaigua, NY. Schedule: 4PM-8PM Part Time Weekdays. Every Other Weekend As Well. DUTIES list: many bullet-like statements. REQUIREMENTS: One-year experience working with laundry. High school diploma or equivalent. Must be able to work as a team member. Must be able to work weekends Ability to work effectively and efficiently. Positive and upbeat attitude. About us: description of facility. We need sections: About the role (maybe summary of job?), Responsibilities (duties), Requirements (requirements), Qualifications (maybe combine with requirements? but we have separate sections: Qualifications, Skills). The posting includes "One-year experience working with laundry" (qualification/experience), "High school diploma or equivalent" (qualification), "Must be able to work as a team member" (skill?), "Must be able to work weekends" (schedule?), "Ability to work effectively and efficiently" (skill), "Positive and upbeat attitude" (skill/attribute). We need to decide what to put where. We have no explicit Benefits, Pay, Schedule details beyond schedule info: "4PM-8PM Part Time Weekdays. Every Other Weekend As Well." That's schedule info. So we can create a Schedule section with that content. We have no explicit Pay or Benefits details. The "About us" mentions "excellent compensation, a comprehensive benefits package". That's vague but not specific numbers. According to rules: do NOT create Pay/Schedule/Benefits sections unless the posting actually states them. For Benefits, we have "excellent compensation, a comprehensive benefits package" - that's somewhat generic but still mentions benefits package. Is that considered specific? It says "comprehensive benefits package" but no details. The rule says: 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. "excellent compensation, a comprehensive benefits package" is vague but still states that there is a benefits package and compensation. It's not a specific detail but it's a statement. I'd consider that as stating benefits exist, but not specifics. The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them in a general sense. However, they also say "Prefer a few substantive sections over many thin ones." Might be better to omit Benefits and Pay sections because they are not substantive. The schedule is specific: 4PM-8PM Part Time Weekdays. Every Other Weekend As Well. That's specific enough for Schedule section. Thus sections: About the role (maybe we can use About us? Actually About the role could be a brief summary: "Ontario Center is hiring a Evening Housekeeper in Canandaigua, NY." But we should not repeat job title as heading. We can put a short paragraph about the role: maybe combine location and schedule? But schedule will be its own section. About the role could be a brief description: "Evening Housekeeper position responsible for maintaining cleanliness and sanitation in a long-term care facility." However we must not invent or summarize away detail. We need to preserve ALL substantive information; do NOT invent or summarize away detail. So we cannot add invented description not in posting. We can only use what's given. The posting includes: "Ontario Center is hiring a Evening Housekeeper in Canandaigua, NY. 4PM-8PM Part Time Weekdays. Every Other Weekend As Well." That's about the role. Also "About us:" paragraph about facility. That could be About the role? Actually About us is about the facility, not the role. The rule says we can have About the role section. We could put the hiring sentence there. But we also have About us paragraph which could go under About the role? Might be better to have About the role: the hiring sentence. And maybe we could also include the facility description under About the role? But that's about the facility, not the role. However we could treat it as About the role context. The rule: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have About the role section containing the hiring sentence and maybe the facility description? The facility description is substantive information about the employer; we must preserve ALL substantive information. So we need to include it somewhere. Could be under About the role or maybe we could create a separate section like "About the facility" but not allowed headings list only those. So we put it under About the role. Thus About the role: "Ontario Center is hiring a Evening Housekeeper in Canandaigua, NY. 4PM-8PM Part Time Weekdays. Every Other Weekend As Well. Ontario Center for Rehabilitation and Healthcare is a long-term care facility that provides the highest possible quality of care and quality of life for all Health Facility residents. The facility provides a versatile nursing-home environment that encourages creativity among residents, managers, and staff. In addition to an emphasis on individuality and self-determination, the nursing home is viewed as home as much as a medical institution, with the residents’ psychosocial needs deserving a prominence at least equal to their medical condition. At Ontario Center, we offer a friendly working environment, excellent compensation, a comprehensive benefits package, professional growth & stability, innovative training programs, and more. Ontario Center is a proud member of the Centers Health Care consortium." But note: The schedule appears also in About the role; we also have a Schedule section. To avoid duplication, we could keep schedule only in Schedule section and not repeat in About the role. However the rule says preserve ALL substantive information; we can't omit schedule info. If we put schedule in Schedule section, we still need to include it somewhere. It's okay to have it only in Schedule section and not repeat. The About the role could then be just the hiring sentence without schedule? But the hiring sentence includes schedule; we could split: "Ontario Center is hiring a Evening Housekeeper in Canandaigua, NY." Then schedule separate. That preserves all info (the hiring sentence without schedule still conveys hiring and location). The schedule is captured in Schedule section. That seems acceptable. Thus About the role: "Ontario Center is hiring a Evening Housekeeper in Canandaigua, NY." Responsibilities: list of duties. Requirements: maybe we separate Requirements and Qualifications? The posting has REQUIREMENTS heading with items. We could treat those as Requirements. Qualifications could be empty? But we should not create a section without real specific content. So we omit Qualifications if no distinct content. Skills: we could extract skill-like items: "Ability to work effectively and efficiently", "Positive and upbeat attitude", "Must be able to work as a team member". Those could go under Skills. However the Requirements already include those. To avoid duplication, we could put all under Requirements and omit Skills. But we need to follow headings list; we can omit Skills if no specific content beyond what's already in Requirements. However we have "One-year experience working with laundry" and "High school diploma or equivalent" which are qualifications/experience. Could put those under Qualifications. Then Requirements could be things like "Must be able to work as a team member", "Must be able to work weekends", "Ability to work effectively and efficiently", "Positive and upbeat attitude". That seems reasonable. Thus: Qualifications: - One-year experience working with laundry. - High school diploma or equivalent. Requirements: - Must be able to work as a team member. - Must be able to work weekends. - Ability to work effectively and efficiently. - Positive and upbeat attitude. Skills: maybe we could combine with Requirements; but we already have Skills heading; we could put the same items under Skills? That would duplicate. Better to omit Skills if we already covered under Requirements. But we need to decide: The posting didn't separate skills; we can interpret. The rule: Prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one Requirements section? But we have both headings allowed. However we could have only Requirements section containing all items (experience, diploma, teamwork, weekends, efficiency, attitude). That's one section. Then we omit Qualifications and Skills. That's fewer sections. But we also have About the role, Responsibilities, Requirements, Schedule. That's four sections. That seems good. Check if we need Benefits: we have "excellent compensation, a comprehensive benefits package" but we omitted Benefits section. According to rule, we should not create Benefits unless posting actually states them. It does state them in a vague way. But we could include a Benefits section with that sentence. However that would be thin but still substantive? It's a statement about benefits. The rule says prefer few substantive sections over many thin ones. Adding a Benefits section with just that sentence might be thin. I'd lean to omit Benefits. Schedule: we have specific schedule. Thus final HTML:

About the role

Ontario Center is hiring a Evening Housekeeper in Canandaigua, NY.

Responsibilities

• Knows how to sweep, dust mop and mop floors
• Knows how to change and remove trash
• Knows how to vacuum
• Knows how to follow cleaning guidelines
• Notifies supervisor when supplies are low
• Keeps Housekeeping carts clean and in good working order
• Properly stores equipment, tools, and supplies
• Keeps a log of areas that are cleaned
• Reports any mechanical or equipment condition to supervisor
• Reports any questionable resident conditions to supervisor

Requirements

• One-year experience working with laundry
• High school diploma or equivalent
• Must be able to work as a team member
• Must be able to work weekends
• Ability to work effectively and efficiently
• Positive and upbeat attitude

Schedule

4PM-8PM Part Time Weekdays. Every Other Weekend As Well.

Check for any leftover info: The About us paragraph about facility is omitted. We omitted that substantive info. That violates "Preserve ALL substantive information". We need to include that somewhere. Could we incorporate it into About the role? The About the role currently only has hiring sentence. We could add the facility description there as well, making About the role substantive. That would preserve all info. Let's do that. Thus About the role: combine hiring sentence and facility description. About the role paragraph: "Ontario Center is hiring a Evening Housekeeper in Canandaigua, NY. Ontario Center for Rehabilitation and Healthcare is a long-term care facility that provides the highest possible quality of care and quality of life for all Health Facility residents. The facility provides a versatile nursing-home environment that encourages creativity among residents, managers, and staff. In addition to an emphasis on individuality and self-determination, the nursing home is viewed as home as much as a medical institution, with the residents’ psychosocial needs deserving a prominence at least equal to their medical condition. At Ontario Center, we offer a friendly working environment, excellent compensation, a comprehensive benefits package, professional growth & stability, innovative training programs, and more. Ontario Center is a proud member of the Centers Health Care consortium." That includes all About us info. Good. Now we have schedule separate. Check for duplicate: The About the role includes "excellent compensation, a comprehensive benefits package". That's benefits info but we are not making a Benefits section; it's okay to be inside About the role. Now ensure we didn't repeat job title as heading: we didn't