Facilities Technician

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the posting. Given posting: - Intro: "We are a fast-paced business..." Not a heading. - Job title: "Facilities Technician Chatsworth - California, USA | Regular, Full-Time | 9/80 Work Schedule $22-$29/hour, based on experience". We should not repeat job title as heading. - About Ontic Chatsworth: description. - The opportunity: description. - What you'll be doing: list of duties. - What you'll bring: list of requirements/qualifications/skills. - Why Ontic?: description. - Benefits at Ontic: list of benefits. - Compensation Pay Range: $22-$29/hour, based on experience. - Also mention 9/80 work schedule earlier. We need sections: About the role (maybe combine About Ontic Chatsworth + The opportunity?), Responsibilities (What you'll be doing), Requirements (What you'll bring), Qualifications (maybe same as Requirements?), Skills (maybe part of what you'll bring), Benefits, Pay, Schedule. We must not create sections with filler. So we need actual content. Let's extract: About the role: Could be "About Ontic Chatsworth" + "The opportunity". That's substantive. Responsibilities: "What you'll be doing" bullet list. Requirements: "What you'll bring" bullet list (experience, knowledge, etc.) Qualifications: maybe same as Requirements? Could combine but we need separate only if distinct content. The posting doesn't have separate qualifications beyond what you'll bring. So we might not create Qualifications section if it would duplicate. Better to have one section for Requirements/Qualifications/Skills combined? But rules: use headings for each of those if content exists. We could split: Requirements (experience), Skills (knowledge, abilities), Qualifications (maybe education? not present). Since no explicit qualifications, we might omit Qualifications heading. Skills: could be part of what you'll bring (knowledge of building systems, etc.) but we could make a Skills section from that list. Better: Have sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. Check each for content: About the role: combine "About Ontic Chatsworth" paragraph and "The opportunity" paragraph. Responsibilities: bullet list from "What you'll be doing". Requirements: bullet list from "What you'll bring" that are experience/knowledge? Actually "What you'll bring" includes previous experience, knowledge, understanding, confidence, ability, strong communication, experience with contractors. That's more like requirements/qualifications. We'll put that as Requirements. Skills: maybe we could extract specific skills like "using tools safely", "prioritise workload", "communication". But that overlaps. Could instead make Skills section from "What you'll bring" items that are skills: confidence carrying out manual tasks, using tools safely, ability to prioritise workload, strong communication and interpersonal skills, experience working with external contractors, using facilities management systems. But that's still similar. Alternatively, we could combine Requirements and Skills into one section, but rules say prefer few substantive sections over many thin ones. So maybe we just have About the role, Responsibilities, Requirements (which includes experience, knowledge, skills), Benefits, Pay, Schedule. Thus we avoid thin sections. Now Benefits: list from "Benefits at Ontic". Need to preserve all substantive info: Goal Share bonus program, Paid volunteering time, 24/7 wellbeing support, Employee discounts, Learning and development, Employee referral program, Comprehensive medical insurance, Competitive PTO, holiday pay and sick leave, 401(k) plan with up to 4% company match, 9/80 work schedule - where applicable. Pay: "$22-$29/hour, based on experience". Also note earlier mention of $22-$29/hour. Schedule: "9/80 Work Schedule" mentioned in job title line and also in benefits. So we can have Schedule section with that. We must not repeat job title as heading. Also must not include metadata like Job ID etc. There's none. We must remove boilerplate: EEO, export control compliance, privacy act, etc. Also remove "Please click here to review Ontic's California Consumer Privacy Act policy." and the EEO paragraph and export control compliance. Also remove "Ready to embrace the challenge? If this sounds like the kind of opportunity where you could make an impact, we'd love to hear from you. Apply today and see where a career with Team Ontic could take you." That's application instructions, remove. Also remove "Why Ontic?" maybe we could incorporate into About the role? But it's separate motivational content. Could be its own section? But we have no heading for "Why Ontic?" Not in list of allowed headings. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not create a heading for "Why Ontic?" We could fold that content into About the role or maybe omit? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the "Why Ontic?" content somewhere. Since we cannot create a heading not in allowed list, we could incorporate it into a paragraph under About the role or maybe under Benefits? But it's not about benefits. Better to add a paragraph under About the role after the existing description. That would preserve info. Thus About the role section will contain: description of Ontic Chatsworth, the opportunity, and Why Ontic? (the motivational paragraph). All as prose (

). Now Responsibilities: list from "What you'll be doing". Use

