Forklift Operator

We need to produce 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. Let's parse the posting. Content: - "Goodyear AZ Schedule set at time of hire 2:00 AM-Finish 4:00 AM-Finish 2:00 PM Finish Potential to earn $720- $920 paid weekly" Interpretation: schedule set at time of hire: maybe shift times? It says "2:00 AM-Finish 4:00 AM-Finish 2:00 PM Finish". That seems garbled. Might be multiple shift options: 2:00 AM to finish? Actually maybe they have three possible shifts: 2:00 AM - finish, 4:00 AM - finish, 2:00 PM - finish. Not clear. But we have schedule info: "Schedule set at time of hire". Also "Potential to earn $720- $920 paid weekly". So we have Pay and Schedule sections. - "People want to work at Capstone because of our high-performance culture. We build strong relationships, challenge the status quo, work hard to deliver results, and pay it forward in our communities. Through transparency and open lines of communication, we do the right thing and deliver on our promises. Think you have what it takes?" This is generic culture description. - "The Opportunity Forklift Operators maneuver freight, load, and unload both by hand and with equipment and other duties as assigned by site leadership." That's responsibilities. - "Requirements High-energy individual with a strong work ethic, the work is fast paced and very physical Lift and carry 25-75lbs, materials handled vary 1+ year warehouse and forklift experience is preferred but we are willing to train the right candidate" - "Why You Should Work With Us Get paid weeklyBenefits-after 60 days of employmentCareer growth-our company looks to promote from within first Join our travel team, see the country, learn how all our sites operatePaid Training, Safety Incentives Our team fully embraces a high-performance culture, that inspires us to build strong relationships, challenge the status quo, work hard to deliver results, and pay it forward in our communities." - "About The Company Capstone is a North American supply chain solutions partner with more than 650 operating locations, 19,000 associates, and 60,000 carriers. We have capabilities in freight management, warehouse and distribution center support, last-mile delivery, supply chain analytics, and optimization, and more. Our integrated, end-to-end logistics solutions uniquely position us to help partners reduce warehousing and transportation costs." We need to remove boilerplate: cookie/navigation/legal/EEO etc. Not present. We need to output only HTML fragment, no /, no markdown fences. We need headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. - About the role: maybe we can use "The Opportunity" description as role description. Could be "About the role". We have a paragraph describing Forklift Operators duties. That could be responsibilities. But we also have separate responsibilities. Could combine. Better: Use "About the role" for a brief description of the job (maybe the first paragraph after The Opportunity). But we have "The Opportunity Forklift Operators maneuver freight, load, and unload both by hand and with equipment and other duties as assigned by site leadership." That's essentially responsibilities. So we could put that under Responsibilities. About the role could be a summary: maybe we can use the culture paragraph? But that's more about company. Could be "About the company". But we have a separate About The Company section. Thus sections: - Responsibilities: list of duties (maybe just one sentence). Could be bullet list? It's a single sentence; we can still put in

or

