Food Runner

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the posting. Content: - Title: Wachusett Brewing Company | Westminster, Massachusetts Part-Time | Hourly, Non-Exempt Reports to: Kitchen Manager - Intro: "Join the Wachusett Team! Looking for a fast-paced restaurant job..." etc. - "What You'll Do" list: bullet points. - "What We're Looking For": bullet points. - "Physical and Work Requirements": bullet points. - "Why Wachusett?": paragraph. - There's no explicit Pay, Benefits, Schedule details. No mention of pay rate, benefits, schedule specifics (only flexible schedule mention). The schedule is mentioned: "Availability to work a flexible schedule during restaurant operating hours, including evenings, weekends, and holidays as needed." That's schedule info. Should we create a Schedule section? The rule: include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The schedule content is specific: flexible schedule, evenings, weekends, holidays. So we can include a Schedule section with that content. Benefits: none mentioned. Pay: none mentioned. So we omit Benefits and Pay. About the role: we have introductory paragraph describing role. Could be About the role. Responsibilities: "What You'll Do" list. Requirements: maybe "What We're Looking For" includes requirements (age, attitude, etc). Could be Requirements. Qualifications: maybe overlapping; but we can combine. The instruction: prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements (including what we're looking for and physical requirements), and Schedule. Possibly also Qualifications? But we can treat Requirements as covering both qualifications and physical requirements. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not repeat job title as heading. Do not put Job ID etc. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all bullet points exactly as given (or close). Must not omit any. Let's extract bullet points. From "What You'll Do": - Food Running and Guest Service - Represent Wachusett Brewing Company with pride and professionalism. - Welcome guests with enthusiasm and help create a friendly, comfortable environment. - Deliver food to the correct tables quickly, accurately, and professionally. - Help ensure every order leaving the kitchen meets our quality standards. - Learn our food menu and beer selection so you can confidently answer general guest questions. - Communicate with kitchen and front-of-house team members to keep service running smoothly. - Provide exceptional customer service with a smile. That's a list with a heading "Food Running and Guest Service" then sub-bullets. We need to represent as

  • . Could treat each bullet as
  • . The heading "Food Running and Guest Service" could be a
  • with bold? But we just need to preserve content. Could make it a
  • with strong? But we cannot add extra tags not specified? We can use
  • and inside we can have the text. The sub-bullets could be nested
    . However spec says use
    • for any list of duties/requirements/benefits. It doesn't forbid nesting. We'll do nested lists. Similarly "What We're Looking For": - At least 16 years old. - No previous restaurant experience required-we are happy to train the right person. - Positive, energetic, and team-oriented attitude. - Dependable, accountable, and ready to work. - Strong communication and people skills. - Ability to remain organized and move quickly in a high-volume restaurant environment. - Commitment to excellent guest service, food quality, cleanliness, and safety. - Availability to work a flexible schedule during restaurant operating hours, including evenings, weekends, and holidays as needed. Note: The last bullet about schedule also appears; but we also have a Schedule section. Might duplicate. We could keep schedule bullet in Requirements or What We're Looking For, and also have a Schedule section? That would duplicate. Better to not duplicate; we can move schedule info to Schedule section and remove from Requirements. But we must preserve all substantive information; we can't remove it. We could keep it in both places? That would be duplication, but not prohibited? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is not inventing or summarizing away; it's preserving. However duplication may be considered unnecessary but not prohibited. However they said "Prefer a few substantive sections over many thin ones." Duplication could be considered thin. Better to avoid duplication by placing schedule info only in Schedule section and not in Requirements. But then we would lose that bullet from Requirements. However the bullet is part of "What We're Looking For". If we remove it, we lose that info. But we could keep it in Requirements and also have Schedule section that just repeats? Might be okay but could be considered duplication. I'd rather keep it in Requirements and not create a separate Schedule section, because schedule info is already there. However the rule says include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The schedule content is specific, but we already have it in Requirements. If we create a Schedule section, we would need to put that content there; we could remove it from Requirements to avoid duplication. But then we would lose the bullet from Requirements? Actually we could keep it in both places but that's duplication. I'd rather not create a Schedule section and just keep schedule bullet under Requirements (or What We're Looking For). The instruction about Schedule section: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state schedule info (availability to work flexible schedule...). So we could create a Schedule section with that content. But then we need to decide where to put it. If we create Schedule section, we should still preserve the info elsewhere? The posting states it; we can place it in Schedule section and not duplicate elsewhere. That would mean we need to remove it from Requirements. But the requirement bullet is part of "What We're Looking For". If we remove it, we lose that piece from that section. However we could keep the bullet in Requirements but also have Schedule section with same content; duplication but still preserving all info. The instruction does not forbid duplication, but says prefer few substantive sections over many thin ones. Duplication creates extra section (thin) maybe not ideal. However the schedule bullet is just one line; making a separate Schedule section for one line could be considered thin. Better to keep it under Requirements and not create a Schedule section. But the rule says we can create Schedule section only if posting actually states them. It does not say we must create it if they state it; it's optional? The phrase: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Means we should not create those sections if the posting does NOT state them. If they do state them, we may create them, but not required. So we can choose not to create Schedule section. That seems fine. Thus sections: About the role (intro paragraph), Responsibilities (What You'll Do), Requirements (What We're Looking For + Physical and Work Requirements). Could also have Qualifications but we can merge. We need to preserve all substantive information: intro paragraphs, bullet points, physical requirements paragraph, Why Wachusett? paragraph. We need to format. Let's extract intro paragraph before "What You'll Do": "Join the Wachusett Team! Looking for a fast-paced restaurant job with a great team, plenty of energy, and no previous experience required? Wachusett Brewing Company, part of Barrel One Collective, is looking for an enthusiastic and dependable Food Runner & Restaurant Support Team Member. This is a great opportunity for someone who enjoys staying active, helping others, and creating a memorable experience for every guest. You will help keep service moving by delivering food, supporting the kitchen, maintaining clean dishes and work areas, and jumping in wherever the team needs you. If you bring a positive attitude and a strong work ethic, we will teach you the rest!" That's prose; we can put in

      . Then "What You'll Do" heading: we will use

      Responsibilities

      then list. Then "What We're Looking For" heading: we will use

      Requirements

      then list. Then "Physical and Work Requirements" heading: we could also include under Requirements as separate list or continue same list. Since it's also requirements, we can just continue same
      after the previous list? But better to separate maybe as another

      Physical Requirements

      but that would be thin. We can combine into Requirements section with two lists: one for "What We're Looking For" and another for "Physical and Work Requirements". That's still one section but multiple lists. Then "Why Wachusett?" paragraph: we can use

      About the role

      ? Actually we already used About the role for intro. Why Wachusett? is more about company culture; could be another section like "About the company" but not in allowed headings list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put Why Wachusett? under About the role? But About the role already used for intro. Could we add another paragraph under About the role? That would be okay: About the role section can contain multiple paragraphs. So we can put intro and Why Wachusett? both under About the role. However the intro already describes role; Why Wachusett? describes company culture; still fits About the role. So we can have one About the role section with two paragraphs. Thus sections: About the role (intro + Why Wachusett?), Responsibilities, Requirements (including What We're Looking For and Physical and Work Requirements). No Qualifications, Skills, Benefits, Pay, Schedule. Now we need to ensure we don't include boilerplate like EEO etc. Remove those lines at end. Now craft HTML. We'll need to escape any special characters? Not needed. Let's write:

      About the role

      Join the Wachusett Team! Looking for a fast-paced restaurant job with a great team, plenty of energy, and no previous experience required? Wachusett Brewing Company, part of Barrel One Collective, is looking for an enthusiastic and dependable Food Runner & Restaurant Support Team Member. This is a great opportunity for someone who enjoys staying active, helping others, and creating a memorable experience for every guest. You will help keep service moving by delivering food, supporting the kitchen, maintaining clean dishes and work areas, and jumping in wherever the team needs you. If you bring a positive attitude and a strong work ethic, we will teach you the rest!

      At Wachusett Brewing Company, hospitality is a team effort. You will work alongside people who move quickly, support one another, take pride in their work, and know how to have fun while getting the job done. Whether this is your first restaurant job or your next opportunity, you will gain valuable experience in customer service, teamwork, food service, and restaurant operations.

      Responsibilities

      • Food Running and Guest Service
        • Represent Wachusett Brewing Company with pride and professionalism.
        • Welcome guests with enthusiasm and help create a friendly, comfortable environment.
        • Deliver food to the correct tables quickly, accurately, and professionally.
        • Help ensure every order leaving the kitchen meets our quality standards.
        • Learn our food menu and beer selection so you can confidently answer general guest questions.
        • Communicate with kitchen and front-of-house team members to keep service running smoothly.
        • Provide exceptional customer service with