Delivery Driver (CDL)

Standards & compliance context

• Describe essential functions clearly so the posting supports ADA-aligned job documentation and accommodation review.
• Avoid bias-coded language such as rockstar, ninja, or culture fit, which can undermine EEOC and OFCCP-aligned hiring practices.
• If the role is exempt or non-exempt for wage and hour purposes, confirm the classification separately and do not imply it from the title alone.
• Include compensation details where pay transparency laws apply, and make sure the salary range reflects the actual route and location.
• Use required skill language for true must-haves and preferred skill language for secondary qualifications to reduce unnecessary screening barriers.

General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.

Best practices

• Name the exact CDL class and any required endorsements instead of leaving the license requirement vague.
• Describe the route pattern, such as local, regional, or scheduled multi-stop delivery, so applicants can self-select accurately.
• List pre-trip and post-trip inspections as essential functions, not optional responsibilities.
• Keep the required skills to the capabilities needed to do the work safely, and move nice-to-have items into preferred skills.
• Use outcome-based language for delivery work, such as on-time drop-offs, accurate paperwork, and safe customer handoff.
• Include the physical demands only as they relate to the actual job, such as lifting, climbing, securing freight, or operating lift gates.
• Add salary range and benefits placeholders when required by law or when competing for drivers in a tight market.

Common use cases