General Labor

We need to output HTML fragment with sections: About Us? Actually headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only if posting has real specific content. We have "About Us" content: description of company. That could be "About the role"? Actually "About Us" is about company, not role. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to these headings. The posting includes "About Us" (company description) maybe fits "About the role"? Not exactly but we can treat as "About the role" maybe not. However we could create a section "About the role" with description of role? There's no explicit "About the role" but we have "Why You’ll Love Working Here" which is benefits. Also "Requirements For Production Operators" is requirements. Also "Production Operators Duties May Include" is responsibilities. Also "Competitive salaryHealth and wellness benefits..." is benefits. Also there is mention of drug test etc. No explicit pay or schedule specifics besides "Ability to work any shift, weekends, or holidays (our plants operate 24/7)." That indicates schedule: any shift, weekends, holidays. So we can include Schedule section with that detail. Pay: "Competitive salary" is mentioned but it's vague; we should not include Pay section if it's just "competitive salary" with no specifics? The rule: 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. "Competitive salary" is vague but it's a statement; is that considered filler? It's not a specific number. Might be considered placeholder. Safer to omit Pay section. Benefits: we have list: Health and wellness benefits with medical coverage through Blue Cross Blue Shield, including mental health benefits; Disability insurance; Paid time off; Employer-matched 401(k) retirement savings plan; Personal and professional growth opportunities; Employee appreciation events and recognition awards; Employee wellness initiatives; Employee feedback and suggestion forums. That's specific enough. So Benefits section. Schedule: we have ability to work any shift, weekends, or holidays (plants operate 24/7). That's specific. So Schedule section. Responsibilities: list of duties. Requirements: list. Qualifications: maybe combine with requirements? The posting includes "High school diploma or GED required" etc. That's qualifications. Could put under Requirements or Qualifications. We need to decide: we have both Requirements and Qualifications sections possible. The posting includes "Requirements For Production Operators" then list includes ability to work any shift, reliable attendance, drug test, high school diploma, follow GMP, etc. Also "Prior experience in manufacturing or dairy is preferred" could be qualification. We could split: Requirements: mandatory items; Qualifications: preferred experience. But we need to avoid thin sections. Might combine into Requirements only. However we have separate headings allowed; we can include both if content sufficient. Skills: maybe not explicitly listed; we have ability to read SOPs, etc. Could be skills. But we might not have a dedicated skills section; we could omit. About the role: we have "About Us" company description. Could treat as About the role? Might be okay. Or we could omit About the role if not specific to role. The instruction: use heading for section headings (e.g. About the role...). It doesn't require we must include About the role; we include only if posting has real specific content for it. The posting has "About Us" which is about company, not role. Might be considered not specific to role, but we could still include as About the role? Might be stretching. Safer to omit About the role section. Thus we will output sections: Responsibilities, Requirements, Benefits, Schedule. Possibly also Qualifications if we split. Let's extract content precisely. About Us paragraph: "The Michigan Milk Producers Association is a dairy farmer owned cooperative and dairy processor. Founded in 1916, the MMPA serves dairy farmers in Michigan, Indiana, Ohio and Wisconsin. MMPA maintains a strong presence within the dairy industry with strategic business relationships through a variety of channels like processing shelf-stable, value added dairy products. MMPA has five member owned processing plants in Michigan, Indiana and Ohio, including Superior Dairy and the Middlebury Cheese Company. Products made at MMPA’s plants include fluid milk, cheese, ultrafiltered milk, cottage cheese, ice cream, butter, nonfat dry milk, cream and condensed skim milk." Why You’ll Love Working Here: list of benefits. Requirements For Production Operators: list. Production Operators Duties May Include: list. Also note: "These duties will change as soon as availability for a skilled position opens" etc. That's part of responsibilities. Also note: "To perform this job successfully, an individual must be able to perform each responsibility satisfactorily. Reasonable accommodations may be made to enable individuals with disabilities to perform the responsibilities. This job description is not designed to contain a comprehensive list of responsibilities that are required of the role. Responsibilities may change at any time with or without notice." That's generic boilerplate; we should remove boilerplate? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The above is generic job description disclaimer; might be considered boilerplate. Should we remove? It's not EEO but it's a generic disclaimer. Might be considered boilerplate; better to omit. Also: "MMPA provides the opportunity for meaningful work that makes a difference in the dairy industry and in our communities. The diverse talents and perspectives of our employees help us to meet the needs of our member farms and the customers we serve. We are interested in every qualified candidate who is eligible to work in the United States. MMPA is committed to maintaining a safe, healthy, and productive environment for all employees as one of our top priorities. As part of our commitment to your well-being and workplace safety, all applicants are required to undergo a drug screening and background check as part of the hiring process. We are not accepting unsolicited candidate introductions, referrals, or résumés from third-party recruiters or staffing agencies for this position. MMPA is an equal opportunity employer." This is EEO/boilerplate; remove. Thus we keep only substantive content: About Us (maybe as About the role?), Why You’ll Love Working Here (benefits), Requirements For Production Operators (requirements), Production Operators Duties May Include (responsibilities), plus schedule note within requirements. We need to format lists with

