Hiring Event- All Central IL Locations!

We need to output HTML fragment with sections for headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each section heading. 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 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 extract substantive content: The posting is about a hiring event with details: date, time, locations, positions with pay rates, benefits info, about company. We need sections: Possibly "About the role" (maybe description of event?), "Responsibilities"? Not given. "Requirements"? Not given. "Qualifications"? Not given. "Skills"? Not given. "Benefits" – we have benefits info. "Pay" – we have pay rates per position. "Schedule" – we have event date/time and maybe work schedule? Not given. The posting includes event schedule (date/time) and location details. Could treat that as "Schedule" (event schedule). But the instruction says include a section only when posting has real, specific content for it. We have schedule: Date: Wednesday, October 7, 2026; Time: 10am to 2pm; Locations list. That's specific. So we can have a Schedule section. We also have Pay: specific rates per position. So Pay section. Benefits: we have benefits info. About the role: maybe a description of the hiring event and positions? Could be "About the role" describing what they're hiring for. We have "What positions are we hiring for?" with list of positions and pay. That could be considered responsibilities? Actually it's positions. Could be "About the role" summarizing the event and positions. Or we could have a section "Positions" but not in allowed headings. Allowed headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these. We have info about positions and pay; could go under Pay (list of positions with pay). Could also have About the role describing the event and company. Could have Responsibilities? Not given. Could have Requirements? Not given. Could have Qualifications? Not given. Could have Skills? Not given. Thus we likely will have sections: About the role, Pay, Benefits, Schedule. Possibly also "Responsibilities" if we can infer from positions? But better not to invent. So only include sections with real content. We need to preserve all substantive information: event date/time/locations, positions with pay, benefits, about company description. We must not repeat job title as heading. The job title is "Hiring Event". Not to be used as heading. We must not put Job ID/requisition numbers as headings; we can fold minor metadata into short

  or drop it. The requisition ID: 265958. Could be placed in a

  maybe at bottom. We must remove boilerplate: EEO, Veteran friendly, etc. Remove duplicated lines, application instructions (like "Walk-ins Welcome, but applying online prior to attending will ensure the best experience- use the apply now button with this posting.") That's application instruction; remove. Also remove "Join the team at Heartland Coca-Cola Bottling Company! When and where? Job Title: Hiring Event Hiring Event Peoria Join the team at Heartland Coca-Cola Bottling Company! When and where? Join Us on October 7, 2026! Looking for your next career opportunity? Heartland Coca-Cola is hosting a hiring event at our Peoria facility and we're looking for talented individuals to join our team." This is duplicated; we need to keep substantive info: event date, time, locations. We need to preserve all substantive information: So we need to keep the event date, time, locations list, positions with pay, benefits, about company description. We need to format as HTML fragment. Let's craft:

  About the role

  Heartland Coca-Cola Bottling Company is hosting a hiring event to fill various positions across its Central Illinois distribution centers. The event will take place on Wednesday, October 7, 2026 from 10am to 2pm at multiple locations.

  Then maybe a

  for locations list? Could be a

  • for each location. But the instruction: Use
    • for any list of duties/requirements/benefits, and

      for prose. Locations list is not duties/requirements/benefits; it's just info. Could be prose or list? Probably better as

      • for list of locations? Not explicitly required but could be okay. However instruction says use
        • for any list of duties/requirements/benefits. It doesn't forbid using lists for other things, but to be safe we can use

          with commas. But we need to preserve all substantive information; we can include a

          • for locations as it's a list; not prohibited. I'd say it's okay. Similarly for positions and pay: we can make a
            • list. Benefits: we can make a
              • . Schedule: we already have date/time; maybe we can also include location list under Schedule? Actually schedule section could contain date, time, locations. Let's decide: We'll have Schedule section with date/time and locations. Thus:

                Schedule

                Date: Wednesday, October 7, 2026

                Time: 10am to 2pm

                • Charleston, IL – 1321 Loxa Road, Charleston, Illinois 61920 – (217) 348-1001
                • Peoria, IL – 5001 South Becker Drive, Bartonville, Illinois 61607 – (309) 697-8600
                • Champaign, IL – 2809 N. Lincoln Avenue, Urbana, Illinois 61801 – (217) 367-1761
                • Quincy, IL – 2620 Ellington Road, Quincy, Illinois 62305 – (217) 223-3336
                • Springfield, IL – 3495 East Sangamon Avenue, Springfield, Illinois 62707 – (217) 544-4891
                Then Pay section:

                Pay

                • Driver Merchandiser (Class A CDL) – $25.00 (Quincy, Peoria, Charleston, Champaign)
                • Driver Merchandiser (Class A CDL) – $28.25 (Springfield)
                • Driver Non-CDL – $23.25 (Quincy, Springfield)
                • Full time Merchandiser – $19.00 (Peoria, Springfield, Charleston, Champaign)
                • Part time Merchandiser – $19.00 (Champaign)
                • Warehouse Order Builder (Springfield) – $25.03
                Benefits section:

                Benefits

                • Medical, dental, and vision insurance
                • Life insurance
                • 401(k)
                • Paid time off
                • Wellness programs
                • Tuition reimbursement
                • Part‑time employees eligible for paid time off, 401(k), and tuition reimbursement
                About the role section: we need to include description of event and company. We have "About Heartland Coca-Cola" paragraph: "Heartland Coca-Cola Bottling Company produces, sells, and distributes the highest quality and best tasting Coca-Cola and Monster Beverages across the states of Kansas, Missouri, and Illinois. Our brand offerings provide multiple beverage options in non-alcoholic categories including sparkling soft drinks, water, ingredient enhanced, isotonics, tea, energy, juice, coffee and nutrition. We value our people, customers and community which drives our passion to work and win together as a team." We can put that in About the role. Also we might include a brief intro about the hiring event: "Join us at our hiring event to learn about opportunities and our paid Class A CDL training program." We have that line: "All Central IL Locations-Come in to learn about our paid Class A CDL training program and show interest in future class dates!" That's substantive. Thus About the role section can combine. Let's craft:

                About the role

                Heartland Coca-Cola Bottling Company is hosting a hiring event to attract talent for various positions across its Central Illinois distribution centers. Attendees can learn about the paid Class A CDL training program and express interest in future class dates.

                Heartland Coca-Cola Bottling Company produces, sells, and distributes the highest quality and best tasting Coca-Cola and Monster Beverages across the states of Kansas, Missouri, and Illinois. Our brand offerings provide multiple beverage options in non-alcoholic categories including sparkling soft drinks, water, ingredient enhanced, isotonics, tea, energy, juice, coffee and nutrition. We value our people, customers and community which drives our passion to work and win together as a team.

                We should not include EEO boilerplate etc. We might also include a short note about requisition ID as minor metadata: maybe a

                at end:

                Requisition ID: 265958

                . But we should not put it as heading; we can fold into a short

                . That's okay. Now ensure we didn't include any duplicated lines, no navigation, no EEO, no scam warning, no application instructions. Check for any leftover boilerplate: The original had "Heartland Coca-Cola is an Equal Opportunity Employer (EOE), and all qualified applicants will receive consideration for employment without regard to race, color, religion, sex, sexual orientation, gender identity, national origin, and any other class protected by law. Veteran friendly." We removed that. Also removed "Pre-employment background check is required." That's substantive? It's a requirement. Could be considered a requirement. Should we keep? It's a requirement for employment. The instruction says preserve ALL substantive information. So we should keep that. It's a requirement. We could put it under Requirements section. But we said we won't create Requirements unless we have real content. We have this requirement: pre-employment background check is required. That's specific. So we should include a Requirements section. Similarly, we might have "All Central IL Locations-Come in to learn about our paid Class A CDL training program and show interest in future class dates!" That's more about the event, could be in About the role. We also have "Walk-ins Welcome, but applying online prior to attending will ensure the best experience- use the apply now button with this posting." That's application instruction; remove. Thus we need to add a Requirements section with the background check