• . The rule: Use
  • for any list of duties/requirements/benefits. If not a list, we can use

    . So we can put responsibilities in

    . - Requirements: we have bullet-like content: "High-energy individual with a strong work ethic, the work is fast paced and very physical Lift and carry 25-75lbs, materials handled vary 1+ year warehouse and forklift experience is preferred but we are willing to train the right candidate". Could be turned into list items: High-energy individual with strong work ethic; Fast-paced, very physical work; Ability to lift and carry 25-75 lbs; Materials handled vary; 1+ year warehouse and forklift experience preferred (but willing to train). We'll make

    • . - Qualifications: maybe same as requirements? Could be separate but we may not have distinct qualifications. Could skip Qualifications if no specific content. - Skills: maybe not explicit. Could skip. - Benefits: we have "Get paid weekly", "Benefits-after 60 days of employment", "Career growth-our company looks to promote from within first", "Join our travel team, see the country, learn how all our sites operate", "Paid Training, Safety Incentives". Also "People want to work at Capstone because of our high-performance culture..." but that's culture. We'll extract benefits list. - Pay: "Potential to earn $720- $920 paid weekly". So we can put that in

      under Pay. - Schedule: "Goodyear AZ Schedule set at time of hire 2:00 AM-Finish 4:00 AM-Finish 2:00 PM Finish". This is confusing but we can present as: Schedule set at time of hire; possible shifts: 2:00 AM start, 4:00 AM start, 2:00 PM start (finish time varies). We'll put as

      . - About the role: maybe we can use a brief description: "Forklift Operators maneuver freight, load, and unload both by hand and with equipment and other duties as assigned by site leadership." That's essentially responsibilities. But we need About the role section; we could put a short paragraph summarizing the role: "As a Forklift Operator, you will maneuver freight, load and unload materials by hand and with equipment, and perform other duties as assigned." That's fine. - About the company: we have a paragraph about Capstone. Could be a section "About the company". But the instruction only lists specific headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "About the company". However we could treat that as "About the role"? Not ideal. But we could include it under "About the role" as a description of the company? Might be okay. However the instruction says use those headings for section headings. It doesn't forbid other headings? It says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings for sections. It doesn't say we cannot add other headings, but likely they want only those. Safer to stick to those headings. So we need to fit company info somewhere; maybe under "About the role" we can include both role and company overview. Or we could omit company info if not fitting. But we must preserve ALL substantive information; cannot omit company info. So we need to include it somewhere. Perhaps we can add a section "About the company" even though not listed; but the instruction says use those headings for section headings (e.g. ...). It doesn't explicitly forbid other headings, but says "Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests examples, not exhaustive. So we can add other headings if needed. However they also say "Prefer a few substantive sections over many thin ones." So we could combine company info into "About the role" or maybe "About the company" as its own heading. I'd add "About the company" as its own

      to preserve info. But the instruction: "Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings. So we can add About the company. We must not repeat the job title as a heading. The job title is "Forklift Operators". Not used as heading. We must not put Job ID/requisition numbers as headings. We must remove boilerplate: cookie/navigation/legal/EEO etc. Not present. We must not include application instructions. Now craft HTML. Structure:

      About the role

      Forklift Operators maneuver freight, load, and unload both by hand and with equipment, and perform other duties as assigned by site leadership.

      Responsibilities

      Same as above? Might be duplicate. Better to have About the role be a brief summary, Responsibilities be a list of duties. But we only have one duty sentence. Could still list as

      • Maneuver freight
      • Load and unload materials by hand and with equipment
      • Perform other duties as assigned by site leadership
      . That would be more detailed. Let's extract duties from sentence: "maneuver freight, load, and unload both by hand and with equipment and other duties as assigned by site leadership." So we can break into three. Thus Responsibilities
      • Maneuver freight
      • Load and unload materials by hand and with equipment
      • Perform other duties as assigned by site leadership
      . Now About the role could be a brief paragraph: "As a Forklift Operator at Capstone's Goodyear, AZ location, you will support warehouse operations by moving freight and materials safely and efficiently." We can craft but must not invent detail. We can base on given: "Forklift Operators maneuver freight, load, and unload both by hand and with equipment and other duties as assigned by site leadership." That's already the duty. So About the role could be same as responsibilities but we risk duplication. Maybe we can skip About the role and just have Responsibilities, Requirements, Benefits, Pay, Schedule, About the company. But the instruction says prefer few substantive sections over many thin ones. Having About the role may be thin if we just repeat. Could combine About the role and Responsibilities into one section titled About the role (or Responsibilities). But we need to follow headings list; we can choose to include only those sections that have real content. So we could omit About the role if it's not distinct. However we need to preserve all substantive info; we can put the role description under Responsibilities. That's fine. Thus sections: Responsibilities, Requirements, Benefits, Pay, Schedule, About the company. Now Requirements: we need to list items. From text: "High-energy individual with a strong work ethic, the work is fast paced and very physical Lift and carry 25-75lbs, materials handled vary 1+ year warehouse and forklift experience is preferred but we are willing to train the right candidate" We can parse: - High-energy individual with strong work ethic - Fast-paced, very physical work - Ability to lift and carry 25-75 lbs - Materials handled vary (maybe "materials handled vary" meaning varied materials) - 1+ year warehouse and forklift experience preferred (but willing to train) We'll make list. Benefits: list items: - Get paid weekly - Benefits after 6