Host

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: $7.25 - $15.00 / Hour (this is Pay information) - Overview: description of the role - Why Join our Team: benefits, perks, etc. - What You'll Do: responsibilities - Your Background: requirements/qualifications - Who We Are: company info 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 boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions) - Include 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 to appropriate sections: 1. Pay: The posting has "Compensation Range $7.25 - $15.00 / Hour" - this is specific pay info, so include a Pay section. 2. About the role: The "Overview" paragraph describes the role. Could be "About the role" or "Overview". Use

  About the role

  with a

  . 3. Responsibilities: "What You'll Do" is a list of duties. Use

  Responsibilities

  with
  • . 4. Requirements/Qualifications: "Your Background" lists requirements. Could be "Requirements" or "Qualifications". Use

    Requirements

    with
    • . 5. Benefits: "Why Join our Team" has multiple subsections: "Steady Hours, Flexible Life", "Benefits That Have Your Back", "Grow With Us", "Perks, Recognition & Community". These are benefits and perks. Should we combine into one Benefits section? The rules say use

      for section headings like Benefits. Since there are multiple categories, we could have a Benefits section with sub-lists, but the rule says use

      • for any list. Could structure as a single Benefits section with multiple lists or separate sections? The rule says "Prefer a few substantive sections over many thin ones." So maybe one Benefits section with multiple sub-lists? But the headings are only

        . Could use

        Benefits

        then include multiple
        lists, maybe with labels? However, the rule says use
        • for any list of duties/requirements/benefits, and

          for prose. It doesn't forbid multiple lists under one heading. But the original has subheadings like "Steady Hours, Flexible Life", "Benefits That Have Your Back", etc. Those could be

          ? But the rule only mentions

          for section headings. It says "use

          for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't mention

          . So we should probably keep only

          headings. Could we make each subcategory a separate

          ? That would create many thin sections. The rule says prefer few substantive sections over many thin ones. So maybe combine into one Benefits section with multiple lists, each preceded by a

          label? But the rule says use

          • for any list. It doesn't say we can't have multiple
            under one

            . That seems acceptable. Alternatively, we could create separate sections for each: "Schedule" for "Steady Hours, Flexible Life", "Benefits" for "Benefits That Have Your Back", "Growth" for "Grow With Us", "Perks" for "Perks, Recognition & Community". But the rule says only use headings like Benefits, Pay, Schedule. "Grow With Us" might be "Career Development" but not in the example list. The example list includes "Benefits, Pay, Schedule". So we could have "Schedule" for flexible scheduling, "Benefits" for medical etc., "Career Development" not in list. But the rule says "use

            for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., so we can use other relevant headings? But it says "include a section ONLY when the posting has real, specific content for it". The posting has specific content for each of those subcategories. However, the rule also says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state them. But we should avoid many thin sections. Let's see: "Steady Hours, Flexible Life" includes scheduling info and pay advance. "Benefits That Have Your Back" includes medical, dental, etc. "Grow With Us" includes training, advancement, education. "Perks, Recognition & Community" includes discounts, recognition, hardship fund, community events, awards. We could create: - Schedule (for flexible scheduling, steady hours) - Benefits (for medical, dental, vision, paid vacation, virtual care) - Career Development (for training, advancement, education) - Perks (for discounts, recognition, hardship fund, community) But the rule says "Prefer a few substantive sections over many thin ones." So maybe combine into one "Benefits" section that includes all these? The heading "Benefits" is in the example list. The posting has a lot of benefits. Could be one Benefits section with multiple lists. Let's decide: I'll create a "Benefits" section that includes all the benefit-related items. I'll use

            for each category, maybe with a

            Category

            before each list? But the rule says use
            • for any list, and

              for prose. It doesn't forbid using

              for a label. However, to keep semantic, maybe use

              ? But the rule only mentions

              . I think using

              is okay as prose. But the rule says "use

              • for any list of duties/requirements/benefits, and

                for prose." So a label could be a

                . But then the list follows. That's acceptable. Alternatively, we could make each benefit category a separate

                but that would be many sections. The rule says "never emit a heading followed by filler/placeholder text". Each category has real content. But "Prefer a few substantive sections over many thin ones." So I'll combine into one Benefits section with multiple lists. Similarly, "Who We Are" is company description. Could be "About the Company" but not in example list. The rule says "include a section ONLY when the posting has real, specific content for it". The posting has a paragraph about the company. Could include as "About the Company" or "Company Overview". But the example list doesn't include that. However, the rule says "e.g." so we can add other relevant headings. But the rule also says "Do NOT repeat the job title as a heading (the page already shows it)". The job title is not given in the input, but the page already shows it. So we shouldn't include a heading for the job title. The company description is not the job title. I think we can include a section "About the Company" or "Company Overview". But the rule says "Prefer a few substantive sections over many thin ones." The company description is one paragraph. Could be included as a

                under a heading. But is it necessary? The user wants to preserve ALL substantive information. So we should include it. I'll add a section "About the Company" with a

                . Now, let's structure: - Pay section: with the compensation range. - About the role: overview paragraph. - Responsibilities: list from "What You'll Do". - Requirements: list from "Your Background". - Benefits: combined benefits, schedule, growth, perks. - About the Company: company description. But note: "Why Join our Team" includes "Steady Hours, Flexible Life" which mentions scheduling and pay advance. The pay advance is a pay-related benefit. Could be in Benefits or Pay. Since Pay section already has compensation range, we could add the "Faster Pay" detail there. But the rule says Pay section only if posting states them. The posting states compensation range and also "Faster Pay – access up to 50% of your earned wages the next day". That's pay-related. Could include in Pay section. Similarly, "Steady Hours, Flexible Life" includes scheduling info. Could be a Schedule section. But the rule says never create Schedule section unless posting actually states them. It does state "Flexible scheduling with full-time or part-time opportunities". So we could create a Schedule section. But again, prefer few sections. I'll include scheduling info in Benefits section. Let's outline:

                Pay

                Compensation Range: $7.25 - $15.00 / Hour

                Faster Pay – access up to 50% of your earned wages the next day (exclusions apply)

                About the role

                Our Hosts know that first impressions are everything. As a Host, your warm, friendly, welcoming personality will shine while greeting and seating guests, managing the waitlist, and accommodating reservations. When we’re on a wait, you’ll quote accurate times, engage guests in casual conversation, and encourage them to explore our iconic menu or beautiful bakery case, answering questions along the way. With pride and a passion for hospitality, you’ll help ensure every guest feels welcomed and cared for from start to finish.

                Responsibilities

                • Warmly greet guests creating a positive first impression
                • Use a floor plan and follow a seating rotation to assign tables promoting guest satisfaction
                • Provide accurately quoted wait times while managing reservations to support smooth guest flow
                • Play an important role in front of house operations, supporting teamwork to enhance the overall guest experience
                • Answer phones with a sense of urgency, helping guests with general questions
                • Follow instructions with attention to detail and consistency
                • Demonstrate ownership of sidework and closing tasks
                • Multitask and work well under pressure while maintaining cleanliness and organization
                • Work with speed and efficiency in a fast paced, full-service restaurant

                Requirements

                • Previous restaurant, hospitality, customer service, or food service industry experience preferred
                • Strong communication and interpersonal skills with a focus on guest service
                • Dependable, dedicated, reliable, and punctual with a strong work ethic
                • Adaptable and patient, taking pride in providing excellent guest relations
                • Team player with a positive, patient attitude
                • Ability to lift up to 35 pounds, stand for extended periods, continuously bend, reach and twist
                • Must be at least 18 years old

                Benefits