Driver Non CDL

We need to output HTML fragment with sections: h3 headings for sections present: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. We need to parse the job posting. Let's extract content. Job description includes: - Position Overview: "We are looking for an experienced Driver to join our team in Kent, WA and service the Seattle route. If you have reliable transportation, a strong work ethic, and experience with multi-stop delivery routes, we'd love to hear from you. Apply today and become part of our growing team! Excellent starting wage and benefits package, including 401k with company match and profit sharing!" - Essential Functions (list of duties): - Ability to load, secure and unload product safely, and maintain a route schedule - Receive and provide appropriate documentation for the delivery of goods to ensure timely service - Demonstrated communication and customer service skills - Accurate handling of CODs, delivery manifests - Vehicle inspection, both pre- and post-delivery, compliance with all federal and state regulations - Excellent attendance and reliability are critical - With minimal supervision, demonstrated ability to solve practical problems - Hazmat training a plus - Required Qualifications: - High school diploma or equivalent with prior delivery experience - Medical examiner's certificate and the ability to have and maintain a satisfactory driving record within company policy limits - Must be able to become certified through OSHA in the following areas: Basic Hazmat, Driver Specific Hazmat, and Security Awareness - CDL preferred but not required - Must be able to lift up to 75lbs - Working Conditions (physical demands): - While performing the duties of this job, the employee is frequently required to sit, stand, walk, bend, stoop, balance and use arms and hands to reach, pull, push, clasp and move a variety of materials. - The employee must lift and/or move up to 50 pounds occasionally and up to 20 lbs frequently. - Pay: "The anticipated pay range for this position is $26.00. The actual base pay offered will vary depending on multiple factors including job-related knowledge/skills, relevant experience, business needs, and geographic location. At Brunswick, it is not typical for an individual to be hired at or near the top end of the salary range for their role. Compensation decisions are dependent upon the specifics of the candidate’s qualifications and the business context." - Benefits: "This position is eligible to participate in Brunswick's comprehensive and high-quality benefits offerings, including medical, dental, vision, paid vacation, 401k (up to 4% match), Health Savings Account (with company contribution), wellbeing program, product purchase discounts, and much more. Details about our benefits can be found here." Also later: "We offer valuable benefits including a competitive 401(k) plan with company match, health benefits, paid time off, a robust Wellness Program, and much more." - Schedule: Not explicitly mentioned. No schedule info. So we should not include Schedule heading. - Skills: Not explicitly listed separate; maybe we can infer from duties but we should not invent. The posting mentions communication and customer service skills, problem solving, etc. Could be considered Skills. But we need to decide if we have a Skills section. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says we can use those headings if content exists. We have content for Responsibilities (Essential Functions). We have Requirements (maybe same as Qualifications?). There's also "Required Qualifications". Could map to Qualifications. There's also "About the role" maybe from Position Overview. There's Benefits, Pay. There's no explicit Skills but we could extract skills like communication, customer service, problem solving, etc. However we must not invent or summarize away detail; we can list those as skills if they appear explicitly. The posting includes: "Demonstrated communication and customer service skills", "demonstrated ability to solve practical problems". Those are skills. So we could create a Skills section with those bullet points. But we need to ensure we don't create a heading with filler. If we have at least one bullet, it's okay. We also need to avoid repeating job title as heading. Not needed. We need to remove boilerplate: EEO, legal, etc. Also remove duplicated lines, navigation, cookie, application instructions. We must preserve all substantive information. We need to output only HTML fragment, no /, no markdown fences. Thus produce something like:

About the role

We are looking for an experienced Driver to join our team in Kent, WA and service the Seattle route. If you have reliable transportation, a strong work ethic, and experience with multi-stop delivery routes, we'd love to hear from you. Apply today and become part of our growing team! Excellent starting wage and benefits package, including 401k with company match and profit sharing!

Responsibilities

• Ability to load, secure and unload product safely, and maintain a route schedule
• Receive and provide appropriate documentation for the delivery of goods to ensure timely service
• Demonstrated communication and customer service skills
• Accurate handling of CODs, delivery manifests
• Vehicle inspection, both pre- and post-delivery, compliance with all federal and state regulations
• Excellent attendance and reliability are critical
• With minimal supervision, demonstrated ability to solve practical problems
• Hazmat training a plus

Qualifications

