Production Supervisor - Weekend Days

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. We need to parse the job description. Content: - Intro paragraph: "As an ISC Production Supervisor here at Honeywell Aerospace, you will oversee production processes, ensure goals are met efficiently, maintain quality and safety standards, lead a team, manage resources, and implement improvements You will report directly to our Sr ISC Operations Manager and you’ll work out of our Minneapolis, MN location on an On-site work schedule. In this role, you will impact the production operations within the AERO business group, ensuring that products are manufactured efficiently and meet customer requirements. You will play a critical role in driving operational excellence, maintaining high-quality standards, and fostering a culture of continuous improvement. Supervise a team of individual contributors who are manufacturing Honeywell Aerospace's world class innovative products. You will leverage your manufacturing experience and skills to lead some of the world's most talented production employees. You will use your leadership abilities to contribute to driving safety, productivity, and exceptional quality at Minneapolis, one of Honeywell Aerospace production facilities. Through collaboration with cross functional teams, you will prioritize team workload and drive continuous improvement. As a team supervisor, you will coach your team members in technical and behavioral competencies in order to deliver high impact business results." That's the "About the role" content. Then "Responsibilities" list: Directly supervise production operators, Drive productivity improvements, Enforce compliance, Engage in plant maintenance program, Drive culture of continuous improvement, Employee Development, Resource management in dynamic environment, Talent management, Review quality output and coach team on improvements, Collaborate with customers and cross functional teams. Then "Qualifications" heading: "YOU MUST HAVE High School Diploma or GED 2 years in Manufacturing/Supply Chain/Operations/Logistics WE VALUE Associates or Bachelor's degree Leadership experience Experience leading in a union environment Some relevant manufacturing experience Ability to troubleshoot processes and equipment Conveys information with clarity and directness Some relevant leadership experience Computer literacy Willingness to consistently take the initiative to get things done Ability to document and train others on manufacturing processes" We need to separate into sections: maybe "Requirements" for must-have, "Qualifications" for valued, "Skills" for abilities? The instruction says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have: - About the role: intro paragraph. - Responsibilities: list. - Requirements: "YOU MUST HAVE High School Diploma or GED 2 years in Manufacturing/Supply Chain/Operations/Logistics". Possibly also "US PERSON REQUIREMENT" maybe but that's a legal requirement; but we should include if it's substantive. It says "Due to compliance with U.S. export control laws and regulations, candidate must be a U.S. person..." That is a requirement. Should we include under Requirements? Probably yes. But we must not include boilerplate like EEO; but this is a specific requirement. So include. - Qualifications: "WE VALUE Associates or Bachelor's degree Leadership experience Experience leading in a union environment Some relevant manufacturing experience Ability to troubleshoot processes and equipment Conveys information with clarity and directness Some relevant leadership experience Computer literacy Willingness to consistently take the initiative to get things done Ability to document and train others on manufacturing processes". That's valued qualifications. - Skills: maybe we can extract skills from the list: leadership, troubleshooting, communication, computer literacy, initiative, documentation/training. Could also include "Ability to document and train others". But we need to avoid duplication. The instruction says prefer a few substantive sections over many thin ones. We could combine Qualifications and Skills? But we have separate headings allowed. We need to decide if we have enough content for Skills separate from Qualifications. The qualifications list includes many skill-like items. Could treat "Skills" as subset: maybe "Ability to troubleshoot processes and equipment", "Conveys information with clarity and directness", "Computer literacy", "Willingness to consistently take the initiative", "Ability to document and train others". However, the qualifications already include those. Might be better to put all under Qualifications and not create Skills section if it would be thin. But we need to follow instruction: include a section ONLY when posting has real, specific content for it. If we put Skills, we need specific content. We could extract skills: Leadership experience, Ability to troubleshoot, Communication clarity, Computer literacy, Initiative, Documentation/training. That's specific enough. But then Qualifications would be left with education and experience requirements? Actually Qualifications could be education/degree etc. Let's split: - Requirements: Must have: High School Diploma or GED, 2 years in Manufacturing/Supply Chain/Operations/Logistics, US person requirement. - Qualifications: Valued: Associates or Bachelor's degree, Leadership experience, Experience leading in a union environment, Some relevant manufacturing experience, Some relevant leadership experience (maybe duplicate), Willingness to consistently take the initiative, Ability to document and train others. - Skills: Ability to troubleshoot processes and equipment, Conveys information with clarity and directness, Computer literacy. But we have duplication of leadership experience etc. Might be okay. Alternatively, we could keep Qualifications as all valued items and not create Skills. The instruction says prefer a few substantive sections over many thin ones. So better to have fewer sections. Let's include About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Schedule: we have On-site work schedule mentioned. That's schedule info: "you’ll work out of our Minneapolis, MN location on an On-site work schedule." That's schedule. So we can include Schedule section with that sentence. Pay: we have salary range: $77,000 - $96,000. Also note about salary guideline. So include Pay. Benefits: list of benefits. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. We should not include Skills if we don't have distinct content; we can omit. Now we need to format:

