Business Unit Manager
ITW Food Equipment Group · Fort Worth, TX · 1 mo ago
Business Development$16/hrFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no summarizing away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "ITW is an equal opportunity employer..." etc. Also remove "PHYSICAL DEMANDS & WORK ENVIRONMENT"? That might be considered part of responsibilities? It's not a required heading; but we could include under Responsibilities? However we should not create sections unless posting has real specific content for it. The posting includes Physical Demands & Work Environment and Hours Of Work. Those could be considered under a "Work Environment" or "Schedule" section. The instructions say use
under
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no summarizing away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "ITW is an equal opportunity employer..." etc. Also remove "PHYSICAL DEMANDS & WORK ENVIRONMENT"? That might be considered part of responsibilities? It's not a required heading; but we could include under Responsibilities? However we should not create sections unless posting has real specific content for it. The posting includes Physical Demands & Work Environment and Hours Of Work. Those could be considered under a "Work Environment" or "Schedule" section. The instructions say use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can create sections for Responsibilities, Requirements (maybe combine Experience & Skills), Qualifications, Skills, Benefits, Pay, Schedule. But we must only include sections when posting has real specific content. The posting includes a "TOTAL REWARDS PACKAGE" with link to benefits. It does not detail specific benefits, just says broad and offers comprehensive support, link for more details. That is not specific detail; we should not create a Benefits section if it's just generic and no specifics. The instruction: 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. The posting does not state specific benefits, pay, or schedule details beyond "Hours Of Work Monday – Friday, 8 hours per day with flex starting times. Infrequent weekend work based on business needs." That is schedule info. So we can create a Schedule section with that content. Pay: not stated, so omit. Benefits: not specific details, just link; but maybe we could include a Benefits section with the link? The instruction says never create Benefits sections unless posting actually states them. It states "Our total rewards package is broad and offers comprehensive support from health and wellness to retirement and financial stability. For more details see https://...". That is a statement about benefits but not specific. Might be considered filler? It's not placeholder like "varies". It's a description but not specific. The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state a total rewards package, albeit vague. I'd lean to include a Benefits section with that description (maybe include the link). However we must preserve ALL substantive information; we cannot drop the link. So we should include Benefits section with that sentence and link.
Now About the role: The posting includes a Position Summary. That could be About the role. We'll create an About the role section with the Position Summary paragraph(s). Also there is introductory paragraph about ITW and Traulsen etc. That's company overview; maybe not needed as a section but could be part of About the role? The instructions: do not repeat job title as heading; we can include About the role summarizing the role and maybe company context. We'll include the Position Summary as About the role.
Responsibilities: there is a "Position Responsibilities" bullet list (actually sentences). We'll put each as
- .
Requirements: The posting has "Experience & Skills Required Qualifications" then lists Required Qualifications (bulleted) and Preferred Qualifications. We could split into Requirements (maybe Required Qualifications) and Skills? But we have separate headings for Requirements, Qualifications, Skills. The instruction says use those headings as examples; we can decide which to use. We have Required Qualifications (education, years, etc.) and Preferred Qualifications. Also there are skills listed within required qualifications (leadership, communication, etc.). We could combine Required Qualifications under Requirements, and Preferred Qualifications under Qualifications? Or we could have Requirements (required) and Qualifications (preferred). Skills could be extracted from required qualifications list (leadership, communication, etc.) but that would duplicate. Better to follow the example: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Schedule. We'll omit Pay. Now we need to map content: - About the role: Position Summary paragraph(s). Also maybe include the introductory description about ITW and Traulsen? That's company overview, not role-specific. Might be considered part of About the role? The instruction says preserve ALL substantive information; we cannot drop company overview. But we could include it in About the role as context. However About the role heading is for role description; but we can include company overview there as it's substantive. Let's include the first paragraphs up to "Position Summary". Actually the text starts with "Job Description Illinois Tool Works Inc...." then describes ITW, Traulsen, C-Series, then "TOTAL REWARDS PACKAGE", then "Position Summary". So we could put the company overview in About the role as well. - Responsibilities: the list under "Position Responsibilities". We'll extract each sentence as a list item. - Requirements: Required Qualifications bullet list (the ones after "Experience & Skills Required Qualifications"). - Qualifications: Preferred Qualifications bullet list. - Skills: maybe we can extract the skill statements from Required Qualifications? But they are already there. Could also list skills like "Strong analytical, problem-solving, and financial management capabilities" etc. But those are already in Required Qualifications. To avoid duplication, maybe we skip Skills section. However the instruction says we can include Skills if we have specific content. We could pull out skill phrases: "Excellent leadership, communication, presentation, and influencing skills", "Strong analytical, problem-solving, and financial management capabilities", "Ability to navigate complex business environments", "Customer-focused mindset". But those are already in Required Qualifications. If we create Skills section, we would be duplicating content. The instruction says preserve ALL substantive information; duplication is not prohibited but might be redundant. Better to not create Skills section if we already covered them under Requirements. But we need to follow the instruction: "Prefer a few substantive sections over many thin ones." So we can combine Requirements and Qualifications and maybe Skills into one? But we have headings examples; we can choose to include only those sections with real content. Let's decide: We'll have About the role, Responsibilities, Requirements (covers required qualifications), Qualifications (covers preferred qualifications), Benefits, Schedule. No Skills. Now Benefits: we have the total rewards package sentence and link. We'll put that as a
with the link. Schedule: Hours Of Work sentence. We must not include boilerplate like "ITW is an equal opportunity employer..." etc. Also remove "PHYSICAL DEMANDS & WORK ENVIRONMENT". That's substantive but not under any heading we chose. Should we include it? It's about work environment; we could incorporate into Schedule? Not really. Could create a section "Work Environment" but not in the allowed headings list. The instruction says use