• High school diploma or equivalent with prior delivery experience
• Medical examiner's certificate and the ability to have and maintain a satisfactory driving record within company policy limits
• Must be able to become certified through OSHA in the following areas: Basic Hazmat, Driver Specific Hazmat, and Security Awareness
• CDL preferred but not required
• Must be able to lift up to 75lbs

Skills

• Demonstrated communication and customer service skills
• Demonstrated ability to solve practical problems

But note that communication and customer service skills already appear in Responsibilities; we might duplicate. Better to avoid duplication. Perhaps we can keep Skills separate for other skills not covered: maybe problem solving. But communication already listed. Could still include but duplication may be okay? The instruction: preserve ALL substantive information; do not invent or summarize away detail. Duplication is not prohibited but might be redundant. However we could keep Skills as separate but we might just omit Skills if we feel it's covered. However we have explicit skill statements: "Demonstrated communication and customer service skills" and "demonstrated ability to solve practical problems". Those are skills. We could put them under Skills and not duplicate in Responsibilities. But Responsibilities already includes those as bullet points. If we move them to Skills, we would lose them from Responsibilities unless we keep them there too. The instruction: preserve ALL substantive information; we can keep them in both places, but that's duplication but still preserving. Might be okay but could be considered redundant. However better to keep them only once. Let's think: Responsibilities section is for duties/functions. Skills section is for abilities/skills. The communication and customer service skills could be considered a skill, but also a responsibility (demonstrated communication and customer service skills). The posting lumps them under Essential Functions. So maybe we keep them under Responsibilities and not create a separate Skills section unless there are other skills not covered. There's also "demonstrated ability to solve practical problems" which is also a skill but could be considered a responsibility (problem solving). So maybe we don't need a Skills section. The instruction says "Prefer a few substantive sections over many thin ones." So we could omit Skills if not needed. Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay. We also have Working Conditions (physical demands). That could be considered part of Responsibilities or a separate section like "Working Conditions". Not in the list of allowed headings but we could treat as Responsibilities? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No Working Conditions. So we need to fit that content somewhere. Could be under Responsibilities as additional bullet points. Or under Qualifications? Probably Responsibilities is fine: we can add bullet points about physical demands. Thus Responsibilities bullets will include the physical demands. Let's extract physical demands bullet points: - While performing the duties of this job, the employee is frequently required to sit, stand, walk, bend, stoop, balance and use arms and hands to reach, pull, push, clasp and move a variety of materials. - The employee must lift and/or move up to 50 pounds occasionally and up to 20 lbs frequently. We can add those as bullets. Now Benefits: we have details. Pay: we have anticipated pay range $26.00, actual base pay varies, not typical to hire at top end. We should not include fluff like "commensurate with experience". The posting includes "The actual base pay offered will vary depending on multiple factors...". That's substantive. We need to avoid boilerplate like EEO, legal, etc. Now produce HTML. Check for any duplicated lines: we should not repeat the same sentence multiple times. Ensure we only include each piece once. Let's compile: About the role: Position Overview paragraph. Responsibilities: list of essential functions + physical demands. Qualifications: Required Qualifications. Benefits: benefits description. Pay: pay range description. We might also include "About Land 'N' Sea" but that's company info not directly about the role; could be considered About the role? Might be extra but it's substantive about the company. However the instruction: "Preserve ALL substantive information". That includes company description? It's part of the posting but not about the role. However we might include it under About the role or maybe a separate section like "About the company". But allowed headings list does not include About the company. Could we include it under About the role? Might be okay to add a paragraph about Land 'N' Sea. But the instruction says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive; we could add other headings if needed? It says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are the expected headings; we should stick to those. So we should not add other headings like About Land 'N' Sea. We could incorporate that info into About the role paragraph maybe as a brief note. But we must preserve all substantive information; if we omit it, we lose info. However maybe it's considered boilerplate? It's a description of a subsidiary; could be considered relevant to the role? It's not directly about the job but could be considered company background. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not those. So we should keep it. But we lack a heading for it. Perhaps we can add a paragraph under About the role after the position overview. That would preserve it. Thus About the role will have two paragraphs: first about position overview, second about Land 'N' Sea description. Now Benefits: we have two paragraphs about benefits; we can combine. Pay: we have paragraph. Now ensure we don't include any filler like "Much more". That's okay. Now produce HTML. Check for any remaining boilerplate: EEO lines, privacy policies, etc. Remove. Let's