Dessert Finisher/Barista

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 - $19.00 / Hour (this is Pay information) - Overview: "As a Dessert Finisher/Barista..." (this is About the role) - Why Join our Team: This contains multiple subsections: Steady Hours, Flexible Life; Benefits That Have Your Back; Grow With Us; Perks, Recognition & Community; Join an award-winning company - What You'll Do: List of responsibilities - Your Background: Requirements/qualifications - Who We Are: Company description 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 (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 sections: 1. Pay: The posting has "Compensation Range $15.92 - $19.00 / Hour" - this is specific pay info, so include Pay section. 2. About the role: The "Overview" paragraph describes the role. Use

  About the role

  with

  . 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". The rules mention both "Requirements" and "Qualifications" as possible headings. Since it's a list of background/experience, I'll use "Requirements". Use
    • . 5. Benefits: The "Why Join our Team" section contains multiple benefits: steady hours, flexible scheduling, faster pay, discounts, paid vacation/sick time, medical/dental/vision, virtual care, GED/degree programs, perks, recognition, HELP Fund, community events, awards. This is substantive benefits content. Should I create a Benefits section? Yes, the posting has real specific content for benefits. Use

      Benefits

      with
      • for each benefit item. However, note that "Steady Hours, Flexible Life" includes scheduling info. The rules mention "Schedule" as a possible heading. But the posting doesn't have a separate schedule section; it's part of benefits. I'll include scheduling details under Benefits or maybe a separate Schedule section? The rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states "Flexible scheduling with full-time or part-time opportunities" and "Steady Hours". That's schedule info. But it's under "Why Join our Team". I could create a Schedule section, but the rules prefer few substantive sections over many thin ones. I'll include schedule details in Benefits or maybe a separate Schedule section? Let's see: The rules list "Schedule" as a possible heading. The posting has specific schedule info: "High-volume restaurant with consistent hours", "Flexible scheduling with full-time or part-time opportunities". That's substantive. I could create a Schedule section. But the user said "Prefer a few substantive sections over many thin ones." I'll combine schedule into Benefits? Actually, Benefits typically include things like health insurance, discounts, etc. Schedule is separate. However, the posting groups them under "Why Join our Team". I'll create a Benefits section that includes all the perks, and maybe a Schedule section for the scheduling details. But the scheduling details are only two bullet points. Might be thin. I'll include them in Benefits as part of the list. 6. Company description: "Who We Are" is about the company. Could be "About the company" but not in the listed headings. The rules list specific headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Who We Are" is not in that list. But it's substantive company info. The rules say "use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exhaustive. However, the instruction: "include a section ONLY when the posting has real, specific content for it". The posting has "Who We Are" with specific content. I could include it as a section with heading "About the company" or "Company overview". But the rules didn't list that. The user might expect only those headings. However, the instruction says "e.g." meaning for example. I think it's okay to include a section for company description. But to be safe, I'll include it as "About the company" or maybe "Who We Are". The rules say "use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings. But the instruction: "Output ONLY the HTML fragment". I'll include a section for "About the company" with the content. But note: The posting includes EEO statement at the end: "We are an equal opportunity employer...". That's boilerplate, should be removed. Also the scam warning: "To notify of a non-compliant job posting..." remove. Also, the "Why Join our Team" has multiple subsections. I'll break them into list items under Benefits. 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: list from "Why Join our Team" including all bullet points. - About the company: "Who We Are" paragraph. But the rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states pay, benefits, and schedule info. So all three are justified. However, schedule info is minimal. I'll include schedule details in Benefits or create a Schedule section. I'll create a Schedule section because the posting explicitly mentions "Steady Hours, Flexible Life" and "Flexible scheduling with full-time or part-time opportunities". That's specific. But the rules say "Prefer a few substantive sections over many thin ones." A Schedule section with two bullet points might be thin. I'll incorporate schedule into Benefits as a bullet point. Let's list all benefits from the posting: - Steady Hours, Flexible Life - High-volume restaurant with consistent hours - Flexible scheduling with full-time or part-time opportunities to fit your life - Faster Pay – access up to 50% of your earned wages the next day (exclusions apply) - 50% off shift meals and 25% discount when dining with friends and family - Benefits That Have Your Back - Paid vacation and sick time - Medical, Dental, Vision, and Prescription coverage options - Medical coverage starting as low as $12 per pay period - Virtual Care and no cost online mental health services - Grow With Us - World class training designed to support your personal and professional growth - Career advancement opportunities – over half of our managers are promoted from within - No cost GED or Associate Degree programs - Perks, Recognition & Community - Perks and discounts including cell phone, gym, movie, and theme park savings - Employee recognition and appreciation awards - HELP Fund (Hardship and Emergency Lifeline Program) for moments that matter - Opportunities to give back through community and charity events - Join an award-winning company - Fortune 100 Best Companies to Work For® (since 2014) - PEOPLE® Companies That Care (since 2021) - Great Place to Work® Certified All these are substantive benefits. I'll create a Benefits section with a

        containing all these as list items. Could group them with subheadings? But the rules say use
        • for any list. I can just make a flat list, but that might be long. Could use nested lists? The rules don't forbid nested lists. But to keep simple, I'll make a single list with each bullet point. However, some are sub-bullets. I'll include them as separate list items, maybe with the category as part of the text. For example: "Steady Hours, Flexible Life: High-volume restaurant with consistent hours". But that might be messy. Better to keep the structure: use
          with
          • for each benefit, and for sub-items, use nested
            . That's still semantic HTML. The rules didn't specify flat only. I'll do nested lists for clarity. But the instruction: "Use
            • for any list of duties/requirements/benefits". It doesn't forbid nested lists. I'll do nested. Now, the "Who We Are" section: I'll include as "About the company" with a

              . Now, remove boilerplate: EEO statement, scam warning, "The Cheesecake Factory offers reasonable accommodations..." etc. Also remove "#SoCheesecake" and the email for non-compliant posting. Now, write HTML. Let's start:

              Pay

              Compensation Range: $15.92 - $19.00 per hour

              About the role

              As a Dessert Finisher/Barista, you’re the friendly face behind our beautiful bakery case, putting the finishing touches on our famous cheesecakes and desserts. You’ll glaze our iconic strawberries, create perfect whipped cream dollops that “wow”, and craft delicious espresso beverages. As part of our high-volume, full-service restaurant team, you’ll support front-of-house operations, taking pride and ownership in delivering consistent quality that elevates the guest experience.

              Responsibilities

              • Plate and finish desserts with accuracy, attention to detail, and consistent presentation
              • Operate an espresso machine to prepare specialty coffee and espresso beverages
              • Accurately follow instructions while upholding food safety and food handling standards, with awareness of food allergies
              • Label, date, and rotate products following FIFO (First In, First Out) practices
              • Work with efficiency, speed, and a sense of urgency in a fast paced environment
              • Maintain organization, cleanliness, and sanitation of work areas
              • Complete station setup and breakdown, including stocking and closing tasks
              • Support teamwork through clear and effective communication
              • Multitask and work well under pressure with a positive attitude
              • Deliver exceptional service to ensure guest satisfaction

              Requirements

              • Previous restaurant, hospitality, barista, or food service industry experience preferred
              • Familiarity with beverage preparation and food handling, a plus
              • Knowledge of food safety and sanitation practices
              • Adaptable, patient, and able