Houseperson

The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and apply the rules. First, I need to identify the sections: - The posting has "Key Responsibilities" - this maps to "Responsibilities" heading - "Requirements" section with "Qualifications" subsection - "Physical And Scheduling Requirements" - this could be part of Requirements or separate - Benefits are mentioned at the top: "Benefits available to all associates include: a quarterly bonus program, paid time off (PTO and holidays), 401k with Employer Match, Option to be paid daily with DailyPay, competitive wages, hotel discounts, and so much more!" - There's also schedule info: "This is an on-site position with first- and second-shift opportunities. Weekend and holiday availability is required." - Pay: "competitive wages" mentioned but no specific numbers Rules: - Use

for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) - Use

• for lists,

  for prose - Do NOT repeat job title as heading - Do NOT put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove boilerplate (cookie/navigation/legal/EEO/scam-warning) - Include section ONLY when posting has real, specific content - Never emit heading followed by filler/placeholder text - Never create Pay/Schedule/Benefits sections unless posting actually states them - Prefer few substantive sections over many thin ones - Output ONLY HTML fragment, no /, no markdown code fences Let me structure this: 1. About the role - there's a description paragraph: "Join our hospitality team and help create a clean, welcoming experience for every guest. The Houseperson supports housekeeping operations by maintaining public areas, organizing supplies, assisting room attendants, responding to guest requests, and completing basic maintenance tasks. This is an on-site position with first- and second-shift opportunities. Weekend and holiday availability is required." 2. Responsibilities - the "Key Responsibilities" list 3. Requirements - the "Requirements" section has "Qualifications" and "Physical And Scheduling Requirements". I could combine or separate. The rules mention "Requirements" and "Qualifications" as possible headings. Since there's a "Qualifications" subsection, I'll use "Requirements" as main heading with "Qualifications" as sub-list? But the rule says use

  for section headings. I think I should have separate sections: "Requirements" and "Qualifications"? Actually the posting has "Requirements" then "Qualifications" as a subheading. But the rule says use

  for section headings like "Requirements, Qualifications". I'll make "Requirements" an h3 and include the qualifications list under it, and also physical/scheduling requirements. 4. Benefits - clearly listed 5. Schedule - mentioned: "on-site position with first- and second-shift opportunities. Weekend and holiday availability is required." Also in physical requirements: "availability for assigned shifts, including weekends, nights, and holidays." So schedule info exists. 6. Pay - only "competitive wages" mentioned, no specifics. The rule says never create Pay section unless posting actually states them. "competitive wages" is vague. I think I should not create a Pay section because it's not specific. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." For Benefits, it states them clearly. For Schedule, it states shift info. For Pay, only "competitive wages" which is generic. I'll omit Pay section. Let me draft HTML:

  About the role

  Join our hospitality team and help create a clean, welcoming experience for every guest. The Houseperson supports housekeeping operations by maintaining public areas, organizing supplies, assisting room attendants, responding to guest requests, and completing basic maintenance tasks. This is an on-site position with first- and second-shift opportunities. Weekend and holiday availability is required.

  Responsibilities

  • Clean and maintain hotel public areas, grounds, and parking areas according to company and brand standards.
  • Deliver towels, toiletries, rollaway beds, and other requested items promptly and courteously.
  • Assist room attendants, laundry, and maintenance teams as operational needs require.
  • Organize and properly handle linens, supplies, and cleaning materials.
  • Set up meeting rooms when applicable.
  • Perform basic troubleshooting or minor repairs, such as addressing a running toilet or leaking faucet.
  • Protect guest privacy and follow all safety, security, sanitation, and emergency procedures.
  • Assist guests with baggage when requested.
  • Report hazards, maintenance concerns, or security issues promptly.
  • Perform other related duties within the associate's training and capabilities.

  Requirements

  Qualifications

  - wait, the rule says use

  for section headings. Should I have both as separate h3? The posting has "Requirements" then "Qualifications" as a subheading. But the rule lists "Requirements, Qualifications" as examples. I think I should have "Requirements" as h3 and then include qualifications as a list under it, but the posting separates them. Actually the posting says "Requirements Qualifications Previous experience..." It might be that "Requirements" is a heading and "Qualifications" is a subheading. But the rule says use

  for section headings. I'll make "Requirements" an h3 and "Qualifications" an h3? That might be too many. The rule: "Prefer a few substantive sections over many thin ones." I'll combine: have "Requirements" h3, then a paragraph or list for qualifications, and another list for physical/scheduling requirements. But the posting has "Requirements" then "Qualifications" then "Physical And Scheduling Requirements". I'll create two sections: "Requirements" and "Physical & Scheduling Requirements"? Or just "Requirements" with two sub-lists. Since the rule says use

  for section headings, and "Qualifications" is listed as an example heading, I could do:

  Requirements

  Qualifications

  - but that's two h3s. Might be okay. Let me see the rule: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So both Requirements and Qualifications are example headings. The posting has both. I'll include both as separate h3 sections. But the posting's "Requirements" heading might be a parent. The text: "Requirements Qualifications Previous experience..." It seems like "Requirements" is a heading and "Qualifications" is a subheading. However, the content under "Qualifications" is a list of qualifications. Then "Physical And Scheduling Requirements" is another subheading. I'll structure as: - Requirements (h3) - maybe a brief intro? But there's no intro, just the subsections. - Qualifications (h3) - list - Physical & Scheduling Requirements (h3) - list But that's three h3s. Might be okay. Alternatively, combine Qualifications and Physical under Requirements. But the rule says prefer substantive sections. Each has specific content. Let me check the content: Qualifications: - Previous experience in a hotel, hospital, residential, or care-facility environment is preferred. - High school diploma or equivalent preferred. - Dependable, trustworthy, service-focused, and able to work independently or as part of a team. - Ability to communicate professionally with guests and coworkers and manage multiple priorities. Physical And Scheduling Requirements: - With or without reasonable accommodation, the associate must be able to stand and walk for extended periods; bend, reach, climb, and kneel; lift or carry up to 30 pounds; and push or pull up to 60 pounds. - The position may involve working outdoors in varying temperatures and requires availability for assigned shifts, including weekends, nights, and holidays. These are distinct. I'll make two sections: "Qualifications" and "Physical & Scheduling Requirements". But the rule says "Requirements" is an example heading. I could have "Requirements" as a heading with two sub-lists, but the rule says use

  for section headings, not subheadings. I think using multiple h3s is fine. I'll do:

  Qualifications

  ...

  Physical & Scheduling Requirements

  ...
  But the posting says "Requirements Qualifications" - maybe "Requirements" is the main heading. I'll include "Requirements" as an h3 with a short paragraph? There's no paragraph. I'll skip "Requirements" heading and go straight to "Qualifications" and "Physical & Scheduling Requirements". However, the rule says "Requirements" is an example heading. The posting has "Requirements" as a heading. I'll include it as an h3 and then have the two subsections as h3? That would be nested h3s which is not semantic. Better to have "Requirements" as h3 and then use
  for qualifications and another
  for physical, but they are distinct categories. I think the best is to have:

  Requirements

  Qualifications:

  ...

  Physical & Scheduling Requirements:

  ...
  But the rule says use

  for section headings. It doesn't forbid using

  for subheadings. However, the example headings include "Qualifications". I'll make "Qualifications" an h3 and "Physical & Scheduling Requirements" an h3. But then "Requirements" is missing. I'll include "Requirements" as an h3 with a brief intro? There's no intro. The posting starts with "Requirements Qualifications Previous experience..." So maybe "Requirements" is just a label. I'll treat "Qualifications" and "Physical & Scheduling Requirements" as the two requirement sections. Let me look at the rule again: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So both Requirements and Qualifications are listed. I'll include both as separate h3 sections. But the posting has "Requirements" then "Qualifications" as a subheading. I'll make "Requirements" an h3 and then "Qualifications" an h3? That would be two h3s in a row. Might be okay. Alternatively, I could combine: "Requirements & Qualifications" but the rule says use those headings. I'll decide: Since the posting has a "Requirements" heading and then "Qualifications" as a subheading, but the content under "Requirements" is only the subsections, I'll create an h3 for "Requirements" and then include the qualifications and physical requirements as lists under it, but with bold labels? But the rule says use

  • for lists. I can have two separate lists with a preceding

    for each label. But the rule says "use

    for section headings". It doesn't say I can't have multiple h3s. I'll do:

    Requirements

    Qualifications

    ...

    Physical & Scheduling Requirements

    ...
    But that's three h3s. Might be acceptable. However, the rule: "Prefer a few substantive sections over many thin ones." So maybe combine Qualifications and Physical under one "Requirements" h3 with two lists. I'll do that: