Busser

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: - About the role / Who We're Inviting To The Table (description) - Responsibilities (RECIPE FOR SUCCESS) - Requirements/Qualifications (THE PERFECT PAIRING) - Benefits (What You Can Look Forward To) - Pay/Compensation (Compensation section) - Schedule (mentioned in benefits: AM/PM and Mid-day shifts, part time to 40 hours) Rules: - Use

for section headings - Use

• for lists - Use

  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 (EEO, equal opportunity, scam warnings, application instructions) - Include section ONLY when real specific content exists - Never emit heading followed by filler/placeholder text - Never create Pay/Schedule/Benefits sections unless posting actually states them - Output ONLY HTML fragment, no html/body, no markdown code fences Let me parse the content: 1. Opening paragraph: "We believe that a life of purpose..." - this is about the company/role, could be "About the role" or "About us". But the rule says don't repeat job title as heading. The job title isn't explicitly stated but it's a Busser role. The heading "Who We're Inviting To The Table" seems like the role description. I'll use that as a heading or "About the role". 2. Interview invitation: "WE INVITE YOU TO COME IN FOR AN INTERVIEW MONDAY- THURSDAY BETWEEN 3-5PM..." - this is application instruction, should be removed per rules. 3. "Who We're Inviting To The Table" - description of the role. This is substantive. 4. "RECIPE FOR SUCCESS" - list of responsibilities. This is a list. 5. "THE PERFECT PAIRING" - requirements/qualifications. List. 6. "What You Can Look Forward To" - benefits. List. 7. "Compensation: Starting at state tipped minimum wage/hour + Tips* Location/state & shift dependent..." - pay information. 8. EEO statement - boilerplate, remove. 9. "If you're excited about working for us..." - application instruction, remove. Now, schedule: The posting mentions "AM/PM and Mid-day shifts available" and "Part time to 40 hours available per person" and "Flexible availability to work nights, weekends, and holidays". That's schedule info. Should I create a Schedule section? The rule says include section ONLY when posting has real specific content for it. It does have schedule info. But also the benefits section includes shift info. Could combine or separate. The rule says prefer few substantive sections over many thin ones. I'll include a Schedule section if there's enough. Pay: The compensation section is specific: "Starting at state tipped minimum wage/hour + Tips* Location/state & shift dependent - Please refer to minimum and maximum hiring range for estimate of weekly earnings." That's real content, not placeholder. So include Pay section. Benefits: The "What You Can Look Forward To" has many specific benefits. Include Benefits section. Now, headings: Use

  for section headings. The suggested headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I'll map: - "Who We're Inviting To The Table" -> About the role (or keep as is? The rule says use

  for section headings (e.g. About the role, Responsibilities...). It doesn't forbid using the original heading text, but suggests those as examples. I think using the original heading text is fine as long as it's semantic. But "Who We're Inviting To The Table" is a bit creative. Could use "About the role". I'll use "About the role" for clarity. - "RECIPE FOR SUCCESS" -> Responsibilities - "THE PERFECT PAIRING" -> Requirements (or Qualifications). The list includes experience and availability. Could be "Requirements" or "Qualifications". I'll use "Requirements". - "What You Can Look Forward To" -> Benefits - "Compensation" -> Pay - Schedule info: from benefits and requirements. I'll create a Schedule section with the shift details. Now, I need to output only HTML fragment. No markdown fences. Let me construct:

  About the role

  Our Bussers keep the restaurant flowing by clearing tables, supporting servers with food and drink delivery, and maintaining a clean, welcoming space. They're ready to lift, move, and jump in wherever needed—all while delivering warm, genuine hospitality that brightens our guests’ day!

  Responsibilities

  • Keep the dining room clean by promptly clearing and resetting tables.
  • Assist servers with water/tea refills and clearing tableware.
  • Monitor and clean floors, bar, and restrooms as needed.
  • Stock clean dishes from the dish station.
  • Clean spills quickly and discreetly.
  • Help deliver food, especially during busy times.
  • Thank guests and ask about their experience.
  • Respond sincerely to guest requests and communicate with the team.
  • Stay flexible to support smooth restaurant operations.

  Requirements

  • Committed to delivering exceptional service and warm hospitality.
  • Experience in a fast-paced, fun restaurant environment is a plus.
  • Flexible availability to work nights, weekends, and holidays.

  Benefits

  • Successful and professional work environment with opportunities for growth and a development program for career advancement.
  • AM/PM and mid-day shifts available.
  • Part-time to 40 hours available per person.
  • Part-time team members offered access to affordable, quality health care through Hooray Health and telehealth options.
  • Pet insurance.
  • Access to expert guidance through EAP/SupportLinc for everyday issues.
  • Restaurant dining discount.
  • Paid volunteer time to support community and favorite charities.
  • Eligible to give to and receive from the True Giving fund that supports life-changing events.

  Pay

  Starting at state tipped minimum wage per hour plus tips. Location/state and shift dependent; refer to minimum and maximum hiring range for estimate of weekly earnings.

  Schedule

  • AM/PM and mid-day shifts available.
  • Part-time to 40 hours per week.
  • Flexible availability required for nights, weekends, and holidays.
  Wait, the schedule info is partially duplicated in benefits. The benefits list includes "AM/PM and Mid-day shifts available" and "Part time to 40 hours available per person". The requirements include "Flexible availability to work nights, weekends, and holidays". I'll include a Schedule section with those details. But note: the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state them. However, the schedule info is scattered. I'll include a Schedule section with the specific details. But the benefits section already includes shift info. Should I duplicate? The rule says preserve ALL substantive information. It's okay to have some overlap but better to organize. I'll keep benefits as listed, and schedule as separate with the schedule-specific details. However, the benefits list includes "AM/PM and Mid-day shifts available" and "Part time to 40 hours available per person". That's schedule info. I could move those to Schedule and keep benefits as other perks. But the original grouping is "What You Can Look Forward To" includes both benefits and schedule. The rule says use sections as appropriate. I think it's fine to have a Benefits section with all the perks, and a Schedule section with the shift details. But the shift details are also perks. I'll keep them in Benefits as they are listed there, and also create a Schedule section? That would duplicate. Better to not duplicate. I'll include schedule details in Benefits and not create a separate Schedule section? But the rule says include section ONLY when posting has real specific content for it. The posting has schedule info, but it's embedded in benefits. The user might expect a Schedule section. The example headings include Schedule. I'll create a Schedule section with the schedule info, and in Benefits I'll keep the other benefits but maybe omit the schedule lines? However, the rule says preserve ALL substantive information. If I move them, I'm not losing info. But the original structure had them under "What You Can Look Forward To". I think it's acceptable to have a Benefits section that includes all the perks, and a Schedule section that summarizes the schedule. But that duplicates. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid duplication, but it's not ideal. I'll keep the Benefits section as the full list from "What You Can Look Forward To", and create a Schedule section that references the same info? That would duplicate. Better to not create a Schedule section if the info is already in Benefits. But the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states schedule info, but it's under benefits. I think it's okay to have a Schedule section with the schedule details, and in Benefits I'll keep the other benefits but maybe not repeat the schedule lines. However, the original list includes them as bullet points. I could keep them in Benefits and not create a separate Schedule section. But the user might expect a Schedule section because it's a common heading. The instruction says "Prefer a few substantive sections over many thin ones." So maybe combine. I'll keep Benefits as is, and not create a separate Schedule section. But the Pay section is separate. The Schedule info is not a separate heading in the original. I'll not create a Schedule section. However, the example headings include Schedule. The rule says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It's a list of examples, not required. I'll only include sections that have real content. The schedule content is real but it's part of benefits. I'll include a Schedule section with the schedule details extracted from benefits and requirements. That way it's a dedicated section. I'll remove the schedule bullets from Benefits? But the rule says preserve ALL substantive information. If I remove from Benefits, I'm removing from that section. But I can keep them in both? That's duplication. I think it's better to have a Schedule section and keep Benefits as the other perks. I'll edit the Benefits list to exclude the schedule-related bullets, and put them in Schedule. But the original posting grouped them together. The user might want the original grouping. However, the instruction says to reformat into clean, well-structured semantic HTML. It's okay to reorganize for clarity. I'll do: Benefits: all the perks except shift/hours. Schedule: shift details and hours. But the original "What You Can Look Forward To" includes both. I'll keep the heading "Benefits" and include all, and also add a Schedule section? That would duplicate. I'll decide to not create a Schedule section, because the schedule info is already in Benefits and Requirements. The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states schedule info, but not under a separate "Schedule" heading. It's under "What You Can Look Forward To" and "THE PERFECT