Heavy Equipment CDL Driver
EquipmentShare · Summerville, SC · 1 mo ago
On-siteManagementFull-time
We need to output HTML fragment with headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate.
We need to parse the posting.
Key sections:
- Schedule: Monday to Friday, 7:00 AM to 5:00 PM, and offers overtime pay after working 40 hours. (This role is subject to on-call scheduling with additional compensation provided)
- Primary Responsibilities: list of duties.
- Why EquipmentShare? (maybe "About the role"? Actually "Why EquipmentShare?" is like benefits/perks. Could map to Benefits or About the role? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly.
- Perks & Benefits: list.
- About You: maybe "About the role"? Actually "About You" is more like qualifications/skills. Could map to Skills & Qualifications.
- Skills & Qualifications: list.
- A Workplace For All: EEO boilerplate, we should remove.
- Also there is "Build the Future with Us — EquipmentShare is Hiring a Heavy Equipment CDL Driver" title, we ignore.
- There's also "Primary Responsibilities" heading.
- There's "Why EquipmentShare?" heading.
- There's "Perks & Benefits" heading.
- There's "About You" heading.
- There's "Skills & Qualifications" heading.
- There's "A Workplace For All" heading (EEO) - remove.
- There's also "EquipmentShare is an Equal Opportunity Employer..." remove.
- Also "Employment is contingent on passing a background check..." remove.
We need to preserve all substantive information.
Let's extract content:
Schedule: Monday to Friday, 7:00 AM to 5:00 PM, and offers overtime pay after working 40 hours. (This role is subject to on-call scheduling with additional compensation provided)
Pay: Not explicitly stated besides overtime pay after 40 hours. No base pay given. So we should not create Pay section unless posting actually states them. It mentions overtime pay after 40 hours, but not base salary. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state schedule and mentions overtime pay (which is pay-related). However Pay section would be for base pay; we have no base pay. Should we still include Pay? Probably not, because no specific pay amount. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state schedule (yes) and mentions overtime pay (which is pay). But Pay section would be for compensation details; we have only mention of overtime pay after 40 hours, which is a pay detail. Could we include Pay with that detail? Might be okay but risk. Safer to include Schedule section only, and maybe include Pay only if there is explicit pay rate or salary. Since not, omit Pay.
Benefits: We have Perks & Benefits list: Monthly Family Dinner Night, Competitive compensation, Full medical, dental, vision coverage, Generous PTO + paid holidays, 401(k) + company match, Tool and boot reimbursements (role dependent), Gym membership stipend + wellness programs (earn PTO and prizes!), Company events, food truck nights, and monthly dinner nights, 16 hours of paid volunteer time per year, Career advancement, leadership training, professional development opportunities.
Also "Why EquipmentShare?" includes: people-first company powered by cutting-edge technology, proprietary T3 platform makes job easier, safer, more connected; team of problem-solvers, go-getters, builders; looking for teammates who take pride in doing meaningful work and want to be part of building something special. That's more about culture; could be part of About the role or Benefits? Might fit under About the role (description of company). We'll create About the role section with that narrative.
Responsibilities: list from Primary Responsibilities.
Requirements: maybe from Education and Experience? Actually Requirements could be the mandatory items: CDL license, background/drug test, DOT physical, age 21+, clean driving record, ability to lift 40 lbs, travel frequently, clean shaven requirement, safety sensitive position, contingent on 10 panel drug screen. Also maybe "Must hold either a commercial drivers license (Class A CDL) or chauffeur’s license depending on state, appropriate for weight of vehicle to be operated". That's requirement.
Qualifications: maybe similar to Skills & Qualifications? Actually Skills & Qualifications section includes Required Skills/Abilities and Education and Experience and Physical Requirements. Could split: Skills (interpersonal, customer service, focus), Qualifications (license, background, DOT physical, age, record). But we have headings Skills and Qualifications separate. We'll allocate accordingly.
Skills: Strong interpersonal and customer service skills, ability to speak professionally and courteously, ability to remain focused in a busy environment.
Qualifications: Must hold CDL A or chauffeur's license appropriate for weight, must pass background and drug testing, must pass DOT physical, must be at least 21, clean driving record, able to lift 40 pounds, able to travel frequently, clean shaven requirement for some customers, safety sensitive position, contingent on 10 panel drug screen.
Also maybe "Education and Experience:" includes license etc. We'll treat as qualifications.
Now About the role: from first paragraph and "Why EquipmentShare?" maybe combine.
Let's craft About the role: "At EquipmentShare, we’re not just filling a role — we’re assembling the best team on the planet to build something that’s never been built before. We’re on a mission to transform an industry that’s been stuck in the past by empowering contractors and communities through innovative technology, real-time support, and a team that truly cares. We’re hiring a CDL Delivery Driver at our rental facility in Ladson, SC, and we’re looking for someone who’s ready to grow with us, bring energy and drive to their work, and help us build the future of construction. Why EquipmentShare? Because we do things differently — and we think you’ll feel it from day one. We’re a people-first company powered by cutting-edge technology. That means our proprietary T3 platform doesn’t just run our business — it also makes your job easier, safer, and more connected. Whether you’re behind the wheel, under the hood, leading a branch, or closing deals — tech supports you, and you drive us forward. We’re a team of problem-solvers, go-getters, and builders. And we’re looking for teammates who take pride in doing meaningful work and want to be part of building something special."
That seems good.
Now Responsibilities: list items from Primary Responsibilities.
Let's list each bullet:
- Operates vehicle according to applicable state and federal transportation laws
- Transports loads safely and in a timely manner over required route, obeying all traffic laws and observing all safety regulations
- Deftly maneuvers truck and trailer into loading and unloading areas; follows loading crew signals
- Assists with loading of or loads and unloads goods and materials, using specialized equipment when warranted; unloads empty skids and returns all equipment to designated area
- Maintains signed invoices, shipping bills of lading, and other required paperwork; delivers documentation to shipping office or other appropriate staff when delivery route is complete
- Facilitates routine service on trucks, which may include checking oil, water, gasoline, and air; reports maintenance malfunctions to Shipping Supervisor
- Arranges trailers in shipping yards for optimum loading patterns
- Performs other related duties as assigned
Now Benefits: list from Perks & Benefits.
- Monthly Family Dinner Night — We treat you and your family to dinner every month, because family comes first. (An employee favorite!) *restrictions apply
- Competitive compensation
- Full medical, dental, and vision coverage for full-time employees
- Generous PTO + paid holidays
- 401(k) + company match
- Tool and boot reimbursements (role dependent)
- Gym membership stipend + wellness programs (earn PTO and prizes!)
- Company events, food truck nights, and monthly dinner nights
- 16 hours of paid volunteer time per year — give back to the community you call home
- Career advancement, leadership training, and professional development opportunities
Now Schedule: Monday to Friday, 7:00 AM to 5:00 PM, and offers overtime pay after working 40 hours. (This role is subject to on-call scheduling with additional compensation provided)
Now Skills: Strong interpersonal and customer service skills with the ability to speak professionally and courteously with customers and staff at delivery points; Ability to remain focused in a busy environment.
Now Qualifications: Must hold either a commercial drivers license (Class A CDL) or chauffeur’s license depending on state, appropriate for weight of vehicle to be operated; Must pass background and drug testing as required by federal and/or state department(s) of transportation regulations; Must pass DOT physical, as trucks driven are over 10k lbs; Must be at least 21 years old to operate company vehicle; Must have a clean driving record; Physical Requirements: Prolonged periods sitting in a trailer cab for long periods of time; Must be able to lift and move up to 40 pounds at a time; Must be able to travel frequently; CDL drivers may be required to be clean shaven in order to deliver to EquipmentShare customers who have this requirement; This is a safety sensitive position and any offer of employment will be contingent on passing a 10 panel drug screen.
We could separate Physical Requirements as part of Qualifications.
Now we need to output HTML fragment with
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate.
We need to parse the posting.
Key sections:
- Schedule: Monday to Friday, 7:00 AM to 5:00 PM, and offers overtime pay after working 40 hours. (This role is subject to on-call scheduling with additional compensation provided)
- Primary Responsibilities: list of duties.
- Why EquipmentShare? (maybe "About the role"? Actually "Why EquipmentShare?" is like benefits/perks. Could map to Benefits or About the role? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly.
- Perks & Benefits: list.
- About You: maybe "About the role"? Actually "About You" is more like qualifications/skills. Could map to Skills & Qualifications.
- Skills & Qualifications: list.
- A Workplace For All: EEO boilerplate, we should remove.
- Also there is "Build the Future with Us — EquipmentShare is Hiring a Heavy Equipment CDL Driver" title, we ignore.
- There's also "Primary Responsibilities" heading.
- There's "Why EquipmentShare?" heading.
- There's "Perks & Benefits" heading.
- There's "About You" heading.
- There's "Skills & Qualifications" heading.
- There's "A Workplace For All" heading (EEO) - remove.
- There's also "EquipmentShare is an Equal Opportunity Employer..." remove.
- Also "Employment is contingent on passing a background check..." remove.
We need to preserve all substantive information.
Let's extract content:
Schedule: Monday to Friday, 7:00 AM to 5:00 PM, and offers overtime pay after working 40 hours. (This role is subject to on-call scheduling with additional compensation provided)
Pay: Not explicitly stated besides overtime pay after 40 hours. No base pay given. So we should not create Pay section unless posting actually states them. It mentions overtime pay after 40 hours, but not base salary. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state schedule and mentions overtime pay (which is pay-related). However Pay section would be for base pay; we have no base pay. Should we still include Pay? Probably not, because no specific pay amount. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state schedule (yes) and mentions overtime pay (which is pay). But Pay section would be for compensation details; we have only mention of overtime pay after 40 hours, which is a pay detail. Could we include Pay with that detail? Might be okay but risk. Safer to include Schedule section only, and maybe include Pay only if there is explicit pay rate or salary. Since not, omit Pay.
Benefits: We have Perks & Benefits list: Monthly Family Dinner Night, Competitive compensation, Full medical, dental, vision coverage, Generous PTO + paid holidays, 401(k) + company match, Tool and boot reimbursements (role dependent), Gym membership stipend + wellness programs (earn PTO and prizes!), Company events, food truck nights, and monthly dinner nights, 16 hours of paid volunteer time per year, Career advancement, leadership training, professional development opportunities.
Also "Why EquipmentShare?" includes: people-first company powered by cutting-edge technology, proprietary T3 platform makes job easier, safer, more connected; team of problem-solvers, go-getters, builders; looking for teammates who take pride in doing meaningful work and want to be part of building something special. That's more about culture; could be part of About the role or Benefits? Might fit under About the role (description of company). We'll create About the role section with that narrative.
Responsibilities: list from Primary Responsibilities.
Requirements: maybe from Education and Experience? Actually Requirements could be the mandatory items: CDL license, background/drug test, DOT physical, age 21+, clean driving record, ability to lift 40 lbs, travel frequently, clean shaven requirement, safety sensitive position, contingent on 10 panel drug screen. Also maybe "Must hold either a commercial drivers license (Class A CDL) or chauffeur’s license depending on state, appropriate for weight of vehicle to be operated". That's requirement.
Qualifications: maybe similar to Skills & Qualifications? Actually Skills & Qualifications section includes Required Skills/Abilities and Education and Experience and Physical Requirements. Could split: Skills (interpersonal, customer service, focus), Qualifications (license, background, DOT physical, age, record). But we have headings Skills and Qualifications separate. We'll allocate accordingly.
Skills: Strong interpersonal and customer service skills, ability to speak professionally and courteously, ability to remain focused in a busy environment.
Qualifications: Must hold CDL A or chauffeur's license appropriate for weight, must pass background and drug testing, must pass DOT physical, must be at least 21, clean driving record, able to lift 40 pounds, able to travel frequently, clean shaven requirement for some customers, safety sensitive position, contingent on 10 panel drug screen.
Also maybe "Education and Experience:" includes license etc. We'll treat as qualifications.
Now About the role: from first paragraph and "Why EquipmentShare?" maybe combine.
Let's craft About the role: "At EquipmentShare, we’re not just filling a role — we’re assembling the best team on the planet to build something that’s never been built before. We’re on a mission to transform an industry that’s been stuck in the past by empowering contractors and communities through innovative technology, real-time support, and a team that truly cares. We’re hiring a CDL Delivery Driver at our rental facility in Ladson, SC, and we’re looking for someone who’s ready to grow with us, bring energy and drive to their work, and help us build the future of construction. Why EquipmentShare? Because we do things differently — and we think you’ll feel it from day one. We’re a people-first company powered by cutting-edge technology. That means our proprietary T3 platform doesn’t just run our business — it also makes your job easier, safer, and more connected. Whether you’re behind the wheel, under the hood, leading a branch, or closing deals — tech supports you, and you drive us forward. We’re a team of problem-solvers, go-getters, and builders. And we’re looking for teammates who take pride in doing meaningful work and want to be part of building something special."
That seems good.
Now Responsibilities: list items from Primary Responsibilities.
Let's list each bullet:
- Operates vehicle according to applicable state and federal transportation laws
- Transports loads safely and in a timely manner over required route, obeying all traffic laws and observing all safety regulations
- Deftly maneuvers truck and trailer into loading and unloading areas; follows loading crew signals
- Assists with loading of or loads and unloads goods and materials, using specialized equipment when warranted; unloads empty skids and returns all equipment to designated area
- Maintains signed invoices, shipping bills of lading, and other required paperwork; delivers documentation to shipping office or other appropriate staff when delivery route is complete
- Facilitates routine service on trucks, which may include checking oil, water, gasoline, and air; reports maintenance malfunctions to Shipping Supervisor
- Arranges trailers in shipping yards for optimum loading patterns
- Performs other related duties as assigned
Now Benefits: list from Perks & Benefits.
- Monthly Family Dinner Night — We treat you and your family to dinner every month, because family comes first. (An employee favorite!) *restrictions apply
- Competitive compensation
- Full medical, dental, and vision coverage for full-time employees
- Generous PTO + paid holidays
- 401(k) + company match
- Tool and boot reimbursements (role dependent)
- Gym membership stipend + wellness programs (earn PTO and prizes!)
- Company events, food truck nights, and monthly dinner nights
- 16 hours of paid volunteer time per year — give back to the community you call home
- Career advancement, leadership training, and professional development opportunities
Now Schedule: Monday to Friday, 7:00 AM to 5:00 PM, and offers overtime pay after working 40 hours. (This role is subject to on-call scheduling with additional compensation provided)
Now Skills: Strong interpersonal and customer service skills with the ability to speak professionally and courteously with customers and staff at delivery points; Ability to remain focused in a busy environment.
Now Qualifications: Must hold either a commercial drivers license (Class A CDL) or chauffeur’s license depending on state, appropriate for weight of vehicle to be operated; Must pass background and drug testing as required by federal and/or state department(s) of transportation regulations; Must pass DOT physical, as trucks driven are over 10k lbs; Must be at least 21 years old to operate company vehicle; Must have a clean driving record; Physical Requirements: Prolonged periods sitting in a trailer cab for long periods of time; Must be able to lift and move up to 40 pounds at a time; Must be able to travel frequently; CDL drivers may be required to be clean shaven in order to deliver to EquipmentShare customers who have this requirement; This is a safety sensitive position and any offer of employment will be contingent on passing a 10 panel drug screen.
We could separate Physical Requirements as part of Qualifications.
Now we need to output HTML fragment with headings and - for lists,
for prose.
We should not include empty sections.
Let's structure:
About the role
... prose ...
Responsibilities
- ...
...
Requirements
maybe not needed if we have Qualifications covering. But we have both Requirements and Qualifications headings available. The posting has "Education and Experience:" and "Physical Requirements:" which could be Requirements. And "Skills & Qualifications:" includes Skills and Qualifications. So we could map:
- Requirements: Education and Experience (license, background, DOT physical, age, record) plus maybe physical requirements? But physical requirements are also under Skills & Qualifications. Might be better to put Requirements as the mandatory qualifications (license, background, DOT physical, age, record). And Qualifications as skills? Actually the headings list includes Skills and Qualifications separate. So we can put Skills under Skills heading, and Qualifications under Qualifications heading (including license, background, etc). Requirements maybe not needed if we don't have distinct content. But we could use Requirements for the license etc and Qualifications for skills? However the instruction says use those headings if there is real specific content. We have content for Skills (interpersonal, focus). We have content for Qualifications (license, background, DOT physical, age, record, clean record, lift, travel, clean shaven, safety sensitive, drug screen). We also have Physical Requirements (prolonged sitting, lift 40 lbs, travel frequently) which overlap with Qualifications. Might be okay to combine.
We could treat Requirements as the mandatory items (license, background, DOT physical, age, record) and Qualifications as the skills and physical requirements. But the headings list includes Skills and Qualifications, not Requirements? Actually list includes Requirements as a possible heading. So we can use Requirements for the mandatory qualifications (license, background, DOT physical, age, record). Skills for interpersonal, focus. Qualifications for physical requirements and maybe other attributes? But the heading "Qualifications" could also be used for the combination of license etc. However we need to avoid duplication.
Let's decide:
- Requirements: Must hold CDL A or chauffeur's license appropriate for weight; Must pass background and drug testing; Must pass DOT physical; Must be at least
- for lists,
for prose. We should not include empty sections. Let's structure:
About the role
... prose ...
Responsibilities
- ... ...
Requirements
maybe not needed if we have Qualifications covering. But we have both Requirements and Qualifications headings available. The posting has "Education and Experience:" and "Physical Requirements:" which could be Requirements. And "Skills & Qualifications:" includes Skills and Qualifications. So we could map: - Requirements: Education and Experience (license, background, DOT physical, age, record) plus maybe physical requirements? But physical requirements are also under Skills & Qualifications. Might be better to put Requirements as the mandatory qualifications (license, background, DOT physical, age, record). And Qualifications as skills? Actually the headings list includes Skills and Qualifications separate. So we can put Skills under Skills heading, and Qualifications under Qualifications heading (including license, background, etc). Requirements maybe not needed if we don't have distinct content. But we could use Requirements for the license etc and Qualifications for skills? However the instruction says use those headings if there is real specific content. We have content for Skills (interpersonal, focus). We have content for Qualifications (license, background, DOT physical, age, record, clean record, lift, travel, clean shaven, safety sensitive, drug screen). We also have Physical Requirements (prolonged sitting, lift 40 lbs, travel frequently) which overlap with Qualifications. Might be okay to combine. We could treat Requirements as the mandatory items (license, background, DOT physical, age, record) and Qualifications as the skills and physical requirements. But the headings list includes Skills and Qualifications, not Requirements? Actually list includes Requirements as a possible heading. So we can use Requirements for the mandatory qualifications (license, background, DOT physical, age, record). Skills for interpersonal, focus. Qualifications for physical requirements and maybe other attributes? But the heading "Qualifications" could also be used for the combination of license etc. However we need to avoid duplication. Let's decide: - Requirements: Must hold CDL A or chauffeur's license appropriate for weight; Must pass background and drug testing; Must pass DOT physical; Must be at least