Freight Handler
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use - for lists
- Use
for prose
- Do NOT repeat job title as heading
- Do NOT put Job ID/requisition numbers as headings
- Preserve ALL substantive information
- Remove boilerplate (cookie/navigation/legal/EEO/scam-warning)
- Include section ONLY when real specific content exists
- Never emit heading followed by filler/placeholder text
- Never create Pay/Schedule/Benefits sections unless posting actually states them
- Output ONLY HTML fragment, no /, no markdown code fences
Now, the posting has:
- Pay: "$500-$1000+/weekly" - this is specific, so include Pay section
- Schedule: "Monday- Friday 5 AM- FINISH" - specific, include Schedule section
- About the role: "The Opportunity" paragraph describes duties - could be "About the role" or "Responsibilities". The duties are listed in prose: "loading, unloading, selecting, freight hauling, auditing, repacking, sorting, palletizing, clean up, housekeeping and other duties as assigned by site leadership." That's a list of duties, so I'll make a Responsibilities section with a list.
- Requirements: bullet points under "Requirements" - three items. Use Requirements heading.
- Benefits: "Why You Should Work With Us" lists benefits: paid weekly, benefits after 60 days, career growth, travel team, paid training, safety incentives, high-performance culture. That's a Benefits section.
- About the Company: "About The Company" paragraph - could be "About the company" section.
Also there's a preamble about Capstone culture: "People want to work at Capstone because of our high-performance culture..." That's part of the company description or could be part of "Why You Should Work With Us". But the "Why You Should Work With Us" already includes that culture line at the end. Actually the posting has two culture paragraphs: one at top and one at bottom of "Why You Should Work With Us". I'll include the top one in About the company or maybe a separate "About the role" intro? The rules say use
for prose. I'll include a brief intro paragraph before sections? But the instruction says output only the HTML fragment with sections. Probably we should include an introductory paragraph about the company culture before sections? However the rules: "Prefer a few substantive sections over many thin ones." And "include a section ONLY when the posting has real, specific content for it". The top paragraph is about company culture, not a section heading. Could be a
before sections. But the output should be only the HTML fragment, which can include a
before the first
. That's allowed.
But the user said: "Output ONLY the HTML fragment — no /, no markdown code fences." So we can output a series of elements: maybe a
then
sections.
Let's structure:
1. Introductory paragraph: "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?"
2. Pay section: Pay
$500–$1,000+ per week
(note: the posting says "$500-$1000+/weekly". I'll keep as is.)
3. Schedule section: Schedule
Monday–Friday, 5:00 AM – finish
4. About the role: About the role
Warehouse Associates perform a variety of warehouse responsibilities including but not limited to loading, unloading, selecting, freight hauling, auditing, repacking, sorting, palletizing, clean up, housekeeping and other duties as assigned by site leadership.
But the duties are a list, so better to make a Responsibilities section with a list. The heading "Responsibilities" is allowed. The rules say use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both "About the role" and "Responsibilities"? The posting has "The Opportunity" which describes the role and lists duties. I'll create "About the role" with a brief prose, then "Responsibilities" with a list. However the prose already includes the list. To avoid duplication, I'll make "Responsibilities" as a list extracted from that sentence. The sentence: "Warehouse Associates perform a variety of warehouse responsibilities including but not limited to loading, unloading, selecting, freight hauling, auditing, repacking, sorting, palletizing, clean up, housekeeping and other duties as assigned by site leadership." That's a list of duties. I'll create a Responsibilities section with a of each duty.
But the rules: "Preserve ALL substantive information; do NOT invent or summarize away detail." So I should keep the prose as well? Could have both: a prose intro then list. But that duplicates. Better to have a Responsibilities section with list, and maybe a brief intro sentence. I'll do:
Responsibilities
- Loading
- Unloading
- Selecting
- Freight hauling
- Auditing
- Repacking
- Sorting
- Palletizing
- Clean up
- Housekeeping
- Other duties as assigned by site leadership
5. Requirements: Requirements
- High-energy individual with a strong work ethic; the work is fast paced and very physical
- Lift and carry 25–75 lbs; materials handled vary
- Prior warehouse and/or equipment experience is preferred but we are willing to train the right candidate
6. Benefits: Benefits
- Paid weekly
- Benefits after 60 days of employment
- Career growth — company promotes from within first
- Join our travel team, see the country, learn how all our sites operate
- Paid training
- Safety incentives
- High-performance culture that inspires building strong relationships, challenging the status quo, working hard to deliver results, and paying it forward in our communities
7. About the company: 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.
Note: The posting ends with "#CB" which is likely a tag, ignore.
Also location: "Alcoa, TN" - could be included in a Location section? The rules don't mention Location heading, but we could include as a maybe in intro. But the rules say use
for section headings like Pay, Schedule, etc. Location not listed. Could fold into a short
at top. I'll include a
with location before sections.
But the user said: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So location is minor metadata, fold into a short
. I'll add a
at beginning: "Location: Alcoa, TN". But the posting also includes pay and schedule in the top line. I'll include those in their own sections.
Let's craft the HTML fragment.
Order: maybe start with location, pay, schedule, then about the role/responsibilities, requirements, benefits, about the company.
But the rules: "Prefer a few substantive sections over many thin ones." So we have Pay, Schedule, Responsibilities, Requirements, Benefits, About the company. That's six sections, all substantive.
I'll output:
Location: Alcoa, TN
Pay
$500–$1,000+ per week
Schedule
Monday–Friday, 5:00 AM – finish
Responsibilities
- Loading
- Unloading
- Selecting
- Freight hauling
- Auditing
- Repacking
- Sorting
- Palletizing
- Clean up
- Housekeeping
- Other duties as assigned by site leadership
Requirements
- High-energy individual with a strong work ethic; the work is fast paced and very physical
- Lift and carry 25–75 lbs; materials handled vary
- Prior warehouse and/or equipment experience is preferred but we are willing to train the right candidate
Benefits
- Paid weekly
- Benefits after 60 days of employment
- Career growth — company promotes from within first
- Join our travel team, see the country, learn how all our sites operate
- Paid training
- Safety incentives
- High-performance culture that inspires building strong relationships, challenging the status quo, working hard to deliver results, and paying 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.
Check for any boilerplate: The top culture paragraph is not included. Should we include it? It's part of the company culture description. The "Why You Should Work With Us" includes a similar line at the end. I've included that in Benefits. The top paragraph is more about why people want to work at Capstone. Could be part of About the company or a separate "Culture" section. But the rules say only include sections with real specific content. The
for prose - Do NOT repeat job title as heading - Do NOT put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove boilerplate (cookie/navigation/legal/EEO/scam-warning) - Include section ONLY when real specific content exists - Never emit heading followed by filler/placeholder text - Never create Pay/Schedule/Benefits sections unless posting actually states them - Output ONLY HTML fragment, no /, no markdown code fences Now, the posting has: - Pay: "$500-$1000+/weekly" - this is specific, so include Pay section - Schedule: "Monday- Friday 5 AM- FINISH" - specific, include Schedule section - About the role: "The Opportunity" paragraph describes duties - could be "About the role" or "Responsibilities". The duties are listed in prose: "loading, unloading, selecting, freight hauling, auditing, repacking, sorting, palletizing, clean up, housekeeping and other duties as assigned by site leadership." That's a list of duties, so I'll make a Responsibilities section with a list. - Requirements: bullet points under "Requirements" - three items. Use Requirements heading. - Benefits: "Why You Should Work With Us" lists benefits: paid weekly, benefits after 60 days, career growth, travel team, paid training, safety incentives, high-performance culture. That's a Benefits section. - About the Company: "About The Company" paragraph - could be "About the company" section. Also there's a preamble about Capstone culture: "People want to work at Capstone because of our high-performance culture..." That's part of the company description or could be part of "Why You Should Work With Us". But the "Why You Should Work With Us" already includes that culture line at the end. Actually the posting has two culture paragraphs: one at top and one at bottom of "Why You Should Work With Us". I'll include the top one in About the company or maybe a separate "About the role" intro? The rules say use
for prose. I'll include a brief intro paragraph before sections? But the instruction says output only the HTML fragment with sections. Probably we should include an introductory paragraph about the company culture before sections? However the rules: "Prefer a few substantive sections over many thin ones." And "include a section ONLY when the posting has real, specific content for it". The top paragraph is about company culture, not a section heading. Could be a
before sections. But the output should be only the HTML fragment, which can include a
before the first
. That's allowed. But the user said: "Output ONLY the HTML fragment — no /, no markdown code fences." So we can output a series of elements: maybe a
then
sections.
Let's structure:
1. Introductory paragraph: "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?"
2. Pay section: Pay
$500–$1,000+ per week
(note: the posting says "$500-$1000+/weekly". I'll keep as is.) 3. Schedule section:Schedule
Monday–Friday, 5:00 AM – finish
4. About the role:About the role
Warehouse Associates perform a variety of warehouse responsibilities including but not limited to loading, unloading, selecting, freight hauling, auditing, repacking, sorting, palletizing, clean up, housekeeping and other duties as assigned by site leadership.
But the duties are a list, so better to make a Responsibilities section with a list. The heading "Responsibilities" is allowed. The rules say use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both "About the role" and "Responsibilities"? The posting has "The Opportunity" which describes the role and lists duties. I'll create "About the role" with a brief prose, then "Responsibilities" with a list. However the prose already includes the list. To avoid duplication, I'll make "Responsibilities" as a list extracted from that sentence. The sentence: "Warehouse Associates perform a variety of warehouse responsibilities including but not limited to loading, unloading, selecting, freight hauling, auditing, repacking, sorting, palletizing, clean up, housekeeping and other duties as assigned by site leadership." That's a list of duties. I'll create a Responsibilities section with a of each duty.
But the rules: "Preserve ALL substantive information; do NOT invent or summarize away detail." So I should keep the prose as well? Could have both: a prose intro then list. But that duplicates. Better to have a Responsibilities section with list, and maybe a brief intro sentence. I'll do:
Responsibilities
- Loading
- Unloading
- Selecting
- Freight hauling
- Auditing
- Repacking
- Sorting
- Palletizing
- Clean up
- Housekeeping
- Other duties as assigned by site leadership
5. Requirements: Requirements
- High-energy individual with a strong work ethic; the work is fast paced and very physical
- Lift and carry 25–75 lbs; materials handled vary
- Prior warehouse and/or equipment experience is preferred but we are willing to train the right candidate
6. Benefits: Benefits
- Paid weekly
- Benefits after 60 days of employment
- Career growth — company promotes from within first
- Join our travel team, see the country, learn how all our sites operate
- Paid training
- Safety incentives
- High-performance culture that inspires building strong relationships, challenging the status quo, working hard to deliver results, and paying it forward in our communities
7. About the company: 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.
Note: The posting ends with "#CB" which is likely a tag, ignore.
Also location: "Alcoa, TN" - could be included in a Location section? The rules don't mention Location heading, but we could include as a maybe in intro. But the rules say use
for section headings like Pay, Schedule, etc. Location not listed. Could fold into a short
at top. I'll include a
with location before sections.
But the user said: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So location is minor metadata, fold into a short
. I'll add a
at beginning: "Location: Alcoa, TN". But the posting also includes pay and schedule in the top line. I'll include those in their own sections.
Let's craft the HTML fragment.
Order: maybe start with location, pay, schedule, then about the role/responsibilities, requirements, benefits, about the company.
But the rules: "Prefer a few substantive sections over many thin ones." So we have Pay, Schedule, Responsibilities, Requirements, Benefits, About the company. That's six sections, all substantive.
I'll output:
Location: Alcoa, TN
Pay
$500–$1,000+ per week
Schedule
Monday–Friday, 5:00 AM – finish
Responsibilities
- Loading
- Unloading
- Selecting
- Freight hauling
- Auditing
- Repacking
- Sorting
- Palletizing
- Clean up
- Housekeeping
- Other duties as assigned by site leadership
Requirements
- High-energy individual with a strong work ethic; the work is fast paced and very physical
- Lift and carry 25–75 lbs; materials handled vary
- Prior warehouse and/or equipment experience is preferred but we are willing to train the right candidate
Benefits
- Paid weekly
- Benefits after 60 days of employment
- Career growth — company promotes from within first
- Join our travel team, see the country, learn how all our sites operate
- Paid training
- Safety incentives
- High-performance culture that inspires building strong relationships, challenging the status quo, working hard to deliver results, and paying 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.
Check for any boilerplate: The top culture paragraph is not included. Should we include it? It's part of the company culture description. The "Why You Should Work With Us" includes a similar line at the end. I've included that in Benefits. The top paragraph is more about why people want to work at Capstone. Could be part of About the company or a separate "Culture" section. But the rules say only include sections with real specific content. The
Responsibilities
- Loading
- Unloading
- Selecting
- Freight hauling
- Auditing
- Repacking
- Sorting
- Palletizing
- Clean up
- Housekeeping
- Other duties as assigned by site leadership
Requirements
- High-energy individual with a strong work ethic; the work is fast paced and very physical
- Lift and carry 25–75 lbs; materials handled vary
- Prior warehouse and/or equipment experience is preferred but we are willing to train the right candidate
Benefits
- Paid weekly
- Benefits after 60 days of employment
- Career growth — company promotes from within first
- Join our travel team, see the country, learn how all our sites operate
- Paid training
- Safety incentives
- High-performance culture that inspires building strong relationships, challenging the status quo, working hard to deliver results, and paying 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.
Note: The posting ends with "#CB" which is likely a tag, ignore. Also location: "Alcoa, TN" - could be included in a Location section? The rules don't mention Location heading, but we could include as amaybe in intro. But the rules say use
for section headings like Pay, Schedule, etc. Location not listed. Could fold into a short
at top. I'll include a
with location before sections. But the user said: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So location is minor metadata, fold into a short
. I'll add a
at beginning: "Location: Alcoa, TN". But the posting also includes pay and schedule in the top line. I'll include those in their own sections. Let's craft the HTML fragment. Order: maybe start with location, pay, schedule, then about the role/responsibilities, requirements, benefits, about the company. But the rules: "Prefer a few substantive sections over many thin ones." So we have Pay, Schedule, Responsibilities, Requirements, Benefits, About the company. That's six sections, all substantive. I'll output:
Location: Alcoa, TN
Pay
$500–$1,000+ per week
Schedule
Monday–Friday, 5:00 AM – finish
Responsibilities
- Loading
- Unloading
- Selecting
- Freight hauling
- Auditing
- Repacking
- Sorting
- Palletizing
- Clean up
- Housekeeping
- Other duties as assigned by site leadership
Requirements
- High-energy individual with a strong work ethic; the work is fast paced and very physical
- Lift and carry 25–75 lbs; materials handled vary
- Prior warehouse and/or equipment experience is preferred but we are willing to train the right candidate
Benefits
- Paid weekly
- Benefits after 60 days of employment
- Career growth — company promotes from within first
- Join our travel team, see the country, learn how all our sites operate
- Paid training
- Safety incentives
- High-performance culture that inspires building strong relationships, challenging the status quo, working hard to deliver results, and paying 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.
Check for any boilerplate: The top culture paragraph is not included. Should we include it? It's part of the company culture description. The "Why You Should Work With Us" includes a similar line at the end. I've included that in Benefits. The top paragraph is more about why people want to work at Capstone. Could be part of About the company or a separate "Culture" section. But the rules say only include sections with real specific content. The