Student Worker

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate. We need to parse the posting. Job Reference Number: 42769 (drop) Employment Type: Part-Time, Onsite (maybe we can include in a short p? The instruction: "fold minor metadata into a short

or drop it." So we could include a short p with employment type. Segment: Education Brand: Elior-Collegiate-Dining Location: Wilson Workforce & Rehab Center (maybe location is part of metadata; could be short p.) The Role at a glance: We are looking to add an enthusiastic, motivated student worker to our [Segment] team in [City]. As a student worker, you will have the opportunity to assist with the production and service of all food for the dining area. What you'll be doing: Preparing food items for the next meal period. Keeping food lines stocked and clean throughout service. Assisting with meal service as assigned. What we're looking for: Must-haves: Strong customer service and organizational skills. Nice-to-haves: At least one years’ experience in foodservice. Where you'll be working: TBD by recruiter (this is placeholder; we should not create a section for it; maybe drop.) Compensation Range (no actual range given; just heading "Compensation Range" but no numbers; we should not create Pay section unless posting actually states them. It says "Compensation Range" but no actual range; it's placeholder. So we should not include Pay section. Our Benefits: then list 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 We need to include Benefits section only if posting actually states them. It does list benefits. So we create

Benefits

with

• each benefit. Also we might include About Elior Collegiate and About Elior-North America as maybe "About the role"? Actually "About Elior Collegiate:" and "About Elior-North America:" are company description; could be placed under a section like "About the company" but not in the prescribed headings list. The headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put company description under About the role? Probably not. The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples; we could also use other headings if appropriate? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It seems they expect us to use those headings when applicable. But we could also have other headings if needed? Safer to stick to those. The company description could go under About the role? Not exactly. Maybe we can omit it as it's not required? But we must preserve ALL substantive information; do not invent or summarize away detail. So we need to include the company description somewhere. Could we put it under a

  without a heading? Yes, we can have prose

  without heading. The instruction: Use

  for section headings,

  • for any list,

    for prose. So we can have a

    for company description. Thus structure:

    Employment Type: Part-Time, Onsite. Location: Wilson Workforce & Rehab Center.

    maybe combine. Then

    About the role

    with prose from "The Role at a glance:" paragraph. Then

    Responsibilities

    with
    • items from "What you'll be doing:". Then

      Requirements

      with
      • for Must-haves and Nice-to-haves? Could separate Must-haves and Nice-to-haves as list items. Could also have two subheadings but not needed. We'll just list each as
      • . Then

        Benefits

        with
        • each benefit. We should not include Pay or Schedule sections because no specifics. We should not include "Where you'll be working: TBD by recruiter" as it's placeholder; drop. We should not include Job Reference Number etc. We need to ensure we preserve all substantive information: The role description, responsibilities, must-haves, nice-to-haves, benefits list, company description paragraphs. Let's extract company description paragraphs: About Elior Collegiate: Elior Collegiate Dining is rewriting the rules of campus dining, serving up bold flavors, fresh ideas, and high-impact experiences that fuel student life. We partner with forward-thinking colleges and universities to create vibrant, customized dining programs that spark connection, celebrate culture, and make food a defining part of the college journey. About Elior-North America: Elior North America is an equal opportunity employer. Qualified applicants will receive consideration for employment without regard to race, color, religion, sex, national origin, sexual orientation, gender identity, disability or protected veteran status. We are committed to diversity and encourage applications from people of all backgrounds and abilities. We take pride in supporting the development of our employees and their skills at all levels and in fostering an environment of growth. At Elior North America, we are committed to offering growth and advancement opportunities for all of our employees. The valuable skills and experience you’ve gained with Elior will propel you further in your career, whether with our corporate office or one of our brand segments. Disclaimer: This job description can be revised by management as needed. (This is boilerplate? It's a disclaimer; maybe we should drop as it's generic legal? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This disclaimer is legal boilerplate; we should drop it. Thus we keep the two About paragraphs. Now produce HTML. We need to output only HTML fragment, no /, no markdown fences. Let's craft:

          Employment Type: Part-Time, Onsite. Location: Wilson Workforce & Rehab Center.

          About the role

          We are looking to add an enthusiastic, motivated student worker to our Education team in Wilson Workforce & Rehab Center. As a student worker, you will have the opportunity to assist with the production and service of all food for the dining area.

          Note: The original had "[Segment] team in [City]". We have actual values: Segment: Education, Location: Wilson Workforce & Rehab Center (maybe city). We'll fill.

          Responsibilities

          • Preparing food items for the next meal period.
          • Keeping food lines stocked and clean throughout service.
          • Assisting with meal service as assigned.

          Requirements

          • Strong customer service and organizational skills.
          • At least one year’s experience in foodservice (nice-to-have).
          But we need to differentiate must-haves vs nice-to-haves? Could keep as separate list items with note. Or we could have two subheadings but not required. We'll keep as list items with indication. Alternatively we could have

          Must-haves

          and

          Nice-to-haves

          but those aren't in the prescribed headings; but we could still use

          for any heading? The instruction says use

          for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe we stick to those. So we combine. We could phrase: Must-haves: Strong customer service and organizational skills. Nice-to-haves: At least one year’s experience in foodservice. We can put as two

          items with that text. Now Benefits:

          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

          Now company description paragraphs:

          About Elior Collegiate

          maybe not allowed but we could use

          without heading. But we need to preserve the info. Could we put under About the role? Not ideal. Perhaps we can add a

          About the company

          though not in list but maybe acceptable. The instruction says "use

          for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not an exhaustive list. So we can use other headings as needed, as long as we use

          . So we can add

          About Elior Collegiate

          and

          About Elior-North America

          . That seems fine. Thus:

          About Elior Collegiate

          Elior Collegiate Dining is rewriting the rules of campus dining, serving up bold flavors, fresh ideas, and high-impact experiences that fuel student life. We partner with forward-thinking colleges and universities to create vibrant, customized dining programs that spark connection, celebrate culture, and make food a defining part of the college journey.

          About Elior-North America

          Elior North America is an equal opportunity employer. Qualified applicants will receive consideration for employment without regard to race, color, religion, sex, national origin, sexual orientation, gender identity, disability or protected veteran status. We are committed to diversity and encourage applications from people of all backgrounds and abilities. We take pride in supporting the development of our employees and their skills at all levels and in fostering an environment of growth. At Elior North America, we are committed to offering growth and advancement opportunities for all of our employees. The valuable skills and experience you’ve gained with Elior will propel you further in your career, whether with our corporate office or one of our brand segments.

          We should exclude the disclaimer. Now ensure we didn't include any boilerplate like "EEO". The About Elior-North America paragraph includes EEO statement; that is part of company description, not boilerplate to remove? The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. However that EEO statement is part of the "About Elior-North America" section; it's describing the company's policy. Might be considered boilerplate but it's substantive? It's a standard EEO statement; but it's part of the "About" section. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. Likely they want to remove the standalone EEO statement that often appears at end. But the About Elior-North America paragraph includes that statement as part of description; maybe we should keep it as it's part of the "About". However to be safe, we could keep it; it's not a separate boilerplate