Setup & Operate Fin Roll 2nd Shift (Coil)

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. 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. Include a section ONLY when posting has real, specific content for it — never emit 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 posting actually states them. Prefer few substantive sections over many thin ones. We need to parse the posting. Content: - Intro about Modine (company description). Could be "About the role"? Actually "About the role" maybe not present; but we could have "About Modine" maybe not required. The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can include sections that have content. We have: - Position Description: Setup and operate a fin press per instructions from a Group Leader to produce fins or complete coils of acceptable quality. - Key Responsibilities: This position requires the ability to setup and operate a fin press for various fins per inch and corrugation, setup and operate an expander for various coil widths, lengths, depths and designs and coil assembly. This position is also responsible for recognizing malfunctions of equipment versus improper setup when products do not agree with drawings, have the ability to read and interpret drawings and ability to use various measuring instruments. - Position Requirements: Must have high school education or equivalent. Must be flexible, problem solving oriented, acceptable to change and display initiative to learn and make improvements in the workplace. - Key Responsibilities Required Education & Qualifications (duplicate heading? Actually appears as a line but we can ignore duplicate.) - Why Choose Modine? Then benefits listed: Health & Well-being: Day One Competitive health, dental & vision insurance coverage Employee Assistance Program After 90 days of continuous employment Maternity Leave (12 weeks at 100% pay) 8 weeks of short term disability leave paid at 100% 4 weeks of paid parental leave paid at 100% Paternity Leave (4 weeks at 100% pay) Financial Benefits: 401k Retirement plan and company paid match Life Insurance Health Savings Account (HSA) with employer contribution Flexible Spending Accounts (FSA) Short Term Disability (company paid) Long Term Disability Work-Life Balance: Competitive time-off policies Tuition Reimbursement To view full benefits information: MyModine Benefits - Then EEO boilerplate etc to remove. - Salary range: "The salary range for this position is estimated in good faith to be [minimum amount – maximum amount]. The specific offer will depend on the candidate’s qualifications, experience, and other job-related considerations but will be within the stated range." This is placeholder with brackets; it's not actual numbers. According to rule: never emit Pay section unless posting actually states them. Since it's placeholder "[minimum amount – maximum amount]" it's not specific; we should not create Pay section. So we omit Pay. - Schedule: Not mentioned. So no Schedule. - Benefits: we have specific benefits listed. So we can create Benefits section with list. - Responsibilities: we have responsibilities described. So we can create Responsibilities section with list. - Requirements: we have Position Requirements. So we can create Requirements section with list. - Qualifications: maybe same as Requirements? The posting includes "Key Responsibilities Required Education & Qualifications" but not separate Qualifications. We could combine Requirements and Qualifications? But we should not create thin sections. We could have Requirements section covering both education and qualifications. Or we could have Qualifications separate if there is content. There's not explicit qualifications beyond education. So we can skip Qualifications. - Skills: Not explicitly listed; maybe implied but not separate. So skip. - About the role: Could include the introductory description about Modine? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could have About the role section describing the role (position description). That seems appropriate: we have Position Description: Setup and operate a fin press per instructions from a Group Leader to produce fins or complete coils of acceptable quality. That's about the role. So we can put that in About the role. Thus sections: About the role, Responsibilities, Requirements, Benefits. We need to ensure we don't repeat job title as heading. Not needed. We need to remove boilerplate: EEO, equal opportunity, etc. Also remove duplicated lines like "Key Responsibilities Required Education & Qualifications". Also remove "To view full benefits information: MyModine Benefits" maybe part of benefits but we can keep as a note? It's not a benefit itself; it's a reference. Could be considered boilerplate? Might be okay to keep as part of benefits description but it's not a benefit. Might be considered navigation? Probably safe to keep as a sentence in benefits section? But instruction: remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "To view full benefits information: MyModine Benefits" is not exactly boilerplate but could be considered a reference; but it's not a benefit. Might be okay to keep as a note but it's not a list item. Could be placed as a

  after the list. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep the benefits details exactly as listed. Let's extract benefits: Health & Well-being: Day One Competitive health, dental & vision insurance coverage Employee Assistance Program After 90 days of continuous employment Maternity Leave (12 weeks at 100% pay) 8 weeks of short term disability leave paid at 100% 4 weeks of paid parental leave paid at 100% Paternity Leave (4 weeks at 100% pay) Financial Benefits: 401k Retirement plan and company paid match Life Insurance Health Savings Account (HSA) with employer contribution Flexible Spending Accounts (FSA) Short Term Disability (company paid) Long Term Disability Work-Life Balance: Competitive time-off policies Tuition Reimbursement We need to turn these into list items. Could group by category but not required. We'll just list each benefit as

  . Might be long but okay. We need to ensure we don't lose any detail: include "Day One" maybe as part of first item: "Competitive health, dental & vision insurance coverage (Day One)". Actually the text: "Health & Well-being: Day One Competitive health, dental & vision insurance coverage Employee Assistance Program After 90 days of continuous employment Maternity Leave (12 weeks at 100% pay) 8 weeks of short term disability leave paid at 100% 4 weeks of paid parental leave paid at 100% Paternity Leave (4 weeks at 100% pay)". So we can parse: - Competitive health, dental & vision insurance coverage (Day One) - Employee Assistance Program - After 90 days of continuous employment: Maternity Leave (12 weeks at 100% pay) - 8 weeks of short term disability leave paid at 100% - 4 weeks of paid parental leave paid at 100% - Paternity Leave (4 weeks at 100% pay) Financial Benefits: - 401k Retirement plan and company paid match - Life Insurance - Health Savings Account (HSA) with employer contribution - Flexible Spending Accounts (FSA) - Short Term Disability (company paid) - Long Term Disability Work-Life Balance: - Competitive time-off policies - Tuition Reimbursement We'll output as

  • items. Responsibilities: list items: - Setup and operate a fin press for various fins per inch and corrugation - Setup and operate an expander for various coil widths, lengths, depths and designs and coil assembly - Recognize malfunctions of equipment versus improper setup when products do not agree with drawings - Ability to read and interpret drawings - Ability to use various measuring instruments Also the initial sentence: "Setup and operate a fin press per instructions from a Group Leader to produce fins or complete coils of acceptable quality." That's part of Position Description; we could include that as a responsibility as well. But we already have About the role covering that. Might duplicate. Better to keep About the role as a prose paragraph describing the role, and Responsibilities as list of duties. Thus About the role:

    Setup and operate a fin press per instructions from a Group Leader to produce fins or complete coils of acceptable quality.

    Responsibilities:
    • ... etc.
    Requirements: list: - Must have high school education or equivalent. - Must be flexible, problem solving oriented, acceptable to change and display initiative to learn and make improvements in the workplace. We could split into two items. Now Benefits: as above. We must not include Pay or Schedule sections. We must not include any boilerplate like EEO, etc. We must output only HTML fragment, no /, no markdown. Let's craft. Check for duplicate lines: we have "Key Responsibilities" appears twice in original; we ignore. Check for any other substantive content: "Why Choose Modine?" heading but we treat as Benefits. Now ensure we preserve all substantive information: The company description intro about Modine (first paragraph) is not required per sections? Could be considered "About the role"? But it's about company not role. The instruction says we can use About the role heading; but we could also include a short paragraph about Modine if we want, but not required. The instruction: "Prefer a few substantive sections over many thin ones." Including company description might be a thin section; but it's substantive. However the sections list does not include "About the company". But we could incorporate into About the role? Might be okay to add a brief paragraph about Modine as part of About the role? But the role description is separate. The instruction says use headings like About the role, Responsibilities, etc. It doesn't forbid adding other headings, but we should stick to those. The company description is not about the role; but we could omit it as it's not required for the role? However we must preserve ALL substantive information; do not invent or summarize away detail. If we omit the company description, we are losing substantive information about the company. But is that considered substantive for the job posting? Likely yes, it's background about the employer. The instruction says preserve ALL substantive information; do not invent or summarize away detail. So we should keep it. Where to put it? Could be a preceding paragraph before any headings, as plain

    . That's allowed because we can have prose outside sections. The instruction only says use headings for sections; doesn't forbid extra paragraphs. So we can include a

    with the company description before the sections. Thus output:

    For more than 100 years, Modine has solved the toughest thermal management challenges for mission-critical applications. Our purpose of Engineering a Cleaner, Healthier World™ means we are always evolving our portfolio of technologies to provide the latest heating, cooling, and ventilation solutions. Through the hard work of more than 11,000 employees worldwide, our Climate Solutions and Performance Technologies segments advance our purpose with systems that improve air quality, reduce energy and water consumption, lower harmful emissions, enable cleaner running vehicles, and use environmentally friendly refrigerants. Modine is a global company headquartered in Racine, Wisconsin (U.S.),