Maintenance Technician - Night Shift

We need to output HTML fragment with sections: About the role? The description includes "Your Mission" and "Explore The Depth Of The Role". We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include a section only when posting has real, specific content. We need to parse content. We have description: "Built on Experience..." intro. Then "Your Mission As a Maintenance Technician..." then "Explore The Depth Of The Role" list of duties. Then "Requirements Mission Readiness: ..." includes requirements. Then "Travel Requirements", "Physical Requirements". Then "Become a part of our Builders and you too can..." list of values? Then "What Keel Will Build For You" list of benefits: Comprehensive Benefit Package, Competitive Pay, 401(k) Match, HSA/FSA, Paid Holidays, Paid Time Off, Internal Referral Bonus Opportunities, Shift Differentials, Overtime Potential, Paid on the Job Training, Certification Sponsorship Opportunities, Committed to Individual Career Growth, We Do Fun Things, Plus More! Also schedule: "Night Shift: Monday - Thursday, 4:15 pm to 4:45 am". So we have schedule info. Pay: Not explicit amount, just "Competitive Pay". That's vague; we should not create Pay section unless posting actually states them. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It says "Competitive Pay" is stated, but it's not a specific number. Is that considered stating? It says "Competitive Pay" as a benefit. The rule says: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It also says: "Prefer a few substantive sections over many thin ones." And "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". "Competitive Pay" is vague but not placeholder like TBD. It's a statement that pay is competitive. Might be considered real content? It's not a specific number but it's a statement. The rule about placeholder text includes "commensurate with experience", "not specified", "N/A", "varies", "TBD". "Competitive Pay" is not those. So we could include a Pay section with that statement. However, they said "Prefer a few substantive sections over many thin ones." Might be better to combine Benefits and Pay? But they want separate headings for Benefits, Pay, Schedule. We have schedule specifics. We have benefits list. We have pay statement. Thus we can include sections: About the role (maybe from intro?), Responsibilities (duties), Requirements (including mission readiness, travel, physical), Benefits, Pay, Schedule. We must not repeat job title as heading. The page already shows it, so we don't add a heading for "Maintenance Technician". Use

