Dishwasher

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: - Compensation Range: $15.92 - $18.50 / Hour (this is Pay information) - Overview: description of the role - Why Join our Team: benefits and perks (multiple subsections) - What You'll Do: responsibilities - Your Background: requirements/qualifications - Who We Are: company info (but this might be boilerplate) 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 (the page already shows it) - Do NOT put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions - Include a section ONLY when posting has real, specific content for it - Never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") - 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 Now, let's map the content: 1. Compensation Range: $15.92 - $18.50 / Hour -> This is Pay information. Should create a Pay section. 2. Overview: "For those who enjoy rolling up their sleeves..." -> This is "About the role" or similar. Could be "About the Role" section. 3. Why Join our Team: This contains multiple subsections: - Steady Hours, Flexible Life (scheduling info) - Faster Pay (pay advance) - Free shift meals and discount - Benefits That Have Your Back (medical, dental, vision, etc.) - Grow With Us (training, advancement, education) - Perks, Recognition & Community (perks, recognition, HELP Fund, community events) - Awards (Fortune 100, etc.) This is essentially Benefits and Perks. Could be a "Benefits" section with sub-lists. But the rule says use

  for section headings like Benefits. I could create a Benefits section and include all these as lists. However, the rule says "Prefer a few substantive sections over many thin ones." So maybe one Benefits section with multiple lists. But note: "Schedule" is also a heading type. The posting mentions "Flexible scheduling with full-time or part-time opportunities". That could be a Schedule section. But the rule says never create Schedule section unless posting actually states them. It does state scheduling info. However, the heading types listed include Schedule. But the user said "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So Schedule is an allowed heading. But we should only include if there's real content. There is: "Flexible scheduling with full-time or part-time opportunities to fit your life". That's schedule info. Could be a Schedule section. But also "Steady Hours, Flexible Life" includes "High-volume restaurant with consistent hours". That's schedule-related. Maybe combine into a Benefits section? The rule says "Benefits" is a heading. The posting has "Benefits That Have Your Back" which is clearly benefits. The other items are perks, recognition, etc. Could all go under Benefits. But also "Faster Pay" is about pay advance, which is a benefit. "Free shift meals and 25% discount" is a perk. "Grow With Us" is career development. "Perks, Recognition & Community" is perks. "Awards" is company recognition. I think a single "Benefits" section with multiple sub-lists (or a list with categories) would be appropriate. However, the HTML structure: we can use

  Benefits

  then
  with
  • items. But the items are grouped. Could use nested lists or separate lists with headings? But we cannot use

    because only

    allowed for section headings. The rule says "use

    for section headings". It doesn't forbid other headings, but likely they want only

    for top-level sections. Could use or just list items with bold text? But the rule says use

    • for any list of duties/requirements/benefits. So we can have a list where each item is a benefit. Could group them with line breaks? But better to have a single list with all benefits. But the posting has distinct categories. Could we create multiple

      sections? Like "Benefits", "Perks", "Career Development"? But the rule says prefer few substantive sections. The example headings include Benefits, Pay, Schedule. So maybe we should have separate sections for Pay, Benefits, Schedule? Let's see. The posting has: - Compensation Range (Pay) - Flexible scheduling (Schedule) - Benefits (medical, dental, etc.) - Perks (discounts, meals, etc.) - Career growth (training, advancement, education) - Recognition and community (HELP Fund, awards) The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states all three: Pay (compensation range), Schedule (flexible scheduling), Benefits (medical, etc.). So we could create three sections: Pay, Schedule, Benefits. But the Benefits section would include medical, dental, vision, etc. The Perks and Career growth could be part of Benefits or separate. The rule says "Prefer a few substantive sections over many thin ones." So maybe combine Perks and Career growth into Benefits. But the posting also has "Why Join our Team" which is a marketing section. We need to preserve all substantive information. So we must include all those details. Let's decide on sections: 1. Pay: compensation range. 2. Schedule: flexible scheduling, full-time/part-time, consistent hours. 3. Benefits: medical, dental, vision, prescription, virtual care, mental health, paid vacation/sick time, free shift meals, 25% discount, faster pay (50% earned wages next day), GED/Associate degree programs, training, advancement, perks (cell phone, gym, movie, theme park), recognition awards, HELP Fund, community events, awards (Fortune 100, etc.) But "Faster Pay" is a pay-related benefit, but it's not the base pay. Could be under Benefits. Alternatively, we could have a single "Benefits & Perks" section. But the rule explicitly lists "Benefits" as a heading example. And "Pay" and "Schedule" are separate. Since the posting has distinct info for each, I'll create three sections: Pay, Schedule, Benefits. But the posting also has "Overview" which is about the role. That should be "About the Role" section. Then "What You'll Do" -> Responsibilities. "Your Background" -> Requirements (or Qualifications). "Who We Are" -> Company description. But this might be boilerplate? It's specific to the company, but it's not a standard section like "About the Company". The rule says include a section ONLY when posting has real, specific content for it. The "Who We Are" is specific to The Cheesecake Factory. It's not generic EEO boilerplate (though it includes EEO statement at the end). The EEO statement is boilerplate: "We are an equal opportunity employer...". That should be removed. The rest is company description. Could be an "About the Company" section. But the rule doesn't list that as an example heading. The example headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About the Company" is not listed. However, the rule says "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." means these are examples, not exhaustive. But we should stick to those if possible. The posting has "Who We Are" which is company info. Could be considered "About the Company". But the rule says "Preserve ALL substantive information". So we should include it. But maybe we can fold it into a short

      at the end? The rule says "fold minor metadata into a short

      or drop it." Company description might be considered minor metadata? But it's substantive about the employer. However, the job posting is for a dishwasher at The Cheesecake Factory. The company description is marketing. The user might want it. But the rule says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". The EEO statement is boilerplate. The company description is not boilerplate. But it's not a standard section. I think we can include it as an "About the Company" section with

      . But the example headings don't include it. However, the rule says "use

      for section headings (e.g. ...)". It doesn't forbid other headings. But to be safe, maybe we can include it as a section with heading "About the Company". But the rule says "Prefer a few substantive sections over many thin ones." This might be thin. But it has several sentences. I'll include it. Alternatively, we could omit it because the page already shows the company name? The user said "Do NOT repeat the job title as a heading (the page already shows it)". The company name might be shown elsewhere. But the posting includes "Who We Are" as a section. I'll include it as a section. Now, let's structure: -

      About the Role

      with

      for overview. -

      Pay

      with

      for compensation range. -

      Schedule

      with
      • for scheduling details. -

        Benefits

        with
        • for all benefits, perks, career growth, recognition, etc. -

          Responsibilities

          with
          • for "What You'll Do". -

            Requirements

            with
            • for "Your Background". -

              About the Company

              with

              for "Who We Are" (excluding EEO boilerplate). But note: "Faster Pay – access up to 50% of your earned wages the next day (exclusions apply)" is a benefit, not base pay. So it goes under Benefits. "Free shift meals and 25% discount when dining with friends and family" -> benefit. "Paid vacation and sick time" -> benefit. "Medical, Dental, Vision, and Prescription coverage options" -> benefit. "Medical coverage starting as low as $12 per pay period" -> benefit detail. "Virtual Care and no cost online mental health services" -> benefit. "World class training designed to support your personal and professional growth" -> benefit/career. "Career advancement opportunities – over half of our managers are promoted from within" -> benefit. "No cost GED or Associate Degree programs" -> benefit. "Perks and discounts including cell phone, gym, movie, and theme park savings" -> benefit. "Employee recognition and appreciation awards" -> benefit. "HELP Fund (Hardship and Emergency Lifeline Program) for moments that matter" -> benefit. "Opportunities to give back through community and charity events" -> benefit. "Join an award-winning