Dockworker
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. Remove boilerplate: EEO, navigation, cookie, legal, application instructions. Also remove duplicated lines.
We need to parse the posting.
Content:
- Intro about Roadtex Transportation: description of company, acquisition, etc. That could be "About the role"? Actually "About the role" is about the job, not company. But we can use "About the role" heading for overview of position. The posting includes "Position Overview" paragraph: "To perform this job, a forklift driver must be familiar with the forklift's controls and capabilities. They should also have strong attention to detail, be able to work independently or as part of a team, and have good communication skills. Additionally, physical strength and stamina may be required as the job may involve lifting and moving heavy materials and goods."
That's about the role. So we can put that under About the role
with
. - Job Duties & Responsibilities: list of duties. Should be under
Responsibilities
with- .
- Requirements: list of requirements. Could be under
Requirements
with- . Also there is "Physical Requirements" which could be part of Requirements or separate. The instruction says we can have sections like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what to include. The posting includes "Requirements" bullet list: at least 3 months forklift experience, high school diploma or GED, ability to pass internal Forklift Certification Training, able to perform job tasks in sometimes dusty, hot and/or cold working conditions. Then "Physical Requirements" list: speak/hear, stand, lift up to 50lbs, occasionally up to 65lbs with team lifting, capability to perform physical activities requiring arms, legs, whole body, bending, crouching, climbing, using steps and ladders, pushing pulling, stooping and reaching.
We could combine both under Requirements, or split into Requirements and Physical Requirements (but we don't have a heading for Physical Requirements; we could put under Requirements). Also there is "Qualifications" maybe overlapping; but we can treat the education/experience as Qualifications. However we have both Requirements and Qualifications sections possible. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine into one Requirements section that includes both experience/education and physical requirements. Or we could have Requirements and Qualifications separate if content distinct. Let's see: The posting has a "Requirements" heading with bullet points (experience, education, certification, conditions). Then a separate "Physical Requirements" heading with bullet points. That suggests two sub-sections. But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could map "Requirements" to the first bullet list, and "Qualifications" to the physical requirements? Or we could treat physical requirements as part of Requirements. Since we want few sections, maybe combine into Requirements.
Also there is "Benefits" section: "For more information about our benefit offerings, please visit our careers page at https://www.echo.com/company/careers." That's not specific benefit details, just a link. The instruction: never create Benefits section unless posting actually states them. It does state benefit offerings but only says to visit page for more info. That's not specific benefit details. Should we include? The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits exist, but no detail. It's vague. I'd argue it's not substantive detail; we should omit Benefits section because no specific benefits listed. However the instruction says "Prefer a few substantive sections over many thin ones." So we skip Benefits.
Pay and Schedule: not mentioned, so omit.
Skills: not explicitly listed; maybe implied but not explicit. So omit.
Qualifications: we could treat the education/experience as Qualifications, but we already have Requirements. Might be redundant. Let's decide to have sections: About the role, Responsibilities, Requirements (including experience, education, certification, conditions, physical requirements). That's three sections.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all bullet points exactly as given (or close). We must not add extra info not present.
We need to format lists with
- . For prose, use
. We must not include boilerplate: EEO statement, navigation, cookie, legal, application instructions. The posting includes EEO statement at end: "All qualified applicants will receive consideration for employment without regard to ..." That's boilerplate; we must remove it. Also the intro about Roadtex Transportation: that's company description, not about the role. Should we include it? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The company description is substantive but not part of the job posting sections we have headings for. Could we include it as a paragraph before any heading? The instruction says output only HTML fragment, no /. It didn't forbid adding a
for company overview before headings. However the instruction about headings: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It didn't say we cannot have other headings or paragraphs outside those sections. But likely they expect we only use those headings for sections; we can have a
for company overview before the first heading. However the instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are the allowed headings for sections. It didn't forbid other content. But to be safe, we could incorporate company overview into About the role section? But About the role is supposed to be about the job, not company. However we could include company overview as part of About the role? Might be stretching. Better: we can include a
before the first heading that describes the company. The instruction didn't forbid that. It only said use
for section headings (list). It didn't say we cannot have other elements. So we can have a
for company overview, then
About the role
etc. But we must not repeat the job title as a heading. The job title is likely "Forklift Driver". Not present as heading; fine. We must not put Job ID/requisition numbers as headings; none present. Now, let's extract content. Company overview paragraph: "Roadtex Transportation has become a leader in the nationwide LTL industry, specializing in transporting time and temperature-sensitive products. We handle refrigerated and LTL needs by leveraging no sailing schedules, our nationwide network of 32 strategically placed temperature-controlled facilities, our state-of-the-art tracking, and our specialized equipment and warehousing capabilities. In 2022, Roadtex was acquired by Echo Global Logistics. The acquisition brings a truckload brokerage and expanded transportation management solutions to Roadtex's customers while providing Echo with our national warehouse footprint and advanced temperature-controlled transportation solutions." That's all. Position Overview paragraph: "To perform this job, a forklift driver must be familiar with the forklift's controls and capabilities. They should also have strong attention to detail, be able to work independently or as part of a team, and have good communication skills. Additionally, physical strength and stamina may be required as the job may involve lifting and moving heavy materials and goods." Job Duties & Responsibilities bullet list: - Inspecting the forklift before use to ensure it is in proper working condition. - Loading and unloading materials and goods onto and off trucks, trailers, or storage areas using the forklift. - Maintaining inventory records and reporting any discrepancies to management. - Ensuring that the forklift is always operated in a safe and responsible manner - Maintaining the cleanliness and organization of the work area. - Reporting any forklift malfunctions or maintenance needs to management - Assisting with other warehouse tasks as needed Note some lines missing period; we keep as is. Requirements bullet list (under Requirements heading): - At least 3 months forklift experience and/or using warehouse distribution equipment - High school diploma or GED, or equivalent combination of education, training, and experience - Ability to successfully pass internal Forklift Certification Training and demonstrate safety procedures - Able to perform job tasks in sometimes dusty, hot and/or cold working conditions Physical Requirements bullet list (we'll include under same Requirements section maybe as sublist? But we need to preserve all info. Could make a nested list? Better to keep as separate- under same heading but maybe add a
- for any list of duties/requirements/benefits. So we can have multiple lists.
We'll output:
About the role
To perform this job, a forklift driver must be familiar with the forklift's controls and capabilities. They should also have strong attention to detail, be able to work independently or as part of a team, and have good communication skills. Additionally, physical strength and stamina may be required as the job may involve lifting and moving heavy materials and goods.
But we also have company overview; maybe we put that before About the role as a. Let's decide: We'll put company overview as a
before the first heading. Then
Responsibilities
with- for duties.
Then
Requirements
with twomaybe: one for general requirements, one for physical requirements. Or we can combine into one list with all items. But physical requirements are distinct; we could add a
Physical Requirements:
then- .
We must not invent headings like "Physical Requirements". So we can just add a
- for lists.
Let's craft:
Roadtex Transportation has become a leader in the nationwide LTL industry, specializing in transporting time and temperature-sensitive products. We handle refrigerated and LTL needs by leveraging no sailing schedules, our nationwide network of 32 strategically placed temperature-controlled facilities, our state-of-the-art tracking, and our specialized equipment and warehousing capabilities. In 2022, Roadtex was acquired by Echo
Physical Requirements:
then list. Now check for any duplicated lines: The posting had "Maintaining the cleanliness and organization of the work area." and "Reporting any forklift malfunctions or maintenance needs to management". No duplicates. Now ensure we removed EEO statement and benefits link? Benefits line: "For more information about our benefit offerings, please visit our careers page at https://www.echo.com/company/careers." This is not specific benefit details; we should omit Benefits section. Should we keep that sentence? It's about benefits but vague. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits exist but only references external page. I'd say we should not create a Benefits section; we could optionally include that sentence as aunder something else? But it's not a duty/requirement. It's basically a pointer. It's not substantive detail about the job. I'd omit it entirely. Now check for any other boilerplate: "All qualified applicants will receive consideration for employment without regard to race, color, religion, sex, sexual orientation, gender identity, national origin, status as a qualified individual with a disability, or Vietnam era or other protected veteran." Remove. Now output HTML fragment. We need to ensure proper nesting:
for prose,
- for lists.
Let's craft:
- for duties.
Then
label "Physical Requirements:" then list. However instruction: Use
- for any list of duties/requirements/benefits. So we can have multiple lists.
We'll output:
- . For prose, use
- . Also there is "Physical Requirements" which could be part of Requirements or separate. The instruction says we can have sections like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what to include. The posting includes "Requirements" bullet list: at least 3 months forklift experience, high school diploma or GED, ability to pass internal Forklift Certification Training, able to perform job tasks in sometimes dusty, hot and/or cold working conditions. Then "Physical Requirements" list: speak/hear, stand, lift up to 50lbs, occasionally up to 65lbs with team lifting, capability to perform physical activities requiring arms, legs, whole body, bending, crouching, climbing, using steps and ladders, pushing pulling, stooping and reaching.
We could combine both under Requirements, or split into Requirements and Physical Requirements (but we don't have a heading for Physical Requirements; we could put under Requirements). Also there is "Qualifications" maybe overlapping; but we can treat the education/experience as Qualifications. However we have both Requirements and Qualifications sections possible. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine into one Requirements section that includes both experience/education and physical requirements. Or we could have Requirements and Qualifications separate if content distinct. Let's see: The posting has a "Requirements" heading with bullet points (experience, education, certification, conditions). Then a separate "Physical Requirements" heading with bullet points. That suggests two sub-sections. But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could map "Requirements" to the first bullet list, and "Qualifications" to the physical requirements? Or we could treat physical requirements as part of Requirements. Since we want few sections, maybe combine into Requirements.
Also there is "Benefits" section: "For more information about our benefit offerings, please visit our careers page at https://www.echo.com/company/careers." That's not specific benefit details, just a link. The instruction: never create Benefits section unless posting actually states them. It does state benefit offerings but only says to visit page for more info. That's not specific benefit details. Should we include? The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits exist, but no detail. It's vague. I'd argue it's not substantive detail; we should omit Benefits section because no specific benefits listed. However the instruction says "Prefer a few substantive sections over many thin ones." So we skip Benefits.
Pay and Schedule: not mentioned, so omit.
Skills: not explicitly listed; maybe implied but not explicit. So omit.
Qualifications: we could treat the education/experience as Qualifications, but we already have Requirements. Might be redundant. Let's decide to have sections: About the role, Responsibilities, Requirements (including experience, education, certification, conditions, physical requirements). That's three sections.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all bullet points exactly as given (or close). We must not add extra info not present.
We need to format lists with