Quarry Haul Truck Operator

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. No job title heading. No Job ID. Remove boilerplate. Preserve all substantive info. We need to parse the posting. Content: - Opening: "We are currently seeking a skilled and safety-minded Haul Truck Operator to join our Quarry Operations team. The successful candidate will be responsible for the safe and efficient operation of heavy equipment, specifically haul trucks, used in our pit and mining operations. This role is critical to our operations, ensuring the smooth transportation of materials within our facility while adhering to safety standards and operational protocols." That's a prose description; could be under "About the role" heading. Then "Your Mission & Key Responsibilities" then bullet list (actually sentences separated by periods). We'll treat as list items. List items: - Operate heavy equipment, particularly haul trucks, in various sizes and weights, in a safe and effective manner to minimize the risk of injury, property damage, or loss of life. - Conduct daily pre-operational checks and regular maintenance on equipment, ensuring functional safety and readiness for operation. - Identify and report any necessary repairs to supervisors to maintain optimal equipment performance and safety. - Collaborate with other team members and departments to ensure the efficient movement of materials and adherence to production schedules. - Adhere to all workplace safety guidelines and regulations, including the wearing of all required personal protective equipment (PPE). - Participate in safety meetings and training sessions. - Maintain cleanliness of equipment and work area, ensuring compliance with environmental regulations. - Perform additional duties as required or assigned by supervisors, which may include operating other types of heavy machinery or assisting with general labor tasks. Then "What Sets You Apart" list: - High School Diploma or equivalent. - Proven experience operating heavy equipment, preferably in quarry or mining operations. - Strong understanding of operation and maintenance requirements of heavy equipment. - Valid operator's license, with a clean driving record. - Ability to work in a fast-paced, outdoor environment in various weather conditions. - Excellent communication and teamwork skills. - Commitment to safety procedures and practices. - Flexibility to work different shifts, including weekends or holidays as required. - Willingness to undergo SRM’s pre-employment screenings. Then "About SRM" paragraph. Then "Why Join SRM Concrete?" with bullet points: - Growth & Advancement: Be part of a rapidly expanding company that believes in promoting from within. We offer real opportunities for you to build a long-term career and advance your skills, no matter where you start. - Competitive Compensation: Earn industry-leading pay, with overtime opportunities, annual raises, and eligibility for bonuses. Our steady workload ensures reliable income for our team members. - Exceptional Benefits: Take advantage of low-cost medical, dental, vision, short-term and long-term disability, and life insurance. We also offer paid holidays, PTO/vacation, a 401k with a $100 weekly match, family days, and more! - Consistent, Reliable Work: At SRM Concrete, you can count on steady hours and dependable work. We value team members who are dedicated and ready to go the extra mile. - Team Culture: At SRM Concrete, we value hard work, respect, and teamwork. We support each other, recognize a job well done, and believe in doing what’s right—on the job and in the community. You’ll find a straightforward, dependable environment where every team member matters. At SRM Concrete, you’re more than just an employee—you’re a valued team member helping to build America’s future. Then final paragraph: "If you’re ready to say “YES” to new opportunities and deliver service that sets the standard in our industry, apply today and join the SRM family!" This is application instruction, should be removed per instruction: "Remove ... application instructions." So we drop that. Now we need to decide sections. We have: - About the role: could combine opening paragraph and maybe About SRM? Actually "About SRM" is separate. The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content. We have responsibilities list (Your Mission & Key Responsibilities) -> Responsibilities. We have qualifications list (What Sets You Apart) -> could be Requirements or Qualifications. Probably Requirements (education, experience, license). Could also be Qualifications. We'll choose Requirements. We have "About SRM" -> could be About the role? Actually About the role is about the job; About SRM is about company. Could be "About the role" includes the opening paragraph and maybe company description? But we have separate "About SRM" which is company overview. Could be placed under "About the role" or maybe we create a section "About the company"? Not in allowed headings. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put company info under About the role (makes sense). Or we could omit if not fitting. But we must preserve ALL substantive information; we cannot drop About SRM. So we need to include it somewhere. The best fit is About the role (includes role description and company). We'll put opening paragraph + About SRM under About the role. Then Responsibilities as list. Then Requirements as list (What Sets You Apart). Could also split into Requirements and Qualifications but we have only one list; we can put under Requirements. Then Benefits: we have Exceptional Benefits bullet under Why Join SRM Concrete. Also we have Competitive Compensation (pay) and Growth & Advancement (maybe skills?), Team Culture (maybe skills?), Consistent Reliable Work (maybe schedule?). But we need to follow instruction: only create sections when posting has real specific content. We have specific content for Benefits (Exceptional Benefits). We have specific content for Pay (Competitive Compensation). We have maybe Schedule? Not explicitly; there is "Flexibility to work different shifts, including weekends or holidays as required." That's under Requirements (flexibility). Not a schedule section. There's no explicit schedule like "Shift: 8am-5pm". So we should not create Schedule section because no specific schedule info. Skills: we could have a Skills section for communication, teamwork, etc. But those are already in Requirements list. Could we separate? The instruction says prefer a few substantive sections over many thin ones. So we might keep Requirements covering education, experience, license, ability to work, communication, teamwork, commitment to safety, flexibility, willingness to undergo screenings. That's fine. Benefits: we have Exceptional Benefits bullet list. Also we have "Paid holidays, PTO/vacation, a 401k with a $100 weekly match, family days, and more!" That's part of benefits. Pay: we have Competitive Compensation bullet: "Earn industry-leading pay, with overtime opportunities, annual raises, and eligibility for bonuses. Our steady workload ensures reliable income for our team members." Growth & Advancement and Team Culture could be considered Skills or maybe we could add a Skills section for soft skills like communication, teamwork, growth mindset. But we already have communication and teamwork in Requirements. Growth & Advancement is about career development; could be under Benefits? Not exactly. Could be under Skills? Might be thin. The instruction says prefer few substantive sections. So we could incorporate Growth & Advancement and Team Culture into Benefits or maybe into a "Why Join SRM" section but not allowed heading. Could we put them under Benefits as additional bullet points? Benefits heading is for benefits like insurance, PTO, 401k. Growth & Advancement is not a benefit but a career opportunity. Could be under Skills? Not exactly. Could be under Requirements? Not exactly. Could be under About the role? Not exactly. We could create a section "Skills" for communication, teamwork, maybe also growth mindset? But we already have communication and teamwork in Requirements. Might be duplication. Better to keep only sections: About the role, Responsibilities, Requirements, Benefits, Pay. That covers all substantive info. We'll embed Growth & Advancement and Team Culture under Benefits? Might be okay as they are part of "Why Join SRM Concrete" which is essentially benefits/value proposition. The instruction says Benefits section only when posting actually states them. It does state benefits (Exceptional Benefits). It also states Growth & Advancement, Team Culture, Consistent Reliable Work. Those are also part of why join. Could we treat them as Benefits? They are not traditional benefits but still part of value proposition. Might be acceptable to include them under Benefits as additional bullet points. However, we must not invent or summarize away detail; we must preserve all substantive information. So we need to include those points somewhere. If we put them under Benefits, we are not losing detail; we are just grouping them under Benefits heading. That's okay as long as we don't misrepresent them as benefits only; but heading is Benefits, but we can include other items under it. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid mixing other content under those headings. 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 if we put Growth & Advancement under Benefits, we are providing specific content under Benefits heading, which is okay. The heading Benefits is appropriate because we have specific benefits content; we can also add other content under same heading if we want, but we might be stretching semantics. However, we could also create a section "Skills" for communication, teamwork, growth mindset, etc. But we already have communication and teamwork in Requirements; we could move them to Skills to avoid duplication. Let's think. We have many items in What Sets You Apart: HS diploma, experience, understanding, license, ability to work outdoors, communication/teamwork, commitment to safety, flexibility, willingness to undergo screenings. Those are requirements/qualifications. Communication and teamwork could be considered skills. But we can keep them under Requirements. Now we have Benefits: Exceptional Benefits bullet list (medical, dental, vision, disability, life insurance, paid holidays, PTO/vacation, 401k match, family days, etc). Also we have Growth & Advancement, Team Culture, Consistent Reliable Work. Those are not typical benefits but could be considered "Why Join" points. Perhaps we could create a section "Skills" for communication, teamwork, growth mindset? But growth & advancement is not a skill. Team culture is not a skill. Consistent reliable work is not a skill. Maybe we should create a section "About the role" that includes company overview and maybe the value proposition (Growth, Team Culture, Consistent work). Then Benefits section only for benefits. Pay section for compensation. That seems logical. Thus: - About the role: opening paragraph + About SRM + Growth & Advancement + Team Culture + Consistent Reliable Work (these are reasons to join). We'll keep them as prose or list? Could be list but we can keep as

paragraphs. - Responsibilities: list. - Requirements: list (What Sets You Apart). - Benefits: list (Exceptional Benefits bullet points). We'll include the bullet points from Exceptional Benefits. - Pay: list (Competitive Compensation bullet). We must not create Schedule section. Now we need to output HTML fragment only, no /. Use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to ensure we don't repeat job title as heading. Not needed. We must not include Job ID/requisition numbers. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. We already removed final apply line. Check for any duplicated lines: none. Now craft HTML. First, About the role section: