Maintenance Professional

We need to output HTML fragment with sections: About the role (but we shouldn't repeat job title; we can have heading "About the Role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include headings for sections that have content. The posting includes "About the Role" paragraph, then "What You’ll Do" (responsibilities), then "What We’re Looking For" (skills/experience), then "Required Qualifications", "Preferred Qualifications", "Schedule", "Compensation", "Benefits", "Additional Details", "About the Company". We need to decide which sections to include. We must not repeat job title as heading. We can include headings: About the Role, Responsibilities, Requirements (maybe combine skills?), Qualifications (maybe separate required and preferred?), Skills, Benefits, Pay, Schedule. But we must only include sections when posting has real specific content. We need to avoid filler like "commensurate with experience". Not present. We need to extract content. Let's parse: About the Role: "We’re looking for skilled Maintenance Professional to keep our production and facility equipment running at peak performance. In this role, you’ll troubleshoot, repair, and maintain mechanical, electrical, pneumatic, and hydraulic systems to ensure smooth operations and zero downtime." What You’ll Do (list): - Install, maintain, and repair food processing and production equipment. - Diagnose and fix mechanical, electrical, pneumatic, and hydraulic issues. - Read and interpret manuals and work orders to complete service tasks. - Perform routine plant inspections and address potential issues proactively. - Respond quickly to maintenance calls to keep production moving. - Maintain utility systems to prevent downtime. - Keep accurate records for safety, quality, and compliance. - Follow all safety rules, PPE requirements, and food safety standards. - Participate in required safety and quality training. - Identify opportunities for continuous improvement. What We’re Looking For (list?): - Experience: Hands-on maintenance experience in a manufacturing or industrial setting. - Skills: Strong mechanical and electrical troubleshooting skills; ability to work with pneumatic and hydraulic systems. - Tech Savvy: Basic computer skills for work orders and documentation. - Problem Solver: Ability to think on your feet and resolve issues quickly. - Team Player: Good communication and time management skills. Required Qualifications: - Associate degree in a related technical discipline or an equivalent combination of education and maintenance experience. - Proven mechanical aptitude with the ability to troubleshoot and repair equipment. Preferred Qualifications: - Knowledge of ammonia refrigeration systems. - Welding experience. - Bilingual (English/Spanish). Schedule: - Day shifts starting at 5 AM on a modified 4-1-2 scheduled rotation - Work every 3rd Weekend Compensation: - Starting base pay range: $24.95-$31.18 per hour, based on education, experience, and qualifications. - Up to 14% additional pay for night shift - Double-time pay for Sundays and Holidays Benefits: - 401(k) with up to 5% company contribution - Profit sharing plan - Paid time off (PTO) - Competitive insurance benefits Additional Details: - Work Environment: Shop and plant setting with exposure to moving parts, vibration, temperature changes, and loud noise. - Travel: Less than 5%. - Other Requirements: High school diploma/GED, valid driver’s license, minimum age 18. About the Company: description. We need to decide which sections to output. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine some. For example, we could have sections: About the Role, Responsibilities, Qualifications (including required and preferred), Skills (maybe part of What We’re Looking For), Benefits, Pay, Schedule. But we need to avoid duplication. We could structure:

About the Role

We’re looking for skilled Maintenance Professional to keep our production and facility equipment running at peak performance. In this role, you’ll troubleshoot, repair, and maintain mechanical, electrical, pneumatic, and hydraulic systems to ensure smooth operations and zero downtime.

Responsibilities

• Install, maintain, and repair food processing and production equipment.
• Diagnose and fix mechanical, electrical, pneumatic, and hydraulic issues.
• Read and interpret manuals and work orders to complete service tasks.
• Perform routine plant inspections and address potential issues proactively.
• Respond quickly to maintenance calls to keep production moving.
• Maintain utility systems to prevent downtime.
• Keep accurate records for safety, quality, and compliance.
• Follow all safety rules, PPE requirements, and food safety standards.
• Participate in required safety and quality training.
• Identify opportunities for continuous improvement.

Qualifications

We could split required and preferred maybe as subheadings? But instruction only says use

for section headings; we could have nested

? Not specified. Safer to keep only

headings. Could combine required and preferred into one list with labels? Might be okay. We could do:

Required Qualifications

• Associate degree in a related technical discipline or an equivalent combination of education and maintenance experience.
• Proven mechanical aptitude with the ability to troubleshoot and repair equipment.

Preferred Qualifications

• Knowledge of ammonia refrigeration systems.
• Welding experience.
• Bilingual (English/Spanish).

But that adds more sections; still okay if substantive. Skills: The "What We’re Looking For" includes experience, skills, tech savvy, problem solver, team player. Could be a section "Skills and Experience". Might be redundant with qualifications. Could combine. Given "Prefer a few substantive sections over many thin ones", maybe we combine "What We’re Looking For" into a section called "Skills and Experience". Then we have Required Qualifications and Preferred Qualifications separate? That's still many. Alternative: Have sections: About the Role, Responsibilities, Requirements (combining experience/skills/qualifications), Benefits, Pay, Schedule. But we need to preserve all substantive info. If we combine, we must not lose detail. We could have a section "Requirements" with subpoints: Experience, Skills, Tech Savvy, Problem Solver, Team Player, Required Qualifications, Preferred Qualifications. That's a lot but still one section. But the instruction says use

• for any list of duties/requirements/benefits. So we can have a
  under Requirements containing all those items. Thus we could have:

  About the Role

  ...

  Responsibilities

  ...

  Requirements

  • Experience: Hands-on maintenance experience in a manufacturing or industrial setting.
  • Skills: Strong mechanical and electrical troubleshooting skills; ability to work with pneumatic and hydraulic systems.
  • Tech Savvy: Basic computer skills for work orders and documentation.
  • Problem Solver: Ability to think on your feet and resolve issues quickly.
  • Team Player: Good communication and time management skills.
  • Required Qualifications: Associate degree in a related technical discipline or an equivalent combination of education and maintenance experience; proven mechanical aptitude with the ability to troubleshoot and repair equipment.
  • Preferred Qualifications: Knowledge of ammonia refrigeration systems; welding experience; bilingual (English/Spanish).
  But we need to keep the detail; we can split each bullet. Better to keep each as separate
  • . That is fine. Then Benefits, Pay, Schedule. We also have Additional Details (Work Environment, Travel, Other Requirements). Could be part of Requirements or a separate section "Additional Details". Might be okay to include as its own section. But "Prefer a few substantive sections over many thin ones" suggests we might combine Additional Details into Requirements or maybe into About the Role? However, they are substantive: work environment, travel, other requirements (HS diploma/GED, driver's license, age 18). Could be part of Requirements. Thus we could add those to Requirements list. Thus final sections: About the Role, Responsibilities, Requirements, Benefits, Pay, Schedule. We must not include sections with filler like "commensurate with experience". Not present. Now we need to output HTML fragment only. Let's craft. Check for any boilerplate: The posting includes "About the Company" and a call to apply. We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About the Company" is not boilerplate; it's substantive about the company. Should we include? The instruction says we can include sections only when posting has real specific content. About the Company is specific content. Should we include a section? The list of suggested headings didn't include "About the Company". But we could still include a heading? The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exhaustive. It says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are typical sections; we could still add other headings if needed, but maybe better to stick to those. However, About the Company is substantive; we could include it as a section maybe with heading "About the Company". The instruction didn't forbid other headings, just gave examples. It says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use

    for any section heading, but we should follow that pattern. So we could add

    About the Company

    . But we need to decide if we want to include it. The instruction: "Prefer a few substantive sections over many thin ones." Adding About the Company adds another section. Might be okay if it's substantive. However, the job posting already includes it; we should preserve ALL substantive information. So we need to include it somewhere. Could we fold it into About the Role? Not appropriate. Could we add a section "About the Company". That seems fine. Thus sections: About the Role, Responsibilities, Requirements, Benefits, Pay, Schedule, About the Company. But we might combine About the Company into a paragraph without heading? The instruction says use

    for section headings. If we don't give it a heading, it's just a

    after previous section. That's okay; we can just put a

    about company after the last section without a heading. But then it's not a section heading; it's just prose. That might be acceptable. However, the instruction says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we must use headings for all sections, but we should for section headings. If we treat About the Company as a section, we should give it a heading. But we could also treat it as part of the "About the Role" or just a paragraph after. I'd lean to give it a heading to keep structure. Thus final HTML:

    About the Role

    We’re looking for skilled Maintenance Professional to keep our production and facility equipment running at peak performance. In this role, you’ll troubleshoot, repair, and maintain mechanical, electrical, pneumatic, and hydraulic systems to ensure smooth operations and zero downtime