Regional Class A Tanker Driver
Clean Harbors · Baltimore, MD · 1 mo ago
On-siteManagement$120k/yrFull-time
We need to output HTML fragment with headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must not repeat job title. Must not include Job ID etc. Remove boilerplate.
We need to parse the posting.
Content:
- Intro: "Clean Harbors is looking for a Regional Class A Tanker Driver to join their safety conscious team in Baltimore, MD! This route runs from Baltimore, MD to PA,VA and averages 60 hours per week."
- About The Role: "Drivers average $90-$120K per year $7,500 sign-on-bonus available Weekly home time Compensation includes hourly wages (all on-duty non-driving time)"
- Why work for Clean Harbors? list: Health and Safety priority, Comprehensive health benefits coverage after 30 days of full-time employment, Group 401K with company matching component, Own Part of the Company with our Employee Stock Purchase Plan, Paid time off, company paid training, and tuition reimbursement, Positive and safe work environments.
- Responsibilities: list bullet points.
- Qualifications: list bullet points.
- Additional info: phone number, EEO etc (remove). Also mention pay transparency etc (maybe part of Pay? but we should not include filler like "The posted salary range reflects the minimum and maximum target for this role...". That's about Pay but it's generic. We should only include Pay section if posting actually states them. It does mention salary range: Drivers average $90-$120K per year $7,500 sign-on-bonus available. That's in About The Role. Could also be Pay section. But we already have that info in About The Role. The instruction: Prefer a few substantive sections over many thin ones. So we could combine About the role and Pay? But they said use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include a section only when posting has real specific content for it. So we need to decide which sections have content.
We have:
- About the role: yes (description of role, route, hours, compensation, sign-on bonus, weekly home time). So include About the role.
- Responsibilities: yes list.
- Qualifications: yes list (Class A CDL, experience, endorsements, physical abilities, tech ability). Could also include Requirements? The posting has "Qualifications" heading. There's no separate "Requirements" besides qualifications. Could treat Qualifications as Requirements? But they said use headings for Requirements and Qualifications separately. However we should not create a section if no specific content. The posting lumps qualifications under "Qualifications". There's no separate "Requirements" section. So we could either put the qualifications under Qualifications heading and skip Requirements. Or we could treat the bullet list as Requirements and also have Qualifications? But better to follow the posting: Use Qualifications heading for the list. Skip Requirements.
- Benefits: yes list (health benefits, 401K, ESPP, PTO, training, tuition reimbursement, safe environment). So include Benefits.
- Pay: The posting mentions salary range and sign-on bonus within About the role. Could we extract Pay section? The instruction: "Prefer a few substantive sections over many thin ones." So we could keep Pay info inside About the role rather than separate Pay section. But they said include a section ONLY when the posting has real, specific content for it. The posting does have specific content about pay (salary range, sign-on bonus). So we could create a Pay section with that info. However then About the role would lose that info; we could keep About the role focusing on role description, route, hours, weekly home time. Then Pay section separate. That seems reasonable.
- Schedule: The posting mentions averages 60 hours per week, weekly home time. That's schedule info. Could create Schedule section. But we already have weekly home time in About the role or Schedule. To avoid thin sections, we could combine schedule info into About the role or Schedule. Since we already have About the role with route and hours, we could add schedule there. But we already have About the role with route and hours; we could add weekly home time there. Then Schedule section may be redundant. Better to keep About the role with route, hours, weekly home time, and maybe not create separate Schedule.
- Skills: Not explicitly listed; maybe "Ability to effectively use required technology such as mobile applications and computer software" could be skill. But we have Qualifications covering that. Could create Skills section but might be thin. Better to omit Skills.
Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay. Possibly Schedule if we want to separate weekly home time. But we already have weekly home time in About the role. Let's keep About the role includes route, hours, weekly home time. Pay section includes salary range and sign-on bonus. Benefits section as described. Responsibilities as list. Qualifications as list.
Now we need to format.
Use
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must not repeat job title. Must not include Job ID etc. Remove boilerplate.
We need to parse the posting.
Content:
- Intro: "Clean Harbors is looking for a Regional Class A Tanker Driver to join their safety conscious team in Baltimore, MD! This route runs from Baltimore, MD to PA,VA and averages 60 hours per week."
- About The Role: "Drivers average $90-$120K per year $7,500 sign-on-bonus available Weekly home time Compensation includes hourly wages (all on-duty non-driving time)"
- Why work for Clean Harbors? list: Health and Safety priority, Comprehensive health benefits coverage after 30 days of full-time employment, Group 401K with company matching component, Own Part of the Company with our Employee Stock Purchase Plan, Paid time off, company paid training, and tuition reimbursement, Positive and safe work environments.
- Responsibilities: list bullet points.
- Qualifications: list bullet points.
- Additional info: phone number, EEO etc (remove). Also mention pay transparency etc (maybe part of Pay? but we should not include filler like "The posted salary range reflects the minimum and maximum target for this role...". That's about Pay but it's generic. We should only include Pay section if posting actually states them. It does mention salary range: Drivers average $90-$120K per year $7,500 sign-on-bonus available. That's in About The Role. Could also be Pay section. But we already have that info in About The Role. The instruction: Prefer a few substantive sections over many thin ones. So we could combine About the role and Pay? But they said use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include a section only when posting has real specific content for it. So we need to decide which sections have content.
We have:
- About the role: yes (description of role, route, hours, compensation, sign-on bonus, weekly home time). So include About the role.
- Responsibilities: yes list.
- Qualifications: yes list (Class A CDL, experience, endorsements, physical abilities, tech ability). Could also include Requirements? The posting has "Qualifications" heading. There's no separate "Requirements" besides qualifications. Could treat Qualifications as Requirements? But they said use headings for Requirements and Qualifications separately. However we should not create a section if no specific content. The posting lumps qualifications under "Qualifications". There's no separate "Requirements" section. So we could either put the qualifications under Qualifications heading and skip Requirements. Or we could treat the bullet list as Requirements and also have Qualifications? But better to follow the posting: Use Qualifications heading for the list. Skip Requirements.
- Benefits: yes list (health benefits, 401K, ESPP, PTO, training, tuition reimbursement, safe environment). So include Benefits.
- Pay: The posting mentions salary range and sign-on bonus within About the role. Could we extract Pay section? The instruction: "Prefer a few substantive sections over many thin ones." So we could keep Pay info inside About the role rather than separate Pay section. But they said include a section ONLY when the posting has real, specific content for it. The posting does have specific content about pay (salary range, sign-on bonus). So we could create a Pay section with that info. However then About the role would lose that info; we could keep About the role focusing on role description, route, hours, weekly home time. Then Pay section separate. That seems reasonable.
- Schedule: The posting mentions averages 60 hours per week, weekly home time. That's schedule info. Could create Schedule section. But we already have weekly home time in About the role or Schedule. To avoid thin sections, we could combine schedule info into About the role or Schedule. Since we already have About the role with route and hours, we could add schedule there. But we already have About the role with route and hours; we could add weekly home time there. Then Schedule section may be redundant. Better to keep About the role with route, hours, weekly home time, and maybe not create separate Schedule.
- Skills: Not explicitly listed; maybe "Ability to effectively use required technology such as mobile applications and computer software" could be skill. But we have Qualifications covering that. Could create Skills section but might be thin. Better to omit Skills.
Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay. Possibly Schedule if we want to separate weekly home time. But we already have weekly home time in About the role. Let's keep About the role includes route, hours, weekly home time. Pay section includes salary range and sign-on bonus. Benefits section as described. Responsibilities as list. Qualifications as list.
Now we need to format.
Use for each section heading.
Inside each section, use
for prose,
- for lists.
We must not repeat job title. Not include Job ID etc.
We must preserve all substantive information.
Let's extract details.
About the role prose: "Clean Harbors is looking for a Regional Class A Tanker Driver to join their safety conscious team in Baltimore, MD! This route runs from Baltimore, MD to PA,VA and averages 60 hours per week. Weekly home time." Actually weekly home time is a bullet? In posting: "Weekly home time" appears as a separate line under About The Role. We'll include as prose: "Weekly home time."
Also mention "Compensation includes hourly wages (all on-duty non-driving time)" - that's compensation detail, but we moved compensation to Pay section. However we could keep it in About the role? Since we moved compensation to Pay, we might omit that line from About the role to avoid duplication. But we need to preserve all substantive information; we can put it in Pay section. So About the role will not include compensation line.
Thus About the role paragraph: "Clean Harbors is looking for a Regional Class A Tanker Driver to join their safety conscious team in Baltimore, MD! This route runs from Baltimore, MD to PA,VA and averages 60 hours per week. Weekly home time."
Now Pay section: Should include "Drivers average $90-$120K per year", "$7,500 sign-on-bonus available", "Compensation includes hourly wages (all on-duty non-driving time)". Also maybe mention that final compensation may vary etc but that's boilerplate; we should remove boilerplate like "The posted salary range reflects the minimum and maximum target for this role..." etc. So keep only substantive: salary range, sign-on bonus, compensation includes hourly wages.
Now Benefits section: list:
- Comprehensive health benefits coverage after 30 days of full-time employment
- Group 401K with company matching component
- Own Part of the Company with our Employee Stock Purchase Plan
- Paid time off
- Company paid training
- Tuition reimbursement
- Positive and safe work environments
Also "Health and Safety is our #1 priority and we live it 3-6-5!" That's a statement about health and safety priority; could be included as prose in Benefits or maybe as a separate statement. It's part of "Why work for Clean Harbors?" So we can include as a paragraph: "Health and Safety is our #1 priority and we live it 3-6-5!"
Now Responsibilities list:
- Ensures that Health and Safety is the number one priority by complying with all safe work practices, policies, and processes and acting in a safe manner at all times
- Operates tractor trailer tanker units
- Adheres to weights and ensures proper utilization of the units
- Ensures proper loading and unloading of hazardous waste/non-hazardous waste; Properly secures the loads
- Placards vehicle in accordance to Company and Department of Transportation (DOT) requirements/regulations
- Maintains daily logs, time sheets, expense reports, dispatch and trip reports as well as vehicle inspection reports
Now Qualifications list:
- Class A CDL
- Minimum 12 months of Class A driving experience
- Minimum 3 months of tanker experience
- HAZMAT and Tanker endorsements
- Ability to climb and work from heights
- Ability to lift and carry 50 lbs or more
- Ability to effectively use required technology such as mobile applications and computer software
Now we need to ensure we didn't miss any substantive info: The posting also mentions "For additional information about driver career opportunities, please call us at 72-Drive (833-723-7483)." That's contact info; maybe we could include as a short paragraph under About the role or separate? It's not a heading; it's contact info. Should we keep? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." Contact info is minor metadata; we could fold into a short
maybe under About the role or at end. But they said remove boilerplate, duplicated lines, and application instructions. Contact info is not exactly application instructions but could be considered contact for more info. Might be okay to keep as a short p. However they said "remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Contact info is not those. I'd keep it as a short paragraph maybe under About the role or after sections. But we need to preserve ALL substantive information. Contact info is substantive for someone wanting to apply. So we should keep it. We could add a
after sections: "For additional information about driver career opportunities, please call us at 72-Drive (833-723-7483)." Now also there is EEO statements etc; we remove those. Now ensure we don't create empty sections. Now produce HTML fragment. Structure:
About the role
Clean Harbors is looking for a Regional Class A Tanker Driver to join their safety conscious team in Baltimore, MD! This route runs from Baltimore, MD to PA,VA and averages 60 hours per week. Weekly home time.
For additional information about driver career opportunities, please call us at 72-Drive (833-723-7483).
Responsibilities
- ... ...
Qualifications
-
...
Benefits
Health and Safety is our #1 priority and we live it 3-6-5!
- Comprehensive health benefits coverage after 30 days of full-time employment
- Group 401K with company matching component
- Own Part of the Company with our Employee Stock Purchase Plan
- Paid time off
- Company paid training
- Tuition reimbursement
- Positive and safe work environments
Pay
Drivers average $90-$120K per year.
$7,500 sign-on-bonus available.
Compensation includes hourly wages (all on-duty non-driving time).
We could combine Pay into a singlebut separate is fine. Check for any missing: The posting also mentions "Own Part of the Company with our Employee Stock Purchase Plan" we have. Now ensure no duplication: We didn't include "Health and Safety is our #1 priority..." in Responsibilities (first bullet mentions ensuring health and safety priority). That's okay. Now ensure we didn't include boilerplate like "Clean Harbors is an equal opportunity employer." etc. We removed. Now output