for each section heading. We need to use

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

  for prose. We must preserve all substantive information; do not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At end there is "Need Assistance? ..." and "Equal Opportunity Employer ..." and "What we build, builds us." Those are boilerplate/EEO; we should remove them. Also "Become a part of our Builders and you too can..." list of values maybe not boilerplate but could be considered part of culture; but it's not a standard heading; we could treat as part of "About the role" or maybe omit as it's fluff? It's substantive? It's values; maybe we can keep as part of About the role. But we need to decide. We need to include all substantive information: intro about Keel, mission, duties, requirements, travel, physical, benefits, pay, schedule. Also the "Become a part of our Builders and you too can..." list (Uphold Safety..., etc.) could be considered part of culture/values; we could include as a section maybe "Values" but not in allowed headings. Since only allowed headings are those listed, we should not create other headings. So we could incorporate that list into "About the role" as prose or maybe as a

  under About the role? But the rule says use
  • for any list of duties/requirements/benefits. This list is not duties/requirements/benefits; it's values. Could still be a list but not specified. Safer to put as

    prose. We must not include duplicated lines. Ensure we don't repeat. Let's extract content: Intro: "Built on Experience. Built for Skill. Built for You. Keel was formed by bringing together three industry leaders combining generations of hands-on expertise in steel fabrication, shipbuilding, aerospace, and defense manufacturing. That means when you join Keel, you’re joining a team backed by decades of proven craftsmanship and real-world results. We build ships, defense systems, aerospace components, and heavy steel structures that serve critical missions — and we do it with pride." Your Mission: "As a Maintenance Technician for Keel Midwest, you will be responsible for repairing and maintaining machinery and equipment such as engines, motors, pneumatic tools, conveyor systems, and production machines and equipment." Explore The Depth Of The Role: list of duties: - Maintain, clean, lubricate, repair and perform preventive maintenance to production machinery. - Cleans up and ensures equipment is ready for production. - Troubleshoot electrical, hydraulic, pneumatic and mechanical systems. - Maintains fixtures/equipment to minimize downtime. - Diagnose repair issues. - Maintains physical structure of fixtures and equipment. - Dismantles devices to gain access to and remove defective parts. - Repairs or replaces defective parts. - Operates cutting torch to cut metal parts. - Repairs or replaces gauges, valves, pressure regulators, and related equipment. - Maintains facility's utilities/support equipment: air, water, drain, steam, hydraulic, electric, etc. - Ensure personal safety and the safety of team members; understand how machines work and how to operate them safely; knowledge of emergency stops; and utilization of personal protective equipment. - Maintain clean work environment. - Perform routine cleaning of equipment and general housekeeping at and around maintenance shop. - Collects and handles solid and hazardous waste generated at the work site and deposits separately in designated containers. - All other duties as assigned. Requirements Mission Readiness: "High school diploma or GED required, and five (5) years maintenance technician experience required." Then list: - Ability to utilize hand-held tools/machinery/instruments, both manual and powered, both precision and non-precision. - Perform basic maintenance tasks, such as plumbing, painting, greasing, oiling, grinding, drilling, disassembling and reassemble simple machine parts. - Ability to weld and cut with gas torches, troubleshoot machine controls. - Ability to follow maintenance procedures and maintain proper documentation, drawings and files. - Knowledgeable in hydraulic, electrical and pneumatic controls, materials and components. - Ability to operate, set, and regulate/adjust machinery. - Ability to troubleshoot machine controls, disassemble and assemble machine parts. - Ability to install conduit, pipe, regulators, and hoses - Knowledgeable in PLC and computer controls, relay ladder logic, and electronic controls preferred. - Must be able to lift a minimum of 50lbs and maneuver 200lbs without assistance. - Ability to take oral direction - Ability to work in a team environment successfully Travel Requirements: "Occasional travel between facilities and customer sites as needed." Physical Requirements: "May be required to stand, walk, sit, reach/pull/push with hands and arms, climb or balance, stoop or kneel regularly. May lift or carry 50lbs. Weights exceeding 50lbs will require mechanical means to maneuver." Then "Become a part of our Builders and you too can..." list: - Uphold Safety and Quality Standards - Embody Team Spirit - Relentless Customer Focus - Convey Integrity, Trust, and Professionalism - Execute with Excellence and Velocity Then "What Keel Will Build For You" list: - Comprehensive Benefit Package - Competitive Pay - 401(k) Match - HSA/FSA - Paid Holidays - Paid Time Off - Internal Referral Bonus Opportunities - Shift Differentials - Overtime Potential - Paid on the Job Training - Certification Sponsorship Opportunities - Committed to Individual Career Growth - We Do Fun Things, Plus More! Schedule: "Night Shift: Monday - Thursday, 4:15 pm to 4:45 am" Pay: "Competitive Pay" (already in benefits list). Might duplicate. We could treat Pay section as just that statement, but it's already in benefits list. To avoid duplication, we could keep Pay section with that statement and not duplicate in Benefits. But the benefits list includes Competitive Pay as an item. If we separate, we might duplicate. Better to keep Benefits section include all items except maybe Competitive Pay, and Pay section just says Competitive Pay. But that repeats the phrase. Could we omit Pay section and just include Competitive Pay within Benefits? The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state Competitive Pay, so we could have a Pay section with that statement. But then Benefits section would not include Competitive Pay. However the benefits list includes it; we could keep it in Benefits and not have a separate Pay section. But then we would not have a Pay section despite the posting stating it. The rule says we should not create Pay section unless posting actually states them. It does state them, so we could create it. But we also need to avoid duplication. We could decide to not duplicate: put Competitive Pay only in Pay section, and omit from Benefits list. However the benefits list originally includes it; removing it might be considered omitting substantive information. The rule says preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep the Competitive Pay statement somewhere. If we put it in Pay section and also keep it in Benefits list, that's duplication. Duplication is to be removed: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should not duplicate lines. So we need to decide where to place Competitive Pay without duplication. Perhaps we can keep it in Benefits list and not have a separate Pay section, but then we are not creating a Pay section despite the posting stating it. The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does not say we must create them if they are stated; it says we should not create them unless the posting actually states them. So we can optionally create them if we want, but we must not create them if not stated. It's not mandatory to create them. So we can skip Pay section and keep Competitive Pay within Benefits. That satisfies not creating a Pay section unless we have specific content; we have content but we choose not to make a separate section. That's allowed? The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It doesn't say we must create them when they are stated. So we can omit Pay section. Similarly for Schedule: we have schedule specifics, we could create a Schedule section. It's optional but we likely should include because it's specific. The rule says prefer a few substantive sections over many thin ones. Having a Schedule section with just one line might be thin but it's specific. Could combine Schedule into About the role? But schedule is distinct