Inventory Handler III - 2nd Shift

We need to output HTML fragment with sections only if content present. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to parse the posting. Content: - About us: description of company, vision, values, etc. This could be "About the role"? Actually "About us" is about company, not role. The instruction: use headings for sections like About the role, Responsibilities, etc. We need to decide which sections have content. We have: - Purpose Statement: Inventory Handlers are responsible for performing site warehousing functions that support the overall manufacturing operations and other customer-related activities. That's like a summary of role. - Key Job Accountabilities: list of bullet points (understands and follows policy, works independently, adapts to change, supports continuous improvement). Those are responsibilities. - Education/Experience Qualifications: bullet list: HS diploma/GED preferred, 1+ years experience preferred, must be 18+. - Other Qualifications: list of many items: basic computer skills, attention to detail, self motivated, ability to interpret direction, flexible, able to work overtime, etc., demonstrated competencies list, general office equipment, material handling equipment, able to alternate sit/stand/walk, lift up to 45 pounds, wear PPE. - Physical Requirements: description of work setting. - Travel Requirements: Less than 40%. - Salary Range: $35,200.00 - $52,800.00. - Benefits: mention comprehensive benefits package: medical, dental, vision insurance, paid time off, retirement savings, professional development, work-life balance, perks, link to benefits website. - Also mention "Our commitment to pay range transparency..." but that's about pay. - Also mention "We are pleased to provide reasonable accommodations..." etc. That's boilerplate EEO etc; we should remove. - Also mention "This document does not represent a contract..." etc. Remove. - Also mention "We are an Equal Opportunity Employer..." remove. - Also mention "Some offers of employment are contingent upon successfully passing a drug screen and/or background check." Might be considered boilerplate but maybe keep? It's not a section heading; could be minor metadata. Probably drop as it's legal boilerplate. We need to include sections only if real specific content. Potential sections: - About the role: Could use the Purpose Statement as description. Could also include About us? But "About the role" heading expects description of role. We'll put Purpose Statement there. - Responsibilities: Key Job Accountabilities bullet list. - Requirements: Could combine Education/Experience Qualifications and Other Qualifications? But we have Qualifications heading separate. The instruction: Use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. We have Education/Experience Qualifications (education/experience). Other Qualifications (skills, abilities). Could map: - Qualifications: Education/Experience Qualifications (HS diploma/GED preferred, 1+ years experience, 18+). - Skills: Other Qualifications (basic computer skills, attention to detail, self motivated, ability to interpret direction, flexible, able to work overtime, demonstrated competencies list, equipment, physical ability to lift, etc.) But also Physical Requirements and Travel Requirements could be under Requirements? Or maybe under Requirements we can include physical requirements and travel. However the instruction: Use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide which content fits each. We could treat: - Requirements: Education/Experience Qualifications + Physical Requirements + Travel Requirements (maybe). But we need to avoid filler. - Qualifications: maybe not needed if we already used Requirements for education/experience. But we have both headings; we can use both if we have distinct content. Better: Use: - About the role: Purpose Statement. - Responsibilities: Key Job Accountabilities. - Qualifications: Education/Experience Qualifications. - Skills: Other Qualifications (including computer skills, attention to detail, etc.) plus demonstrated competencies. - Benefits: Benefits package description. - Pay: Salary Range. - Schedule: Travel Requirements? Actually schedule could be shift flexibility, overtime, nights, various shifts, weekends. That's under Other Qualifications (flexible to work overtime, nights, various shifts and weekends as required). Also flexible to work in multiple areas as required. So schedule info is there. Could put under Schedule heading. But we also have Physical Requirements and Travel Requirements; maybe those go under Requirements? Or we could add a separate section for Physical Requirements but not in allowed headings. Since only allowed headings are those listed, we should not create extra headings. So we need to fit Physical Requirements and Travel Requirements somewhere else, maybe under Requirements or Skills. We could put Physical Requirements under Requirements (makes sense: job requirements). Travel Requirements also under Requirements. Thus: - Requirements: Education/Experience Qualifications + Physical Requirements + Travel Requirements. But we also have Qualifications heading; maybe we can use Qualifications for Education/Experience Qualifications, and Requirements for Physical + Travel. However the instruction says use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid using both; we can decide. We need to avoid thin sections. Let's see content volume. Education/Experience Qualifications: 3 bullet points. Physical Requirements: a paragraph about work setting. Travel Requirements: one sentence. If we put all under Requirements, that's decent. Qualifications: maybe we can use for "Other Qualifications" (skills, abilities). That's a lot. Skills: maybe we can use for demonstrated competencies list? But that overlaps. Better: Use: - About the role: Purpose Statement. - Responsibilities: Key Job Accountabilities. - Qualifications: Education/Experience Qualifications. - Skills: Other Qualifications (including computer skills, attention to detail, self motivated, ability to interpret direction, flexible to work overtime/nights/shifts/weekends, flexible to multiple areas, demonstrated competencies list, equipment, lift, PPE). - Benefits: Benefits package. - Pay: Salary Range. - Schedule: Travel Requirements? Actually schedule is about shift flexibility etc. That is already in Skills (flexible to work overtime, nights, various shifts and weekends). So maybe we don't need Schedule separate. But we could put Travel Requirements under Schedule? Travel is less than 40% travel. That's not schedule but travel. Could put under Requirements. We need to decide if we need Schedule heading. The posting does not mention specific schedule like shift times, but mentions flexible to work overtime, nights, various shifts and weekends as required. That's schedule info. So we could create Schedule heading with that content. But we also have flexible to work in multiple areas as required (that's not schedule). Could be under Skills. Thus: - Schedule: flexible to work overtime, nights, various shifts and weekends as required. But we also have "flexible to work in multiple areas as required" maybe under Skills. Travel Requirements: less than 40% travel. Could be under Requirements. Let's allocate: - About the role: Purpose Statement. - Responsibilities: Key Job Accountabilities. - Requirements: Education/Experience Qualifications + Physical Requirements + Travel Requirements. - Qualifications: (maybe we skip because we used Requirements for education/experience; but we still have Qualifications heading allowed; we could use for "Other Qualifications" that are not skills? Hmm. Better to follow the instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should try to fill as many as possible with real content, but avoid filler. Let's map: - About the role: Purpose Statement. - Responsibilities: Key Job Accountabilities. - Requirements: Education/Experience Qualifications (HS diploma/GED preferred, 1+ years experience, 18+). Could also add Physical Requirements? But physical requirements are more like job demands; could be under Requirements as well. - Qualifications: Other Qualifications (basic computer skills, attention to detail, self motivated, ability to interpret direction, flexible to work overtime/nights/shifts/weekends, flexible to multiple areas, demonstrated competencies list, equipment, lift, PPE). That's a lot. - Skills: maybe we can use for demonstrated competencies list (teamwork, professional demeanor, quality, job knowledge, communication, problem solving and lean principles, flexibility, attendance and timeliness). But that overlaps with Qualifications. Could split: Qualifications for education/experience + other baseline qualifications; Skills for specific competencies. - Benefits: Benefits package. - Pay: Salary Range. - Schedule: Travel Requirements? Actually schedule is about shift flexibility; we already have flexible to work overtime etc under Qualifications or Skills. Could put shift flexibility under Schedule. - Travel Requirements: less than 40% travel. Could be under Requirements or maybe under Schedule? Travel is not schedule. Could be under Requirements. We need to avoid duplication. Let's decide final sections: - About the role: Purpose Statement. - Responsibilities: Key Job Accountabilities. - Requirements: Education/Experience Qualifications + Physical Requirements. - Qualifications: Other Qualifications (basic computer skills, attention to detail, self motivated, ability to interpret direction, flexible to work overtime/nights/shifts/weekends, flexible to multiple areas, demonstrated competencies list, equipment, lift, PPE). Actually that includes many things; maybe too broad. - Skills: (maybe we can skip if Qualifications already covers). But we need to avoid thin sections. If we put all other qualifications under Qualifications, Skills may be thin. Could instead put demonstrated competencies under Skills, and the rest under Qualifications. Thus: - Qualifications: Education/Experience Qualifications (HS diploma/GED preferred, 1+ years experience, 18+). - Skills: Other Qualifications (basic computer skills, attention to detail, self motivated, ability to interpret direction, flexible to work overtime/nights/shifts/weekends, flexible to multiple areas, demonstrated competencies list, equipment, lift, PPE). - Benefits: Benefits package. - Pay: Salary Range. - Schedule: Travel Requirements? Actually schedule is about shift flexibility; we already have flexible to work overtime etc under Skills. So maybe Schedule is not needed. But we could put Travel Requirements under Schedule? Not appropriate. We could decide to omit Schedule heading because no specific schedule info beyond what's already covered. The instruction: "Prefer a few substantive sections over many thin ones." So we can omit Schedule if not substantive. Similarly, we might omit Qualifications if we combine education/experience into Requirements. But we have both headings allowed; we can choose to use only those with content. Let's see if we can make a good set: - About the role: Purpose Statement. - Responsibilities: Key Job Accountabilities. - Requirements: Education/Experience Qualifications + Physical Requirements + Travel Requirements. - Skills: Other Qualifications (including computer skills, attention to detail, self motivated, ability to interpret direction, flexible to work overtime/nights/shifts/weekends, flexible to multiple areas, demonstrated competencies list, equipment, lift, PPE). - Benefits: Benefits package. - Pay: Salary Range. That's 6 sections. No Schedule. Check each for substantive content. Now we need to format. Use

for each heading. Under each heading, we need

for prose,

• for lists. We need to preserve all substantive information; do not invent or summarize away detail. We must remove boilerplate: EEO, accommodation request, contract disclaimer, equal opportunity, drug screen background check (maybe borderline but could be considered boilerplate; but it's about hiring contingency; could be considered minor metadata; we can drop). Also remove "Visit Plexus.com to learn more..." maybe that's about us; but it's part of About us description; we can keep some but maybe it's generic; but it's still substantive about company vision. We'll keep the About us paragraph but maybe trim the link? The instruction: preserve ALL substantive information; do not invent or summarize away detail. The link is substantive? It's a reference; we could keep as plain text. But we might drop the link as it's just a URL; but it's still info