About the role

... (the intro paragraph)

Responsibilities

• Directly supervise production operators
• Drive productivity improvements
• Enforce compliance
• Engage in plant maintenance program
• Drive culture of continuous improvement
• Employee Development
• Resource management in dynamic environment
• Talent management
• Review quality output and coach team on improvements
• Collaborate with customers and cross functional teams

Requirements

• High School Diploma or GED
• 2 years of experience in Manufacturing/Supply Chain/Operations/Logistics
• Must be a U.S. person (U.S. citizen, permanent resident, or protected status under asylum/refugee) due to export control compliance

Qualifications

• Associates or Bachelor's degree (valued)
• Leadership experience
• Experience leading in a union environment
• Some relevant manufacturing experience
• Some relevant leadership experience
• Ability to troubleshoot processes and equipment
• Conveys information with clarity and directness
• Computer literacy
• Willingness to consistently take the initiative to get things done
• Ability to document and train others on manufacturing processes

But note we moved some skill items into Qualifications; that's okay. Now Benefits:

Benefits

• Employer-subsidized medical, dental, vision and life insurance
• Short-term and long-term disability coverage
• 401(k) match, flexible spending accounts and health savings accounts
• Employee assistance program and educational assistance
• Parental leave and 12 paid holidays
• Paid time off for vacation, personal and sick time

Pay:

Pay

The annual base salary range for this position is $77,000 - $96,000. Honeywell considers various factors when extending an offer, including scope and responsibilities, work experience, education and training, key skills, and market/business considerations.

Schedule:

Schedule

On-site work schedule at the Minneapolis, MN location.

We need to ensure we didn't repeat job title. Not included. We must not include boilerplate like "The application period for the job is estimated to be 40 days..." etc. Remove. Also remove "Explore your benefits: https://..." maybe that's a link; but it's part of benefits? It's a link to benefits page. Might be considered boilerplate? It's a link to benefits page; but it's not a benefit itself. Might be considered navigation? Probably remove. Also remove "About Honeywell Aerospace" section? That's company description; not required headings; but it's substantive? It's about the company, not the role. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Should we include that? It's not under any of the headings we have; but we could include it as a paragraph under About the role? But it's about the company, not the role. The instruction says use headings for specific sections; we could include a paragraph after About the role that is not under a heading? But they said use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They didn't forbid other headings, but they said use those for section headings. It might be okay to include a paragraph without heading? Probably better to incorporate relevant company info into About the role if it's relevant. However, the "About Honeywell Aerospace" is a generic company overview; might be considered boilerplate? It's not specific to the role. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly those, but it's more general company description. Might be considered not substantive to the job? It's somewhat generic but could be considered substantive. However, the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep it. Where to put? Could add a

after About the role before Responsibilities, describing the company. But the About the role heading is for role description; we could add a separate

About Honeywell Aerospace

but that's not in the list. The instruction says use

for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but they gave examples. Safer to include it as a paragraph under About the role? Might blur. Alternatively, we could create a section "About Honeywell Aerospace" as a heading, but it's not in the list; risk of deviating. I'd rather include it as a paragraph after the About the role heading, still under same heading? That would mix role and company info. Might be okay. But the instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are the expected headings. It doesn't say you cannot have other headings, but to be safe, we stick to those. Thus we will incorporate the company description into the About the role paragraph. Let's craft About