Commercial Driver
JELD-WEN, Inc. · Oceanside, CA · 1 mo ago
Manufacturing$32.83–$36.28/hrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the posting.
- About the role: The "Purpose of the Role" paragraph: "The key role of the Commercial Delivery Driver is to deliver high quality custom windows and doors to our valued customers, putting safety first and adhering to DOT rules and regulations. This job operates in a combination of outdoor, fair-weather, windy, rainy conditions and a warehouse environment consisting of a manufacturing setting. This role routinely uses a commercial vehicle with a 35000 GVWR and a Princeton Piggyback or Donkey. While performing the duties of this job, the employee is frequently exposed to fumes or airborne particles, moving mechanical parts, vibration and outdoor weather elements. The noise level in the work environment can be loud."
That is substantive. So we can have . There's duplication: "Communicate eta with customers when requested." appears twice. We should preserve all substantive info but we can deduplicate? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is present in source; we could keep both but it's redundant. Might be okay to keep both but better to keep unique? The instruction doesn't say to deduplicate, but preserving all substantive info includes duplicates; removing duplicates could be considered summarizing away detail? It's not summarizing, it's removing duplicate lines which are identical. Might be okay but safer to keep both? However duplicates add no new info; but they are still substantive? They are same info repeated. I'd keep one instance to avoid filler. I think it's acceptable.
List items:
- To ensure adherence with all compliance standards and operate with integrity at all times.
- Pre-trip truck & forklift daily.
- Maintain cleanliness of the interior and exterior of the truck.
- Fuel truck with assigned fuel card.
- Assist warehouse forklift drivers with pre-loading truck for next day deliveries.
- Audit delivery order on the truck prior to leaving the yard for load accuracy.
- Communicate eta with customers when requested.
- Complete delivery receipts with accuracy and required customer and driver signatures.
- Deliver customer orders on time in full and accurately.
- Manages complex situations, such as unplanned re-routes and confined spaces.
- Plan and organize route to complete deliveries and pickups with efficiency.
- Warehouse work as needed.
- Performs all other duties as assigned.
Also there is "Communicate ETA with customers when requested." duplicate; we have one.
- Requirements: The "Required Qualifications" list. We'll treat as Requirements section.
List:
- Minimum one year of Class A or B driving experience.
- Must have current and unrestricted CDL license.
- Princeton Piggyback, Donkey or Moffett experience preferred.
- Understanding and knowledge of DOT rules and regulations.
- Knowledge of windows & doors products a plus.
- Clean DMV report.
- Good communication skills.
- Ability to plan and organize with efficiency.
- Ability to complete paperwork with accuracy.
- Good attendance history.
- Positive attitude with the ability to contribute to a team atmosphere.
- Must be fluent in both written and spoken English.
- A second language is preferred, but not essential.
- Qualifications: Might be overlapping with Requirements; but we could combine? The instruction says use headings for sections like Qualifications. The posting has "Required Qualifications". That could be considered Qualifications. We could put that under Qualifications. But we also have "Required Qualifications" as a list; we could treat that as Qualifications. Then Requirements maybe empty? However we also have "Physical Demands" which could be considered Requirements? But we have no separate Requirements heading besides that. The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we need to decide which content goes where.
We have:
- About the role: purpose paragraph.
- Responsibilities: key responsibilities list.
- Requirements: maybe the "Required Qualifications" list? Or we could split: Requirements = mandatory items (minimum one year experience, CDL license, etc.) Qualifications = preferred items (Princeton Piggyback experience, knowledge of windows & doors a plus, second language preferred). But the instruction says prefer a few substantive sections over many thin ones. So maybe combine into one Qualifications section. But we have both Requirements and Qualifications as possible headings; we need to include a section only when posting has real specific content for it. We could put all under Qualifications and skip Requirements. Or we could put under Requirements and skip Qualifications. Which is more appropriate? The posting says "Required Qualifications". That's a heading. So we could map that to Qualifications section. Then we could have Requirements empty -> omit. So we will have Qualifications section with that list.
- Skills: The posting mentions "Good communication skills.", "Ability to plan and organize with efficiency.", "Ability to complete paperwork with accuracy.", "Positive attitude...". Those could be skills. But we already have them in Qualifications list. Might be redundant. Better to keep Qualifications as is and not create Skills unless there is distinct skill list. There's no separate skills list. So we omit Skills.
- Benefits: The posting has "What We Offer" paragraph with benefits: medical, dental, vision, basic life insurance, up to 15 days vacation, ten paid holidays, 401k, Prescription Drug Plan, FSA, HRA, EAP, Tuition Reimbursement, Employee Discount Program. That's substantive. So we create Benefits section with
About the role
withcontaining that. - Responsibilities: The "Key Responsibilities" bullet list. We need to extract each bullet as
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we need to decide which content goes where.
We have:
- About the role: purpose paragraph.
- Responsibilities: key responsibilities list.
- Requirements: maybe the "Required Qualifications" list? Or we could split: Requirements = mandatory items (minimum one year experience, CDL license, etc.) Qualifications = preferred items (Princeton Piggyback experience, knowledge of windows & doors a plus, second language preferred). But the instruction says prefer a few substantive sections over many thin ones. So maybe combine into one Qualifications section. But we have both Requirements and Qualifications as possible headings; we need to include a section only when posting has real specific content for it. We could put all under Qualifications and skip Requirements. Or we could put under Requirements and skip Qualifications. Which is more appropriate? The posting says "Required Qualifications". That's a heading. So we could map that to Qualifications section. Then we could have Requirements empty -> omit. So we will have Qualifications section with that list.
- Skills: The posting mentions "Good communication skills.", "Ability to plan and organize with efficiency.", "Ability to complete paperwork with accuracy.", "Positive attitude...". Those could be skills. But we already have them in Qualifications list. Might be redundant. Better to keep Qualifications as is and not create Skills unless there is distinct skill list. There's no separate skills list. So we omit Skills.
- Benefits: The posting has "What We Offer" paragraph with benefits: medical, dental, vision, basic life insurance, up to 15 days vacation, ten paid holidays, 401k, Prescription Drug Plan, FSA, HRA, EAP, Tuition Reimbursement, Employee Discount Program. That's substantive. So we create Benefits section with - items.
- Pay: The posting says "Expected pay for this role is between $32.83 to $36.28 per hour and is based on experience and qualifications." That's specific. So we create Pay section with
containing that.
- Schedule: The posting mentions "Shift (if applicable): Day Shift". That's schedule info. So we create Schedule section with
containing that.
We also have location and department info; but those are metadata; we could fold into a short
under About the role or maybe separate? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we could include location/department/shift in a short paragraph maybe under About the role or separate? But we already have Schedule section for shift. Location could be included in About the role? Might be better to add a short
after About the role for location/department. But we must not create extra headings. We could add a
with "Location: Onsite- Oceanside, CA. Department/Team: Logistics / Shipping Department." That's minor metadata. We'll include that as a paragraph after About the role.
Now we need to output only HTML fragment, no /, no markdown.
Structure:
About the role
... purpose paragraph ...
Location: Onsite- Oceanside, CA. Department/Team: Logistics / Shipping Department.
Responsibilities
- ...
...
Qualifications
- ...
...
Benefits
- ...
...
Pay
Expected pay for this role is between $32.83 to $36.28 per hour and is based on experience and qualifications.
Schedule
Day Shift.
Check for any other sections: maybe "Physical Demands" could be considered Requirements but we omitted Requirements. Could we add a Requirements section for physical demands? The posting has "Physical Demands" paragraph. That is substantive. We could create a Requirements section for that. But we already have Qualifications covering required qualifications. Physical demands are more like job demands; could be considered Requirements. The instruction says include a section only when posting has real specific content for it. So we could add a Requirements section with physical demands. That would be appropriate. Then we would have both Requirements and Qualifications sections.
Let's do that: Requirements section for Physical Demands.
Physical Demands paragraph: "This position is very active and requires driving, standing, walking, bending, kneeling, stooping, crouching, crawling, and climbing all dayMust be able to frequently lift and / or move items over 50 pounds. Specific vision abilities required by this job include close vision, distance vision, colour vision, peripheral vision, depth perception and ability to adjust focus."
We need to format as maybe.
Thus we will have:
Requirements
This position is very active and requires driving, standing, walking, bending, kneeling, stooping, crouching, crawling, and climbing all day. Must be able to frequently lift and/or move items over 50 pounds. Specific vision abilities required by this job include close vision, distance vision, colour vision, peripheral vision, depth perception and ability to adjust focus.
Now Qualifications section for Required Qualifications list.
Now Benefits section as described.
Now Pay and Schedule.
Now we need to ensure we didn't miss any substantive info: The "About JELD-WEN Holding, Inc." paragraph is company overview; could be considered About the role? But we already have About the role for purpose. The company overview is extra but could be considered About the role? Might be considered "About the company". Not in headings list. Could we add a section "About the company"? Not in allowed headings. So we could fold into About the role paragraph? Might be too much. The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings but says use those for section headings. It doesn't say we cannot add other headings, but we should follow the pattern. Probably better to keep only those headings. The company overview could be considered part of About the role? Not really. But we could include it as a paragraph under About the role after purpose. That would be okay: About the role could include both purpose and company overview. However the purpose is about the role; company overview is about the employer. Might be okay to include.
But we already have a short metadata paragraph for location/department. We could add company overview after that.
Thus About the role will have two paragraphs: purpose and company overview.
Let's extract company overview paragraph: "JELD-WEN Holding, Inc. (NYSE: JELD) is a leading global designer, manufacturer and distributor of high-performance interior and exterior doors, windows, and related building products serving the new construction and repair and remodeling sectors. Based in Charlotte, North Carolina, the company operates across North America and Europe. Our associates are dedicated to bringing beauty and security to the spaces that touch our lives through our market-leading product brands across the world. The JELD-WEN family of brands includes JELD-WEN® worldwide, LaCantina® and VPI™ in North America, and Swedoor® and DANA® in Europe. For more information, visit corporate.JELD-WEN.com or follow LinkedIn. JELD-WEN has been named by Forbes as one of ‘America’s Best Employers’ and by Newsweek as one of the ‘World’s Most Trustworthy Companies’."
We'll include that as a
.
Now Benefits list: need to itemize each benefit.
From text: "Employees (and their families) are covered by medical, dental, vision, and basic life insurance. Employees will accrue up to 15 days’ vacation leave annually and receive ten paid holidays throughout the calendar year. Employees can also enroll in the following company benefit programs including, 401k Retirement Savings Plan,
containing that. - Schedule: The posting mentions "Shift (if applicable): Day Shift". That's schedule info. So we create Schedule section with
containing that. We also have location and department info; but those are metadata; we could fold into a short
under About the role or maybe separate? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we could include location/department/shift in a short paragraph maybe under About the role or separate? But we already have Schedule section for shift. Location could be included in About the role? Might be better to add a short
after About the role for location/department. But we must not create extra headings. We could add a
with "Location: Onsite- Oceanside, CA. Department/Team: Logistics / Shipping Department." That's minor metadata. We'll include that as a paragraph after About the role. Now we need to output only HTML fragment, no /, no markdown. Structure:
About the role
... purpose paragraph ...
Location: Onsite- Oceanside, CA. Department/Team: Logistics / Shipping Department.
Responsibilities
- ... ...
Qualifications
- ... ...
Benefits
- ... ...
Pay
Expected pay for this role is between $32.83 to $36.28 per hour and is based on experience and qualifications.
Schedule
Day Shift.
Check for any other sections: maybe "Physical Demands" could be considered Requirements but we omitted Requirements. Could we add a Requirements section for physical demands? The posting has "Physical Demands" paragraph. That is substantive. We could create a Requirements section for that. But we already have Qualifications covering required qualifications. Physical demands are more like job demands; could be considered Requirements. The instruction says include a section only when posting has real specific content for it. So we could add a Requirements section with physical demands. That would be appropriate. Then we would have both Requirements and Qualifications sections. Let's do that: Requirements section for Physical Demands. Physical Demands paragraph: "This position is very active and requires driving, standing, walking, bending, kneeling, stooping, crouching, crawling, and climbing all dayMust be able to frequently lift and / or move items over 50 pounds. Specific vision abilities required by this job include close vision, distance vision, colour vision, peripheral vision, depth perception and ability to adjust focus." We need to format asmaybe. Thus we will have:
Requirements
This position is very active and requires driving, standing, walking, bending, kneeling, stooping, crouching, crawling, and climbing all day. Must be able to frequently lift and/or move items over 50 pounds. Specific vision abilities required by this job include close vision, distance vision, colour vision, peripheral vision, depth perception and ability to adjust focus.
Now Qualifications section for Required Qualifications list. Now Benefits section as described. Now Pay and Schedule. Now we need to ensure we didn't miss any substantive info: The "About JELD-WEN Holding, Inc." paragraph is company overview; could be considered About the role? But we already have About the role for purpose. The company overview is extra but could be considered About the role? Might be considered "About the company". Not in headings list. Could we add a section "About the company"? Not in allowed headings. So we could fold into About the role paragraph? Might be too much. The instruction: "Usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings but says use those for section headings. It doesn't say we cannot add other headings, but we should follow the pattern. Probably better to keep only those headings. The company overview could be considered part of About the role? Not really. But we could include it as a paragraph under About the role after purpose. That would be okay: About the role could include both purpose and company overview. However the purpose is about the role; company overview is about the employer. Might be okay to include. But we already have a short metadata paragraph for location/department. We could add company overview after that. Thus About the role will have two paragraphs: purpose and company overview. Let's extract company overview paragraph: "JELD-WEN Holding, Inc. (NYSE: JELD) is a leading global designer, manufacturer and distributor of high-performance interior and exterior doors, windows, and related building products serving the new construction and repair and remodeling sectors. Based in Charlotte, North Carolina, the company operates across North America and Europe. Our associates are dedicated to bringing beauty and security to the spaces that touch our lives through our market-leading product brands across the world. The JELD-WEN family of brands includes JELD-WEN® worldwide, LaCantina® and VPI™ in North America, and Swedoor® and DANA® in Europe. For more information, visit corporate.JELD-WEN.com or follow LinkedIn. JELD-WEN has been named by Forbes as one of ‘America’s Best Employers’ and by Newsweek as one of the ‘World’s Most Trustworthy Companies’." We'll include that as a
. Now Benefits list: need to itemize each benefit. From text: "Employees (and their families) are covered by medical, dental, vision, and basic life insurance. Employees will accrue up to 15 days’ vacation leave annually and receive ten paid holidays throughout the calendar year. Employees can also enroll in the following company benefit programs including, 401k Retirement Savings Plan,