Maintenance Supervisor (3rd Shift) – St Joseph Prepared Foods Plant
for section headings
- Use - for lists
- Use
for prose
- Don't repeat job title as heading
- Don't put Job ID/requisition as headings
- Fold minor metadata into short
or drop
- Preserve ALL substantive information
- Remove boilerplate (cookie/nav/legal/EEO/scam-warning, duplicated lines, application instructions)
- Include section ONLY when real specific content exists
- Never emit heading followed by filler/placeholder text
- Never create Pay/Schedule/Benefits unless posting actually states them
- Prefer few substantive sections over many thin ones
- Output ONLY HTML fragment, no html/body, no markdown fences
Let me structure this:
1. Summary/About the role - there's a SUMMARY paragraph
2. Responsibilities - list
3. Requirements - could break into subsections but maybe keep as one section with sub-lists? The rules say use h3 for section headings like "Requirements". The posting has "REQUIREMENTS:" with subsections: Experience and Education, Communication Skills, Computer Skills. Then "QUALIFICATIONS AND SKILLS:" with Leadership and Technical Skills, Preventive Maintenance and Safety. Then "ADDITIONAL REQUIREMENTS:" and "POSITION SPECIFIC REQUIREMENTS:". I should probably combine Requirements and Qualifications into one "Requirements" section with sub-lists, or separate? The rules say use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So "Requirements" and "Qualifications" are separate example headings. But the posting has both "REQUIREMENTS" and "QUALIFICATIONS AND SKILLS". I'll make "Requirements" and "Qualifications" as separate h3 sections.
4. Benefits - there are benefits mentioned: "BENEFITS ON DAY ONE OF EMPLOYMENT and EDUCATION ASSISTANCE!" and later "We provide our team members and their families with paid time off; 401(k) plans; affordable health, life, dental, vision and prescription drug benefits; and more." So Benefits section is warranted.
5. Schedule - shift details are specific: 3rd shift, Sunday-Thursday, 10pm-7am, weekends/overtime as needed, additional compensation for 6th/7th workdays. So Schedule section.
6. Additional metadata: Relocation Assistance Eligible: No, Work Shift: 3rd shift (already in schedule), background check note, hourly applicants note, physical requirements, sponsorship not available, must reside in US, resume format recommendation. Some of these can be folded into a "Additional Information" section or dropped if boilerplate. The rules: "fold minor metadata into a short
or drop it." Things like "Must reside in the United States to be considered", "Sponsorship is not available", "Relocation Assistance Eligible: No", "Work Shift: 3RD SHIFT" (already covered), background check, hourly applicants task, physical requirements, AI tools policy, unsolicited assistance. Many of these are boilerplate or minor. I'll include the substantive ones: residency requirement, no sponsorship, no relocation, physical requirements, background check possibility. The AI tools policy is specific to Tyson but maybe keep? It's a company policy. The unsolicited assistance is boilerplate. The hourly applicants note is specific to application process - maybe drop as application instruction. The rules say remove application instructions. So drop hourly applicants note. The AI tools policy is a company expectation - could include in Additional Information.
I'll create an "Additional Information" section for miscellaneous specifics.
Now, let's write HTML.
Sections:
- About the role (summary)
- Responsibilities
- Requirements (experience/education, communication, computer skills)
- Qualifications (leadership/technical, preventive maintenance/safety)
- Additional Requirements (availability for weekend work)
- Position Specific Requirements (resume format, residency, sponsorship, AI tools)
- Benefits
- Schedule
- Additional Information (relocation, background check, physical requirements)
But the rules: "Prefer a few substantive sections over many thin ones." So maybe combine Requirements and Qualifications into one "Requirements & Qualifications" section? But the example headings include both Requirements and Qualifications as separate. I'll keep them separate as they are distinct in the posting.
Also "Additional Requirements" and "Position Specific Requirements" are thin. Could combine into "Additional Requirements". The posting has "ADDITIONAL REQUIREMENTS:" with one bullet (availability for weekend work) and "POSITION SPECIFIC REQUIREMENTS:" with several bullets. I'll combine into "Additional Requirements".
Let's draft.
Note: The posting starts with "Highly recommend attaching a resume in a Word or PDF format when applying" - that's in Position Specific Requirements. Also "At Tyson Foods, we believe..." is intro prose. Could be part of About the role or a separate intro paragraph. The rules: use
for prose. I'll include a brief intro paragraph before sections? The rules say output HTML fragment with sections. Probably start with a
for the intro, then sections.
But the rules: "Do NOT repeat the job title as a heading (the page already shows it)". So no h3 for job title.
I'll structure:
At Tyson Foods, we believe that our team members are the heart of our success. Are you ready to take on a dynamic role where you can make a significant impact? Join Our Team in the Prepared Foods Division. We invest in our team members and their success by providing resources like benefits on day one of employment and education assistance!
About the role
As a Maintenance Supervisor, you will play a critical role in keeping production running safely, efficiently, and reliably.
Responsibilities
- Lead and direct maintenance technicians, fostering a well-trained and motivated team.
- Assist the Maintenance Manager in directing and coordinating maintenance policies and procedures while maintaining a safe and clean environment.
- Manage and oversee preventative maintenance and repairs of equipment.
- Quickly assess problems to minimize production downtime.
- Maintain knowledge of SQF Quality Management policies and procedures along with GMP practices.
- Ensure all maintenance staff understand and follow company policies and procedures.
Requirements
Experience and Education
- 3+ years as a maintenance technician or closely related role.
- Experience in directing, evaluating and training maintenance technicians preferred.
- Associate's degree or relevant college certificate in a related field preferred, along with hands-on experience as a maintenance technician in a manufacturing environment.
Communication Skills
- Proficient in verbal communication, with the ability to listen, understand, and articulate ideas effectively.
- Strong written communication skills for clear expression and comprehension of ideas and concepts.
Computer Skills
- Basic PLC experience required.
- Knowledge of Microsoft Office Suite; experience with SAP is a plus.
Qualifications
Leadership and Technical Skills
- Ability and experience in leading, directing, evaluating, and training a team of maintenance technicians.
- Skilled in measuring, monitoring, and reducing machine downtime, and diagnosing basic electrical, mechanical, pneumatic, plumbing, and electronic (PLC) issues, with the capacity to direct or assist in repairs.
Preventive Maintenance and Safety
- Capable of promoting a "Safety First" culture among staff and developing/maintaining an effective preventive maintenance program for equipment and plant.
Additional Requirements
- Availability for some weekend work as needed.
- Highly recommend attaching a resume in a Word or PDF format when applying.
- Must reside in the United States to be considered.
- Sponsorship is not available for this position.
- All professional team members are expected to demonstrate responsible use of approved AI tools, including safeguarding sensitive information, adhering to company policies, and validating AI-generated outputs. Individual Contributors should demonstrate the ability to integrate AI into daily work, improve efficiency through AI-enabled solutions, evaluate outputs critically, and apply professional judgment when using AI. People Leaders should demonstrate the ability to drive responsible AI adoption, enable effective use of approved solutions, identify opportunities to improve team performance through AI, and ensure accountability for the quality and accuracy of AI-supported outcomes.
Benefits
- Benefits on day one of employment
- Education assistance
- Paid time off
- 401(k) plans
- Affordable health, life, dental, vision, and prescription drug benefits
Schedule
- Shift: 3rd shift (Sunday – Thursday)
- Hours: 10:00 PM – 7:00 AM / end of shift (flex as needed)
- Weekends and overtime as needed to support operations
- Additional compensation provided for 6th and 7th workdays
Additional Information
- Relocation assistance: Not eligible
- Certain roles require background checks; if offered a position requiring a background check, additional documentation will be provided.
- The successful candidate must be willing and able to perform the physical requirements of the job with or without a reasonable accommodation.
Check for any missing substantive info: The "Hourly Applicants ONLY - You must complete the task after submitting your application..." is application instruction, remove. EEO statement removed. Privacy notice removed. Unsolicited assistance removed. Good.
Now, ensure no markdown fences, just HTML. Use proper tags. The rules say use for section headings. I used for subsections. That's okay? The rules didn't forbid h4, but they said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Subsections could be h4 or just bold? But they said use - for any list of duties/requirements/benefits, and
for prose. They didn't mention subheadings. However, the posting has clear subsections under Requirements and Qualifications. Using h4 is semantic and acceptable. But to be safe, maybe use or just incorporate into list items? The rules:
for prose - Don't repeat job title as heading - Don't put Job ID/requisition as headings - Fold minor metadata into short
or drop - Preserve ALL substantive information - Remove boilerplate (cookie/nav/legal/EEO/scam-warning, duplicated lines, application instructions) - Include section ONLY when real specific content exists - Never emit heading followed by filler/placeholder text - Never create Pay/Schedule/Benefits unless posting actually states them - Prefer few substantive sections over many thin ones - Output ONLY HTML fragment, no html/body, no markdown fences Let me structure this: 1. Summary/About the role - there's a SUMMARY paragraph 2. Responsibilities - list 3. Requirements - could break into subsections but maybe keep as one section with sub-lists? The rules say use h3 for section headings like "Requirements". The posting has "REQUIREMENTS:" with subsections: Experience and Education, Communication Skills, Computer Skills. Then "QUALIFICATIONS AND SKILLS:" with Leadership and Technical Skills, Preventive Maintenance and Safety. Then "ADDITIONAL REQUIREMENTS:" and "POSITION SPECIFIC REQUIREMENTS:". I should probably combine Requirements and Qualifications into one "Requirements" section with sub-lists, or separate? The rules say use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So "Requirements" and "Qualifications" are separate example headings. But the posting has both "REQUIREMENTS" and "QUALIFICATIONS AND SKILLS". I'll make "Requirements" and "Qualifications" as separate h3 sections. 4. Benefits - there are benefits mentioned: "BENEFITS ON DAY ONE OF EMPLOYMENT and EDUCATION ASSISTANCE!" and later "We provide our team members and their families with paid time off; 401(k) plans; affordable health, life, dental, vision and prescription drug benefits; and more." So Benefits section is warranted. 5. Schedule - shift details are specific: 3rd shift, Sunday-Thursday, 10pm-7am, weekends/overtime as needed, additional compensation for 6th/7th workdays. So Schedule section. 6. Additional metadata: Relocation Assistance Eligible: No, Work Shift: 3rd shift (already in schedule), background check note, hourly applicants note, physical requirements, sponsorship not available, must reside in US, resume format recommendation. Some of these can be folded into a "Additional Information" section or dropped if boilerplate. The rules: "fold minor metadata into a short
or drop it." Things like "Must reside in the United States to be considered", "Sponsorship is not available", "Relocation Assistance Eligible: No", "Work Shift: 3RD SHIFT" (already covered), background check, hourly applicants task, physical requirements, AI tools policy, unsolicited assistance. Many of these are boilerplate or minor. I'll include the substantive ones: residency requirement, no sponsorship, no relocation, physical requirements, background check possibility. The AI tools policy is specific to Tyson but maybe keep? It's a company policy. The unsolicited assistance is boilerplate. The hourly applicants note is specific to application process - maybe drop as application instruction. The rules say remove application instructions. So drop hourly applicants note. The AI tools policy is a company expectation - could include in Additional Information. I'll create an "Additional Information" section for miscellaneous specifics. Now, let's write HTML. Sections: - About the role (summary) - Responsibilities - Requirements (experience/education, communication, computer skills) - Qualifications (leadership/technical, preventive maintenance/safety) - Additional Requirements (availability for weekend work) - Position Specific Requirements (resume format, residency, sponsorship, AI tools) - Benefits - Schedule - Additional Information (relocation, background check, physical requirements) But the rules: "Prefer a few substantive sections over many thin ones." So maybe combine Requirements and Qualifications into one "Requirements & Qualifications" section? But the example headings include both Requirements and Qualifications as separate. I'll keep them separate as they are distinct in the posting. Also "Additional Requirements" and "Position Specific Requirements" are thin. Could combine into "Additional Requirements". The posting has "ADDITIONAL REQUIREMENTS:" with one bullet (availability for weekend work) and "POSITION SPECIFIC REQUIREMENTS:" with several bullets. I'll combine into "Additional Requirements". Let's draft. Note: The posting starts with "Highly recommend attaching a resume in a Word or PDF format when applying" - that's in Position Specific Requirements. Also "At Tyson Foods, we believe..." is intro prose. Could be part of About the role or a separate intro paragraph. The rules: use
for prose. I'll include a brief intro paragraph before sections? The rules say output HTML fragment with sections. Probably start with a
for the intro, then sections. But the rules: "Do NOT repeat the job title as a heading (the page already shows it)". So no h3 for job title. I'll structure:
At Tyson Foods, we believe that our team members are the heart of our success. Are you ready to take on a dynamic role where you can make a significant impact? Join Our Team in the Prepared Foods Division. We invest in our team members and their success by providing resources like benefits on day one of employment and education assistance!
About the role
As a Maintenance Supervisor, you will play a critical role in keeping production running safely, efficiently, and reliably.
Responsibilities
- Lead and direct maintenance technicians, fostering a well-trained and motivated team.
- Assist the Maintenance Manager in directing and coordinating maintenance policies and procedures while maintaining a safe and clean environment.
- Manage and oversee preventative maintenance and repairs of equipment.
- Quickly assess problems to minimize production downtime.
- Maintain knowledge of SQF Quality Management policies and procedures along with GMP practices.
- Ensure all maintenance staff understand and follow company policies and procedures.
Requirements
Experience and Education
- 3+ years as a maintenance technician or closely related role.
- Experience in directing, evaluating and training maintenance technicians preferred.
- Associate's degree or relevant college certificate in a related field preferred, along with hands-on experience as a maintenance technician in a manufacturing environment.
Communication Skills
- Proficient in verbal communication, with the ability to listen, understand, and articulate ideas effectively.
- Strong written communication skills for clear expression and comprehension of ideas and concepts.
Computer Skills
- Basic PLC experience required.
- Knowledge of Microsoft Office Suite; experience with SAP is a plus.
Qualifications
Leadership and Technical Skills
- Ability and experience in leading, directing, evaluating, and training a team of maintenance technicians.
- Skilled in measuring, monitoring, and reducing machine downtime, and diagnosing basic electrical, mechanical, pneumatic, plumbing, and electronic (PLC) issues, with the capacity to direct or assist in repairs.
Preventive Maintenance and Safety
- Capable of promoting a "Safety First" culture among staff and developing/maintaining an effective preventive maintenance program for equipment and plant.
Additional Requirements
- Availability for some weekend work as needed.
- Highly recommend attaching a resume in a Word or PDF format when applying.
- Must reside in the United States to be considered.
- Sponsorship is not available for this position.
- All professional team members are expected to demonstrate responsible use of approved AI tools, including safeguarding sensitive information, adhering to company policies, and validating AI-generated outputs. Individual Contributors should demonstrate the ability to integrate AI into daily work, improve efficiency through AI-enabled solutions, evaluate outputs critically, and apply professional judgment when using AI. People Leaders should demonstrate the ability to drive responsible AI adoption, enable effective use of approved solutions, identify opportunities to improve team performance through AI, and ensure accountability for the quality and accuracy of AI-supported outcomes.
Benefits
- Benefits on day one of employment
- Education assistance
- Paid time off
- 401(k) plans
- Affordable health, life, dental, vision, and prescription drug benefits
Schedule
- Shift: 3rd shift (Sunday – Thursday)
- Hours: 10:00 PM – 7:00 AM / end of shift (flex as needed)
- Weekends and overtime as needed to support operations
- Additional compensation provided for 6th and 7th workdays
Additional Information
- Relocation assistance: Not eligible
- Certain roles require background checks; if offered a position requiring a background check, additional documentation will be provided.
- The successful candidate must be willing and able to perform the physical requirements of the job with or without a reasonable accommodation.
for section headings. I used for subsections. That's okay? The rules didn't forbid h4, but they said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Subsections could be h4 or just bold? But they said use - for any list of duties/requirements/benefits, and
for prose. They didn't mention subheadings. However, the posting has clear subsections under Requirements and Qualifications. Using h4 is semantic and acceptable. But to be safe, maybe use or just incorporate into list items? The rules:
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Subsections could be h4 or just bold? But they said use - for any list of duties/requirements/benefits, and
for prose. They didn't mention subheadings. However, the posting has clear subsections under Requirements and Qualifications. Using h4 is semantic and acceptable. But to be safe, maybe use or just incorporate into list items? The rules:
for prose. They didn't mention subheadings. However, the posting has clear subsections under Requirements and Qualifications. Using h4 is semantic and acceptable. But to be safe, maybe use or just incorporate into list items? The rules: