Maintenance Technician - Weekend Shift - $1,000 Sign On Bonus

We need to output only HTML fragment, no html/body tags, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job posting. First, we have "About McNeilus, An Oshkosh Company ..." This is about the company. Could be "About the role"? Actually "About McNeilus" is about company. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" heading, but the content about the company may be considered "About the role"? The posting includes a paragraph about McNeilus. That's not about the role but about the company. However we can still put under "About the role" maybe? The instruction says "About the role" is an example heading; we can use that heading for a description of the role/company. Probably we should include a section "About the role" with the role" containing the McNeilus description and Job Summary. But we also have "Job Summary" paragraph: "The Facility Maintenance Technician is responsible for a wide variety of maintenance work on production equipment, industrial type heavy machinery, factory vehicles, and the overall facility. The employee must be able to troubleshoot electrical, plumbing, hydraulic, HVAC and mechanical problems." That's part of role description. We also have "Your Impact" bullet list of duties. Those are responsibilities. We have "Minimum Qualifications", "Standout Qualifications", "Core Competencies", "Working Conditions" (Physical Demands etc). Also "Pay Range: $20 - $28.34 $4 Shift Differential (Weekend Shift Only)". That's pay info. We have "Work Schedule: Routine shift hours. Infrequent overtime, weekend, or shift rotation." That's schedule. We have benefits? Not explicit. No benefits listed. So we should not create Benefits section. We have "Skills"? Not explicit but maybe core competencies includes skills. Could treat Core Competencies as Skills? But we have a separate Skills heading example. The posting includes "Core Competencies" with internal/external contacts, communication skills, decision-making, complexity, etc. That could be considered Skills. We could put that under Skills heading. Or we could put under Qualifications? The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have: - About the role: company description + Job Summary. - Responsibilities: the bullet list under "Your Impact". Also maybe some duties from Job Summary? But we can include those under Responsibilities. - Requirements: Minimum Qualifications? Could be Requirements. Or we could have Requirements and Qualifications separate. The posting has Minimum Qualifications and Standout Qualifications. Could treat Minimum Qualifications as Requirements, Standout Qualifications as Qualifications (or vice versa). We'll need to decide. - Skills: Core Competencies (communication, decision-making, etc). Could also include technical skills like forklift certification, welding, etc. Those are in Standout Qualifications. But we can keep Skills as Core Competencies. - Pay: Pay Range line. - Schedule: Work Schedule line. We must not include sections with placeholder or vague content like "commensurate with experience". Not present. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format them as lists or paragraphs. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At the end there is a lot of EEO statement, accommodation, etc. Those are boilerplate; we should remove them. Also the Oshkosh commitment statements about accommodations, equal opportunity, etc. Remove. Also remove duplicated lines? Not seeing duplicates. We must not include Job ID/requisition numbers as headings; none present. We must not repeat the job title as a heading. The job title is Facility Maintenance Technician; we should not put that as heading. Now produce HTML fragment. Structure:

About the role

McNeilus Truck and Manufacturing Inc. is committed to serving everyday heroes and is an industry leading designer and manufacturer of refuse truck bodies. McNeilus produces a complete line of high-performance rear load, front load, and automated side load refuse bodies to augment any refuse collection fleet. Our team members are critical in our mission of supporting waste warriors and keeping communities safe and clean.

The Facility Maintenance Technician is responsible for a wide variety of maintenance work on production equipment, industrial type heavy machinery, factory vehicles, and the overall facility. The employee must be able to troubleshoot electrical, plumbing, hydraulic, HVAC and mechanical problems.

Then Responsibilities:

Responsibilities

• Check and review work orders and complete tasks on a priority basis.
• Inspect and troubleshoot electrical, plumbing, hydraulic and mechanical problems.
• Replace and/or repair worn-out, broken, and damaged components, equipment, and parts.
• Operate a crane/hoist for heavy lifting.
• Operate and repair forklift, tow motor, tractors, and other facility vehicles safely.
• Handle wires and hardware.
• Report repair statuses to department supervisors.
• Communicate using handheld radios with other maintenance personnel.
• Assist co-workers with heavy lifting of parts.
• Complete all the assigned PM’s for the production equipment on time and safely.
• Enter data into computer program as needed.
• Assist in training new employees.

Then Requirements (Minimum Qualifications):

Requirements

• Six (6) months of applicable position experience or an evaluated equivalent.
• Forklift Certified.

Then Qualifications (Standout Qualifications):

Qualifications

• Associate degree in Electromechanical Technology or equivalent.
• Non-Licensed Maintenance Electrical license.
• Knowledge in welding, metal fabrication, and/or technical equipment.

Then Skills (Core Competencies):

Skills

• Internal Contacts: Contact with peers and others involving explanation of information (these contacts may be within or outside department or division), and the gathering of factual information; may include the communication of sensitive or confidential information.
• External Contacts: Limited external contact to: gather information, answer queries, or ask assistance.
• Communication Skills: Read, write and comprehend simple instructions, short correspondence and memos. Read and interpret safety rules, operating/maintenance instructions and procedure manuals. Read, analyze and interpret business manuals, technical procedures and/or government regulations.
• Decision-Making: Requires minimal decision-making responsibility.
• Complexity, Judgment and Problem Solving: Work of a relatively routine nature. Requires the ability to understand the follow instructions.

But we also have Physical Demands, Working Conditions etc. Those could be part of Skills? Or maybe we could add a "Working Conditions" section but not in the allowed headings list. The allowed headings list includes only those examples; we should not create other headings. So we need to fit Working Conditions somewhere. Perhaps we can include them under Skills as well, or under Responsibilities? But they are not responsibilities. Could be part of "Requirements"? Not exactly. The instruction says "Prefer a few substantive sections over many thin ones." So we could incorporate Working Conditions into Skills or maybe into Qualifications? But they'd be misrepresenting. Alternatively, we could create a section "Working Conditions" but that's not in the allowed list; but 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, not an exhaustive list? It says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It might be implying those are the allowed headings. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Usually they'd want you to use those headings only. It says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we should only use those headings if we have content. If we have content that doesn't fit those headings, maybe we should not create a heading for it, but we still need to preserve all substantive information. Where can we put Working Conditions? Could be part of Skills? Or maybe we can incorporate into Responsibilities? Not ideal. Maybe we can treat Working Conditions as part of "Skills" or "Qualifications"? But the posting includes "Working Conditions Physical Demands: ..." etc. That is substantive. We need to preserve it. Could we put it under a

without a heading? The instruction says we should use headings for sections, but we can have paragraphs outside headings? It says "Use

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

• for any list of duties/requirements/benefits, and

  for prose." It doesn't forbid having paragraphs without a heading, but likely they want sections with headings. However we could have a

  for prose that is not under a heading? The instruction: "Use

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

  • for any list of duties/requirements/benefits, and

    for prose." It doesn't say every piece of content must be under a heading, but they gave examples of headings. Usually they'd want headings for each section. But we could have a

    for the Working Conditions without a heading? That might be considered not following the pattern. However the instruction says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid having a

    without heading. But they'd likely expect each substantive block to be under a heading. However we have limited headings; we could create a section "Working Conditions" but it's not in the examples. The examples are not exhaustive? The phrase "e.g." suggests they are examples, not an exhaustive list. So we could create other headings as needed, as long as they are

    . The instruction: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This could be read as "use h3 for headings, for example these headings". So we can use other headings if needed. But they also say "Prefer a few substantive sections over many thin ones." So we should avoid many small sections. We could combine Working Conditions with Skills or Qualifications. Given the content, we have Physical Demands, Non-Physical Demands, Environmental Demands, Work Schedule, Demands/Deadlines. Work Schedule we already have as Schedule section. Demands/Deadlines maybe could be part of Skills or Responsibilities? It's about occasional stress due to deadlines. Could be part of Skills (maybe under "Complexity, Judgment and Problem Solving"). Physical Demands etc could be placed under Skills as well, but they'd be a bit off. Alternatively, we could create