• . For prose, use

  . We need to avoid repeating job title as heading. We need to output only HTML fragment. Let's craft:

  About the Company

  but heading must be from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About the Company" not allowed. Could we use "About the role" and put company description there? Might be acceptable. 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, not exclusive? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those exact headings. So we should only use those headings. So we cannot use "About the Company". We could use "About the role" and put company description there, though it's not exactly about role but maybe okay. Or we could omit About the role section entirely. Since we have no explicit "About the role" content, better to omit. Thus we will have sections: Responsibilities, Requirements, Benefits, Schedule. Now extract content for each. Responsibilities: from "Production Operators Duties May Include" list: - Knowledge of the product flows pertaining to the systems to, to include but no limited to piping, controls, and connections for receiving and the loading out of pasteurized products - Operating butter and powder packing equipment within specifications of packaging standards - Handling pack cases into boxes prepare for shipment to warehouse - Assisting with palletizing and shrink-wrapping pallets to prepare for shipping - Assisting with accurately recording weights, start time, down time, pounds produced, and pallets produced - These duties will change as soon as availability for a skilled position opens Also maybe include "To perform this job successfully..." but that's boilerplate; we omit. We should preserve all substantive information; the line "These duties will change as soon as availability for a skilled position opens" is substantive. Thus responsibilities list items. Requirements: from "Requirements For Production Operators" list: - Ability to work any shift, weekends, or holidays (our plants operate 24/7). - Reliable and consistent attendance required. - Must be able to pass a drug test and background check - High school diploma or General Education Degree (GED) required - Follow Good Manufacturing Practice Regulations, which requires gloves, hairnets, shoe covers and uniforms in working areas -- personal cleanliness is necessary to prevent product contamination - Comply with all applicable food safety regulations and mandates (Safety Quality Foods, Food & Drug Admin, Pasteurized Milk Ordinance) - Ability to constantly stand/walk and frequently bend/flex/twist/squat/carry for an 8-hour shift - Repetitive movements and tasks -- lift, move, slide, and situate 55 pounds routinely - Safely handle cleaning products and chemicals - Ability to read and understand standard operating procedures in a team environment - Prior experience in manufacturing or dairy is preferred Also note: "Ability to work any shift, weekends, or holidays (our plants operate 24/7)." This also informs schedule; we could move schedule detail to Schedule section, but we can keep in requirements and also schedule. However we should not duplicate. Better to put schedule info in Schedule section, and remove from requirements? But requirement includes ability to work any shift etc. That's a requirement. We could keep it in requirements and also have schedule section referencing same. Might duplicate. Better to keep requirement as is, and schedule section could note shift flexibility. But we risk duplication. The instruction: preserve ALL substantive information; do not invent or summarize away detail. Duplication is okay if it's present in source? The source includes that sentence only once. If we put it in both sections, we duplicate. Better to keep it only once. Where does it fit best? It's about schedule, but also a requirement. Since we have a Schedule section, we could place it there and not duplicate in requirements. However the requirement list also includes other items; we could keep the requirement list without that sentence, and put schedule separately. That would preserve all info (the sentence appears in schedule). That's acceptable. Thus requirements list excludes the shift sentence. Now Benefits: from "Why You’ll Love Working Here": - Competitive salary - Health and wellness benefits with medical coverage through Blue Cross Blue Shield, including mental health benefits - Disability insurance - Paid time off - Employer-matched 401(k) retirement savings plan - Personal and professional growth opportunities - Employee appreciation events and recognition awards - Employee wellness initiatives - Employee feedback and suggestion forums Note: "Competitive salary" is vague but it's a statement; we might include it as benefit? It's under benefits heading. The rule: never create Benefits sections unless posting actually states them. It does state benefits list; includes "Competitive salary". That's okay. Now Schedule: from ability to work any shift, weekends, or holidays (our plants operate 24/7). So schedule section: Ability to work any shift, weekends, or holidays; plants operate 24/7.