Material Handler

The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and apply the rules. First, I need to identify the sections. The posting has: - "What We Offer" - this seems like a benefits/company culture section - "Group Summary" - company background - "Job Responsibilities" - with "SUMMARY OF RESPONSIBILITY" and then a list of required skills/qualifications - "Required Skills & Qualifications" - a long list of bullet points - "Preferred Skills" - another list - Some boilerplate at the end (EEO, privacy, AI disclosure, worker type, group) Rules: - Use

for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) - Use

• for lists,

  for prose - Do NOT repeat job title as heading (not provided anyway) - Do NOT put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/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 sections unless posting actually states them - Output ONLY HTML fragment, no /, no markdown code fences Now, let's map the content to appropriate sections. The posting doesn't have explicit "About the role" but has "SUMMARY OF RESPONSIBILITY" which is a prose paragraph. That could be "About the role" or "Responsibilities". The "Required Skills & Qualifications" is a list of duties/requirements. "Preferred Skills" is another list. "What We Offer" describes benefits/culture - could be "Benefits" section. "Group Summary" is company background - could be "About the company" but not a standard heading. The allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Group Summary" might fit "About the role" or could be a separate section? The rules say use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says "e.g." so maybe other headings allowed? But better to stick to those. "Group Summary" is about the company, not the role. Could be omitted or folded into "About the role"? But the rule: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." Group Summary is not minor metadata; it's substantive. However, the allowed headings don't include "Company Overview". I could use "About the role" for the summary of responsibility, and maybe "Benefits" for "What We Offer". "Group Summary" could be a

  under "About the role" or separate? The rule: "Prefer a few substantive sections over many thin ones." I'll include "Group Summary" as a section maybe with heading "About the company"? But the allowed headings list doesn't include that. The instruction says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, but we should use those when appropriate. For company description, maybe "About the role" is not appropriate. Could create a heading "Company Overview" but not in the list. However, the rule says "include a section ONLY when the posting has real, specific content for it". The posting has "Group Summary" with real content. I think it's okay to include a heading like "Company Overview" or "About Magna". But to be safe, I'll use "About the role" for the summary of responsibility, and maybe include the group summary as a paragraph under "About the role" or as a separate section with a generic heading? The instruction says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests those. I'll use "About the role" for the summary paragraph, and "Responsibilities" for the list of required skills? Actually "Required Skills & Qualifications" is a list of duties and requirements. That could be "Responsibilities" and "Requirements". But they are mixed. The list includes both duties (move materials, follow FIFO, use RF scanners) and qualifications (wear PPE, follow safety, demonstrate attendance). The "Preferred Skills" is clearly preferred qualifications. I'll structure as: - About the role: the SUMMARY OF RESPONSIBILITY paragraph. - Responsibilities: the list from "Required Skills & Qualifications" (since they are duties) - Requirements: maybe the same list? But the list includes both duties and requirements. The heading "Required Skills & Qualifications" suggests it's both. I could split: Responsibilities for the duty-like items, Requirements for the qualification-like items. But the list is not separated. Better to keep as one section "Responsibilities & Requirements" or "Requirements". The allowed headings include "Responsibilities" and "Requirements". I'll use "Responsibilities" for the list, and maybe "Qualifications" for preferred skills? But "Qualifications" is allowed. "Skills" is also allowed. Let's see: The posting has "Required Skills & Qualifications" and "Preferred Skills". I'll create: - Responsibilities: for the required list (since they are job duties) - Qualifications: for the preferred skills? But preferred skills are not required qualifications. Could be "Preferred Qualifications". The allowed headings include "Qualifications". I'll use "Qualifications" for preferred skills, and maybe "Requirements" for required? But the required list is labeled "Required Skills & Qualifications". I'll make two sections: "Responsibilities" (for the required list) and "Qualifications" (for preferred skills). However, the required list includes both responsibilities and qualifications. The first part: "Move materials in and out of storage locations" is a responsibility. "Follow first-in, first-out (FIFO) procedures" is a responsibility. "Use radio frequency (RF) scanners" is a responsibility. "Maintain clean, organized, and safe work areas" is a responsibility. "Support production flow by delivering materials on time" responsibility. "Verify, count, label, and stack materials correctly" responsibility. "Take breaks as needed to meet material demands of production" responsibility. "Flex schedule (start/end times) to support shift change needs" responsibility. "Use kanban cards to manage inventory" responsibility. "Communicate respectfully and professionally with team members" responsibility. "Participate in scheduled employee meetings and training" responsibility. "Wear required personal protective equipment (PPE)" requirement. "Follow all health and safety policies and procedures" requirement. "Report hazards and assist with safety inspections" responsibility. "Accurately complete required documentation and paperwork" responsibility. "Demonstrate dependable attendance and a team-oriented attitude" requirement. "Safely operate forklifts, RF scanners, and related equipment (after training/licensing)" requirement. It's mixed. I'll keep as one section "Responsibilities & Requirements" but the allowed headings don't include that. I could use "Responsibilities" and include all, as they are all expected of the role. The heading "Required Skills & Qualifications" is essentially the job requirements. I'll use "Requirements" as heading for that list. And "Preferred Qualifications" for preferred skills. But "Qualifications" is allowed. I'll use "Requirements" for required, "Qualifications" for preferred? But "Qualifications" might be confused. The allowed headings: "Requirements", "Qualifications", "Skills". I'll use "Requirements" for the required list, and "Preferred Qualifications" for preferred skills? But "Preferred Qualifications" not in list. I'll use "Qualifications" for preferred skills, and note they are preferred. Alternatively, I could combine required and preferred under "Requirements" with sub-lists? But the rule: use

  • for any list. Could have two lists under same heading with subheadings? But only

    for section headings. Could use

    ? Not specified. Better to have separate sections. Let's decide on sections: 1. About the role: the summary paragraph. 2. What We Offer (Benefits): the "What We Offer" paragraph. 3. Group Summary: maybe "Company Overview" but not in allowed. Could include as a paragraph under "About the role" or separate. I'll include as a separate section with heading "Company Overview" but the instruction says use

    for section headings (e.g. ...). It doesn't forbid other headings. I'll use "Company Overview" as

    . 4. Responsibilities: the required list? Or "Requirements". I'll use "Requirements" for the required list. 5. Preferred Qualifications: for preferred skills. But the rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states "What We Offer" which describes benefits/culture. So "Benefits" section is appropriate. Also, there is "Flex schedule (start/end times) to support shift change needs" in the required list, but no explicit schedule section. The posting doesn't state pay or schedule details beyond that. So no Pay/Schedule sections. Now, boilerplate to remove: EEO statement, privacy, AI disclosure, worker type, group. Those are at the end. Remove them. Also, the line "The above statement reflects the general details considered necessary to describe the principal functions of the job identified and shall not be considered as a detailed description of the work required inherent in the job. Other duties may be assigned from time to time to support business needs." This is a disclaimer, could be considered boilerplate. But it's part of the job description. Might keep as a paragraph under Requirements? Or drop. The rule: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." This disclaimer is legal boilerplate. I'll drop it. Now, let's write HTML. Sections:

    About the role

    SUMMARY OF RESPONSIBILITY ...

    Benefits

    What We Offer ...

    Company Overview

    Group Summary ...

    Requirements

    • Move materials in and out of storage locations
    ... all items from Required Skills & Qualifications

    Preferred Qualifications

    • Experience with kanban/Heijunka systems
    ... all items from Preferred Skills
    But "Preferred Qualifications" not in example headings. Could use "Qualifications" but that might imply required. The example includes "Qualifications". I'll use "Qualifications" for preferred, but note they are preferred. Or use "Skills" for preferred skills. The example includes "Skills". I'll use "Preferred Skills" as heading? But the rule says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). "Skills" is allowed. So I can use "Skills" for preferred skills. But the required list also includes skills. Hmm. Better: "Requirements" for required list, "Preferred Skills" for preferred list. But "Preferred Skills" not in example. However, the example is not exhaustive. I'll use "Preferred Skills" as