• . Requirements: list from "What you'll bring". Use
  • . Benefits: list from "Benefits at Ontic". Use
    • . Pay:

      $22-$29/hour, based on experience

      Schedule:

      9/80 work schedule

      (maybe mention where applicable). Keep as is. Now ensure we don't include filler like "based on experience" is okay. Now produce HTML fragment: no or . Just the sections. Order: About the role (

      About the role

      ), then

      ... paragraphs combined maybe multiple

      tags allowed? The rule: use

      for prose. Could have multiple

      inside section. We'll put multiple

      for each paragraph. Now craft content. About Ontic Chatsworth paragraph: "Our 114,000 sq ft Chatsworth facility in Los Angeles specializes in electronic and electro-mechanical aerospace products, supporting critical systems including airborne radar, cabin and cockpit lighting, flight controls, engine and environmental controls and pilot controls. Behind those products is a team solving complex technical and operational challenges every day. With specialist manufacturing and testing capabilities on site, Chatsworth combines decades of aerospace expertise with the opportunity to keep improving how we deliver for our customers. Join the team and your work will contribute directly to the reliability and availability of systems used across civil and military aviation around the world." The opportunity paragraph: "As a Facilities Technician at Ontic, you'll play a hands-on role in keeping our Chatsworth site safe, operational and ready to support the teams delivering critical aerospace products. You'll support both planned and reactive maintenance across the facility, helping to resolve issues quickly, maintain building systems and equipment, and identify opportunities to improve the working environment. You'll have the opportunity to take ownership of day-to-day facilities needs while working closely with external contractors and teams across the site. This is an opportunity for someone who enjoys variety, takes pride in solving practical problems and can work independently in a fast-paced environment where keeping operations running matters." Why Ontic? paragraph: "At Ontic, we're specialists in keeping critical aircraft flying. Our work supports civil and military aviation around the world, giving established aircraft products the long-term support they need to remain safe, reliable and available. But it's our people who make that possible. We're a growing, global team where you're trusted to take ownership, encouraged to challenge how things have always been done and supported to develop your career as our business grows. We believe in embracing the challenge - working together to solve complex problems and create opportunities for our customers, our business and each other." Now Responsibilities list items: - Carry out routine and reactive maintenance across building systems, equipment and infrastructure, including lighting, plumbing and HVAC. - Support planned preventative maintenance schedules and maintain accurate records of completed work. - Coordinate and monitor external contractors and service providers, helping ensure work is completed safely and to Ontic standards. - Conduct regular site inspections, identifying and reporting issues and opportunities for improvement. - Respond to facilities requests and resolve issues in a timely manner using helpdesk or ticketing systems. - Support health and safety compliance activities, including fire alarm testing, emergency lighting and equipment checks. - Help maintain a safe, clean and efficient working environment, including supporting office moves, equipment setup and consumable stock management. Now Requirements list items (from What you'll bring): - Previous experience in a facilities or maintenance technician role within a commercial or industrial environment. - Knowledge of building systems and general maintenance activities, including electrical, mechanical and plumbing. - A good understanding of health and safety procedures and compliance requirements. - Confidence carrying out manual tasks, using tools safely and working both indoors and outdoors. - The ability to prioritise your workload and respond quickly to changing needs in a fast-paced environment. - Strong communication and interpersonal skills. - Experience working with external contractors or vendors and using facilities or maintenance management systems to log and track work would be advantageous. Now Benefits list items: - Goal Share bonus program - everyone at Ontic is automatically enrolled, giving us all the opportunity to share in our success - Paid volunteering time - giving you time to support a cause or community that matters to you - 24/7 wellbeing support - confidential support available through our Employee Assistance Program (EAP) - Employee discounts - access to discounts and offers across a range of retailers and services - Learning and development - opportunities to build your skills, develop your career and grow with Ontic - Employee referral program - rewarding you for introducing great people to Team Ontic - Comprehensive medical insurance - Competitive PTO, holiday pay and sick leave - 401(k) plan - with up to 4% company match - 9/80 work schedule - where applicable Now Pay:

      $22-$29/hour, based on experience

      Schedule: maybe we already have schedule in benefits; but we need a Schedule section if posting states it. It does state 9/80 work schedule in job title line and also in benefits. So we should include Schedule section with that info. Could be

      9/80 work schedule

      . But we already have it in benefits; duplication is okay? The rule: Preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is not prohibited but we might avoid duplication. However we need a Schedule section; we can put the schedule info there, and we could optionally remove it from benefits to avoid duplication, but we must preserve all substantive info; removing it from benefits would lose that info. So we keep it in benefits and also have Schedule section? That would duplicate. The instruction: "Prefer a few substantive sections over many thin ones." Duplication might be considered thin? Not sure. Better to keep schedule only in Benefits section and not create a separate Schedule section, because the schedule is already covered under Benefits. But the rule says: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state schedule, so we could create a Schedule section. But we must preserve all substantive info; we could keep schedule in both places but that's duplication but still preserving. However duplication might be considered unnecessary but not prohibited. I'd rather keep schedule in Benefits and not create a separate Schedule section to avoid thin section