Seasonal Delivery Driver
The Honey Baked Ham Company, LLC · Grand Rapids, MI · 1 mo ago
On-siteCustomer ServicePart-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. Remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines. Keep all substantive info.
Let's parse the posting.
Content:
- Intro: "#16-011 Job Description Join the #HamFam for a seasonal gig! After over 60 years in business, we're still deeply committed to Making Meals Memorable. We're the home of The World's Best Ham™, and the secret to our success isn't a secret at all--it's our people. We're a high performance team committed to being authentic in everything we do and to living our Values in full view of the communities we serve. We have an entrepreneurial spirit that's brought us a lot of success and we're looking for a Seasonal Delivery Driver to join our team - these roles deliver our awesome HoneyBaked products from our hub store to our Pop-Up Retail locations in grocery stores and/or malls in the local area. If you're uber tired and need a lyft, come to HoneyBaked - we offer truly flexible scheduling, so you can work around school/family/other commitments! HoneyBaked's seasonal positions could be the perfect seasonal side gig! You'll find a great culture at HoneyBaked. Serve Others and Do The Right Thing are core values for us - we believe in being authentic in all that we do and in living our Values in full view of the community we serve."
That's about the role/company.
- "What You'll Do" list: bullet points.
- "YOUR TRACK RECORD" list: requirements.
- "What We Offer": bullet points.
- "GET TO KNOW US": link to YouTube channel.
- "Other Things To Know": physical demands.
- EEO boilerplate: remove.
- Also note: "Job ID #16-011" maybe minor metadata; we can fold into short p or drop.
We need sections: About the role (maybe intro), Responsibilities (What You'll Do), Requirements (YOUR TRACK RECORD), Qualifications? Could be same as Requirements? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which sections have content.
We have:
- About the role: intro paragraph about company and role.
- Responsibilities: the "What You'll Do" list.
- Requirements: the "YOUR TRACK RECORD" list (ability to operate truck, license, DOT medical, etc.)
- Qualifications: maybe overlapping with Requirements; but we could treat Requirements as qualifications. However we need to avoid thin sections. Could combine Requirements and Qualifications into one? But we must follow instruction: use headings for those categories if we have content. If we have content for both, we could split but ensure not thin. Let's see if we have distinct qualifications beyond requirements: maybe "At least 21 years of age", "CDL not required". Those are requirements. Could treat them as Qualifications. But we have also "Ability to safety operate a 14 ft. to 26 ft. refrigerated truck for local deliveries", "Have a valid driver's license and current DOT medical card", "Ability to pass a pre-employment DOT drug screen, MVR check and DOT background", "Have knowledge of current DOT requirements". Those are requirements/qualifications. Could put them under Requirements. Qualifications maybe not needed.
- Skills: maybe not explicitly listed; we could infer but not invent. So skip Skills.
- Benefits: "What We Offer" includes Competitive pay, Fun and casual environment, Flexible hours, Associate discounts on our fantastic products, along with a free ham or turkey breast at the completion of your holiday schedule (a gift card may be substituted, depending on product availability). Also maybe "truly flexible scheduling" mentioned earlier. So we have Benefits.
- Pay: "Competitive pay" is mentioned but not specific amount. The instruction says: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Here we have "Competitive pay" which is vague but still states pay exists. Is that considered placeholder? It's not a specific number, but it's stating that pay is competitive. The instruction says avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". "Competitive pay" is somewhat vague but not exactly those. It's still a statement about pay. I'd say we can include Pay section with that phrase.
- Schedule: "truly flexible scheduling" and "flexible hours" mentioned. Also "If you're uber tired and need a lyft, come to HoneyBaked - we offer truly flexible scheduling, so you can work around school/family/other commitments!" and "What We Offer" includes Flexible hours. So we have schedule info.
- Also "Other Things To Know": physical demands (long hours, bending, stooping, standing, twisting, lifting up to 65 pounds). Could be part of Requirements or maybe a separate section like "Physical Demands". Not in list of headings; we could put under Requirements or maybe under a generic section but we only allowed those headings. Could incorporate into Requirements as additional requirement.
- "GET TO KNOW US": link to YouTube channel. Could be under About the role or maybe a separate section like "Learn More". Not in headings; we could put under About the role as a link.
We must not include boilerplate EEO etc.
We need to output only HTML fragment, no /, no markdown fences.
We'll produce something like:
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. Remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines. Keep all substantive info.
Let's parse the posting.
Content:
- Intro: "#16-011 Job Description Join the #HamFam for a seasonal gig! After over 60 years in business, we're still deeply committed to Making Meals Memorable. We're the home of The World's Best Ham™, and the secret to our success isn't a secret at all--it's our people. We're a high performance team committed to being authentic in everything we do and to living our Values in full view of the communities we serve. We have an entrepreneurial spirit that's brought us a lot of success and we're looking for a Seasonal Delivery Driver to join our team - these roles deliver our awesome HoneyBaked products from our hub store to our Pop-Up Retail locations in grocery stores and/or malls in the local area. If you're uber tired and need a lyft, come to HoneyBaked - we offer truly flexible scheduling, so you can work around school/family/other commitments! HoneyBaked's seasonal positions could be the perfect seasonal side gig! You'll find a great culture at HoneyBaked. Serve Others and Do The Right Thing are core values for us - we believe in being authentic in all that we do and in living our Values in full view of the community we serve."
That's about the role/company.
- "What You'll Do" list: bullet points.
- "YOUR TRACK RECORD" list: requirements.
- "What We Offer": bullet points.
- "GET TO KNOW US": link to YouTube channel.
- "Other Things To Know": physical demands.
- EEO boilerplate: remove.
- Also note: "Job ID #16-011" maybe minor metadata; we can fold into short p or drop.
We need sections: About the role (maybe intro), Responsibilities (What You'll Do), Requirements (YOUR TRACK RECORD), Qualifications? Could be same as Requirements? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which sections have content.
We have:
- About the role: intro paragraph about company and role.
- Responsibilities: the "What You'll Do" list.
- Requirements: the "YOUR TRACK RECORD" list (ability to operate truck, license, DOT medical, etc.)
- Qualifications: maybe overlapping with Requirements; but we could treat Requirements as qualifications. However we need to avoid thin sections. Could combine Requirements and Qualifications into one? But we must follow instruction: use headings for those categories if we have content. If we have content for both, we could split but ensure not thin. Let's see if we have distinct qualifications beyond requirements: maybe "At least 21 years of age", "CDL not required". Those are requirements. Could treat them as Qualifications. But we have also "Ability to safety operate a 14 ft. to 26 ft. refrigerated truck for local deliveries", "Have a valid driver's license and current DOT medical card", "Ability to pass a pre-employment DOT drug screen, MVR check and DOT background", "Have knowledge of current DOT requirements". Those are requirements/qualifications. Could put them under Requirements. Qualifications maybe not needed.
- Skills: maybe not explicitly listed; we could infer but not invent. So skip Skills.
- Benefits: "What We Offer" includes Competitive pay, Fun and casual environment, Flexible hours, Associate discounts on our fantastic products, along with a free ham or turkey breast at the completion of your holiday schedule (a gift card may be substituted, depending on product availability). Also maybe "truly flexible scheduling" mentioned earlier. So we have Benefits.
- Pay: "Competitive pay" is mentioned but not specific amount. The instruction says: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Here we have "Competitive pay" which is vague but still states pay exists. Is that considered placeholder? It's not a specific number, but it's stating that pay is competitive. The instruction says avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". "Competitive pay" is somewhat vague but not exactly those. It's still a statement about pay. I'd say we can include Pay section with that phrase.
- Schedule: "truly flexible scheduling" and "flexible hours" mentioned. Also "If you're uber tired and need a lyft, come to HoneyBaked - we offer truly flexible scheduling, so you can work around school/family/other commitments!" and "What We Offer" includes Flexible hours. So we have schedule info.
- Also "Other Things To Know": physical demands (long hours, bending, stooping, standing, twisting, lifting up to 65 pounds). Could be part of Requirements or maybe a separate section like "Physical Demands". Not in list of headings; we could put under Requirements or maybe under a generic section but we only allowed those headings. Could incorporate into Requirements as additional requirement.
- "GET TO KNOW US": link to YouTube channel. Could be under About the role or maybe a separate section like "Learn More". Not in headings; we could put under About the role as a link.
We must not include boilerplate EEO etc.
We need to output only HTML fragment, no /, no markdown fences.
We'll produce something like:
About the role
After over 60 years in business, we're still deeply committed to Making Meals Memorable. We're the home of The World's Best Ham™, and the secret to our success isn't a secret at all--it's our people. We're a high performance team committed to being authentic in everything we do and to living our Values in full view of the communities we serve. We have an entrepreneurial spirit that's brought us a lot of success and we're looking for a Seasonal Delivery Driver to join our team - these roles deliver our awesome HoneyBaked products from our hub store to our Pop-Up Retail locations in grocery stores and/or malls in the local area. If you're uber tired and need a lyft, come to HoneyBaked - we offer truly flexible scheduling, so you can work around school/family/other commitments! HoneyBaked's seasonal positions could be the perfect seasonal side gig! You'll find a great culture at HoneyBaked. Serve Others and Do The Right Thing are core values for us - we believe in being authentic in all that we do and in living our Values in full view of the community we serve. Learn more about HoneyBaked and get great recipes on our YouTube channel: HoneyBaked YouTube.
But we need to preserve the link text exactly as in posting: "Find out more about HoneyBaked - and get some great recipes - on our YouTube channel here". The posting says: "GET TO KNOW US Find out more about HoneyBaked - and get some great recipes - on our YouTube channel here". No actual URL given. We cannot invent a URL. We should keep the text as is, maybe as plain text without a link? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the sentence exactly, but we cannot make up a URL. The original text includes "here" as a placeholder for a link but no URL. We could keep it as plain text: "Find out more about HoneyBaked - and get some great recipes - on our YouTube channel here." That's fine. Thus About the role paragraph includes that sentence. Now Responsibilities: list from "What You'll Do". We'll create- items.
Responsibilities list:
- Arrive at HUB store to get product for Pop-Up Retail locations.
- Complete Truck Assessment checklist at the beginning of each delivery day prior to leaving hub store.
- Ensure that products are secured in the truck using straps or loading bars.
- Safely transport products to Pop-Up Retail locations.
- Place product on the reassembled flatbed cart to be taken into the location.
- Take expired product and place in empty boxes and return to home store.
- Complete the delivery manifest checklist, ensuring that all product is accounted for and delivered accurately, as well as returned to store when needed.
- Complete temp logs to ensure product food safety standards are met.
Now Requirements: from "YOUR TRACK RECORD". Also include physical demands from "Other Things To Know". Also maybe include "At least 21 years of age", "CDL not required". Also "Ability to safety operate a 14 ft. to 26 ft. refrigerated truck for local deliveries", "Have a valid driver's license and current DOT medical card", "Ability to pass a pre-employment DOT drug screen, MVR check and DOT background", "Have knowledge of current DOT requirements". Also physical demands: "Requires long hours at the Holiday season and requires bending, stooping, standing for long periods, twisting and lifting products and supplies of up to 65 pounds on a constant basis."
We'll put all under Requirements.
Now Benefits: from "What We Offer". List:
- Competitive pay
- Fun and casual environment
- Flexible hours
- Associate discounts on our fantastic products.
- along with a free ham or turkey breast at the completion of your holiday schedule (a gift card may be substituted, depending on product availability)
We could combine the last two as separate items.
Now Pay: we have "Competitive pay" already in Benefits. But we could still have Pay section with that phrase. However to avoid duplication, maybe we put Pay section with "Competitive pay" and Benefits with other items. But the instruction says prefer a few substantive sections over many thin ones. Having both Pay and Benefits may be thin if Pay only has "Competitive pay". Might be better to incorporate Pay into Benefits. However the instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state competitive pay, so we could have Pay section. But we also have Benefits section with other items. It's okay to have both if they are substantive. Pay section with just "Competitive pay" might be considered thin but it's still substantive (states pay is competitive). The instruction says prefer a few substantive sections over many thin ones. Could combine Pay and Benefits into one Benefits section that includes pay. But they gave separate headings for Pay and Benefits; we can choose to include both if we have content. I'd lean to include both to follow the heading list, but ensure not thin. Pay: "Competitive pay". Benefits: other items.
Schedule: we have flexible scheduling/hours. So Schedule section: "Truly flexible scheduling to work around school/family/other commitments" and "Flexible hours". Could combine.
Now we need to ensure we don't repeat content. We'll avoid duplication.
Let's craft sections:
About the role
After over 60 years in business, we're still deeply committed to Making Meals Memorable. We're the home of The World's Best Ham™, and the secret to our success isn't a secret at all--it's our people. We're a high performance team committed to being authentic in everything we do and to living our Values in full view of the communities we serve. We have an entrepreneurial spirit that's brought us a lot of success and we're looking for a Seasonal Delivery Driver to join our team - these roles deliver our awesome HoneyBaked products from our hub store to our Pop