Food Service Supervisor

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

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

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to parse the job posting. Key details: - Job Reference Number: 43072 (metadata) - Employment Type: Full-Time, Onsite - Segment: Education - Brand: Elior-School-Dining - Location: Cook County SD #130 - The Role at a glance: We are looking to add an experienced, motivated food service supervisor to our Elior School Dining team. As a food service supervisor, you will have the opportunity to directly oversee the production and service of meals. - What you'll be doing: Providing hands-on supervision and oversight for the preparation, cooking, and portioning of meals, following company recipes based on daily needs and contractual obligations. Ensuring all meals meet standards for quality. - What we're looking for: Must-haves: Experience supervising multiple employees. Strong communication, interpersonal, and organizational skills. Excellent attention to detail and service knowledge. Nice-to-haves: An advanced degree in culinary arts or a related field. Food Handler’s certification. - Where you'll be working: Cook County SD #130 - Compensation Range $18 / hour - Our Benefits: Medical (FT Employees) Dental Vision Voluntary UNUM offering for Accident, Critical Illness and Hospital Indemnity Discount Program Commuter Benefits (Parking and Transit) EAP 401k Sick Time Holiday Pay (9 paid holidays) Tuition Reimbursement (FT Employees) Paid Time Off - About Elior School Dining: Elior School Dining partners with public and charter schools across the country, serving millions of meals that meet NSLP guidelines while exceeding expectations. We create thoughtful, customized dining experiences rooted in fresh food, student voice, and collaboration – fueling school pride, smart choices, and brighter futures with every meal. - About Elior-North America: (EEO boilerplate) we need to remove EEO/equal-opportunity boilerplate. Also disclaimer: "This job description can be revised by management as needed." That's boilerplate? Possibly we can drop it as it's generic. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should drop the EEO paragraph and disclaimer. We need to produce sections: maybe "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". But we should only include sections that have real specific content. Let's map: - About the role: The Role at a glance paragraph: "We are looking to add an experienced, motivated food service supervisor to our Elior School Dining team. As a food service supervisor, you will have the opportunity to directly oversee the production and service of meals." That's substantive. Could be "About the role". Also maybe "Where you'll be working" could be part of About the role or separate? But we can include location in a short paragraph maybe not a separate heading. The instruction: Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. So location could be a short p. - Responsibilities: "What you'll be doing: Providing hands-on supervision and oversight for the preparation, cooking, and portioning of meals, following company recipes based on daily needs and contractual obligations. Ensuring all meals meet standards for quality." That's responsibilities. - Requirements: Must-haves and Nice-to-haves. Could be "Requirements" (must-haves) and "Qualifications" (nice-to-haves) or "Skills". We need to decide. We have Must-haves: Experience supervising multiple employees. Strong communication, interpersonal, and organizational skills. Excellent attention to detail and service knowledge. Nice-to-haves: An advanced degree in culinary arts or a related field. Food Handler’s certification. We could have a section "Requirements" for must-haves, and "Preferred Qualifications" for nice-to-haves, but we only have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could put must-haves under Requirements, nice-to-haves under Qualifications, and maybe Skills under Skills? But we could also combine. Better: Use Requirements for must-haves, Qualifications for nice-to-haves, and maybe Skills not needed. Or we could put all under Requirements and skip Qualifications. But we need to avoid thin sections. Let's see content: Must-haves: three bullet points. Nice-to-haves: two bullet points. That's enough for two sections. We could also have Skills section for communication etc. But we already have them in must-haves. Thus: -

  About the role

  with paragraph(s): The Role at a glance + maybe location? Could include location as separate short p. -

  Responsibilities

  with
  • for each duty? There's two sentences: "Providing hands-on supervision and oversight for the preparation, cooking, and portioning of meals, following company recipes based on daily needs and contractual obligations." and "Ensuring all meals meet standards for quality." Could be two list items. -

    Requirements

    with
    • for must-haves: Experience supervising multiple employees. Strong communication, interpersonal, and organizational skills. Excellent attention to detail and service knowledge. -

      Qualifications

      with
      • for nice-to-haves: An advanced degree in culinary arts or a related field. Food Handler’s certification. -

        Benefits

        with list: Medical (FT Employees), Dental, Vision, Voluntary UNUM offering for Accident, Critical Illness and Hospital Indemnity, Discount Program, Commuter Benefits (Parking and Transit), EAP, 401k, Sick Time, Holiday Pay (9 paid holidays), Tuition Reimbursement (FT Employees), Paid Time Off. -

        Pay

        with paragraph: Compensation Range $18 / hour. - Schedule: Not mentioned explicitly; we have Employment Type: Full-Time, Onsite. That implies schedule full-time but not specific hours. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Schedule not explicitly stated; we have Full-Time but not schedule details. Should we include Schedule? Probably not, as it's not specific. The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." Pay is stated ($18/hour). Benefits are stated. Schedule is not explicitly stated (just Full-Time). So we should not include Schedule section. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. We need to output only HTML fragment, no /, no markdown fences. We need to ensure we preserve all substantive information. Let's check we didn't miss any: The Role at a glance paragraph includes "We are looking to add an experienced, motivated food service supervisor to our Elior School Dining team. As a food service supervisor, you will have the opportunity to directly oversee the production and service of meals." That's covered. Location: "Cook County SD #130" appears twice (Location and Where you'll be working). We should include location somewhere. Could be a short p after About the role or within About the role. Let's add a p: "

        Location: Cook County SD #130

        " maybe. Employment Type: Full-Time, Onsite. Could be included in a short p as well. But we might not need to include if not required? The instruction: preserve ALL substantive information. So we should include Employment Type. Could be a short p: "

        Employment Type: Full-Time, Onsite

        " maybe under About the role or separate. Brand: Elior-School-Dining. Could be included. Segment: Education. Could be included. But we need to avoid duplication. The posting includes Segment: Education, Brand: Elior-School-Dining, Location: Cook County SD #130. These are metadata. We can fold them into a short p. Thus after About the role heading, we could have a p containing: "

        Segment: Education | Brand: Elior-School-Dining | Location: Cook County SD #130 | Employment Type: Full-Time, Onsite

        " That preserves all. Now About the role paragraph: we already have the Role at a glance. Could we combine? Maybe About the role heading includes the paragraph and then the metadata p. Now Responsibilities: we have two duties. Could be list. Requirements: Must-haves list. Qualifications: Nice-to-haves list. Benefits: list. Pay: paragraph. Check for any other substantive info: About Elior School Dining paragraph: "Elior School Dining partners with public and charter schools across the country, serving millions of meals that meet NSLP guidelines while exceeding expectations. We create thoughtful, customized dining experiences rooted in fresh food, student voice, and collaboration – fueling school pride, smart choices, and brighter futures with every meal." That's substantive. Should we include that? It's under "About Elior School Dining". That could be a section "About the company" but not in our allowed headings. However we could incorporate it under About the role? But that's about the role, not company. The instruction: we can only use headings from the list. But we could also not include a heading for that and just put it as a p under About the role? But that might be mixing. However we need to preserve ALL substantive information. So we need to include that paragraph somewhere. Since we don't have a heading like "About the company", we could add it as a p under About the role or maybe under a separate heading like "About Elior School Dining" but that's not in allowed list. The instruction says: use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples, not exclusive? It says "use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings for sections. It doesn't say we cannot use other headings, but it's implied to use those. Safer to stick to those headings. But we need to include the About Elior School Dining paragraph somewhere. Could we put it under About the role? That might be odd but still preserves info. However About the role is about the role, not company. But we could rename the heading to "About the role and company"? Not allowed. Maybe we can treat it as part of About the role? The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

        or drop it." It doesn't forbid adding