Jobs · OTHR · California

Distribution Center Transportation Dispatch - Graveyard Shift

Rexel USA · Hayward, CA · 4 wk ago
OTHR$21.78–$27.23/hrFull-time
We need to output HTML fragment with sections: About the role? Actually we have Company Description, Job Description, Summary, What You'll Do, Job Duties Disclaimer, Qualifications, Additional Information (Physical Demands etc), Benefits, Pay (California pay range), Schedule (Graveyard Shift). Also maybe "Additional Information" includes Physical Demands etc. We need to follow rules: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use
  • for any list of duties/requirements/benefits, and

    for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones. We need to decide which sections to include. The posting includes: - Company Description (maybe not needed as a heading? Could be "About the company"? Not listed in allowed headings but we can use "About the role"? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They said use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should stick to those headings. However we can also have other headings? The instruction: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are examples; we could use other headings if appropriate, but likely they want those. We'll try to map content to those. We have: - About the role: could include summary and maybe company description? The "About the role" could be a brief description of the role. We have Summary: "The Distribution Center Transportation Dispatch is responsible for routing deliveries and drivers in the most efficient way possible while maintaining delivery metrics. Will also be responsible for vehicle maintenance, setting schedules, managing expedited orders, and acting as the main point of contact between internal customers and the delivery drivers. This position's schedule is Graveyard Shift from 9:00 PM to 5:30 AM Monday through Friday." We could put that in About the role. - Responsibilities: list of duties (What You'll Do). Could be bullet list. - Requirements: maybe Qualifications? Actually they have Qualifications section with "What You'll Need". Could be Requirements. - Skills: maybe Knowledge, Skills & Abilities. - Benefits: list of benefits. - Pay: California pay range. - Schedule: Graveyard Shift. We also have Additional Information: Physical Demands etc. Could be part of Requirements? Not exactly. Could be omitted? The instruction says include a section ONLY when posting has real, specific content for it. Physical Demands is specific content. But we don't have a heading for that in the list. Could we create a custom heading? The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those are typical. However to be safe, we could incorporate Physical Demands into Requirements or Qualifications? Might be better to create a section "Physical Demands" as its own heading, but not in the list. The instruction says "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say you cannot use other headings, but they gave examples. I'd stick to those to avoid risk. Thus we need to decide where to put Physical Demands. Could be part of Requirements (maybe as a sublist). But the instruction says use
    • for any list of duties/requirements/benefits. So we could have a Requirements section with sublists: Experience, Education, Knowledge/Skills/Abilities, Physical Demands. Similarly, we could have a Skills section separate from Requirements? The list includes both Requirements and Skills. Could separate: Requirements (experience, education) and Skills (knowledge, skills & abilities). Physical Demands could be under Requirements or maybe a separate section but we don't have heading. Might be okay to put under Requirements. We also have "Additional Information" includes Physical Demands, Weight And Force Demands, Working Environment. That's all specific. We'll include those as sub-items under Requirements. Now we need to remove boilerplate: EEO statements, duplicated lines, etc. Also remove "Job Duties Disclaimer" maybe not needed as it's boilerplate. Remove "Please note that management retains the right..." etc. That's boilerplate. Remove "The ability to competently perform all the essential duties..." also boilerplate. Remove "Rexel USA (A VEVRAA Federal Contractor), and its affiliated companies, is an EEO/Disabled/Veterans employer..." duplicates. Remove "For the state of California only, the pay range is $21.78 to $27.23, depending upon qualifications, experience, and other considerations permitted by law." That's pay info, keep. Remove "Commission/bonus plan: CSC Plan" maybe part of benefits? Could be included under Benefits? It's a specific plan; we could include as a bullet under Benefits. Also remove "Our Benefits Include ..." list; keep that as Benefits. Remove "Our goal is to create a workplace..." boilerplate. Now produce HTML. Structure:

      About the role

      Summary text.

      Responsibilities

      • Coordinate daily route planning, staffing, and load balancing activities
      • Ensure all vehicles, drivers, and processes meet both OSHA and DOT requirements
      • Responsible for the complete and accurate loading process of material going out for delivery
      • Ensure manifest integrity for all loads
      • Schedule deliveries and dispatches drivers based on requirements of the customer as communicated through various media channels
      • Keep accurate record of deliveries and ensures manifests are properly closed
      • Coordinate and communicates daily on-demand services as needed
      • Ensure all assets are maintained consistent with company expectations
      • Responsible for building and vehicle maintenance, safety, and security
      • Other duties as assigned

      Requirements

      1+ years of experience in a similar role and/or experience working in a Distribution Center or Warehouse preferred; High School or GED required.

      • Knowledge of Distribution Center/Warehouse principles, practices, and procedures
      • Knowledge of Transportation Systems and industry a plus
      • Excellent written, verbal, interpersonal, and presentation skills are required
      • Strong analytical, troubleshooting, and problem-solving abilities
      • Organization and time management skills, detail oriented, able to prioritize in a multi-tasking environment and ability to work under pressure and adhere to deadlines
      • Excellent customer service skills
      • Physical Demands:
        • Sit: Must be able to remain in a stationary position – Constantly (≥51%)
        • Walk: Must be able to move about inside/outside office or work location – Constantly (≥51%)
        • Use hands to finger, handle, or feel: Operates a computer and other office machinery – Constantly (≥51%)
        • Stoop, kneel, crouch, or crawl: Must be able to crouch down to stock shelves, pick up boxes, or position oneself to maintain computers in the lab/under desks/in server closet – Constantly (≥51%)
        • Climb or balance: Must be able to ascend/descend on a ladder, forklift, pallet jack, or other warehouse equipment – Frequently (21%–50%)
        • Talk, hear, taste, smell: Must be able to use senses to effectively communicate with co-workers and clients and detect hazardous conditions – Constantly (≥51%)
      • Weight and Force Demands:
        • Up to 10 pounds – Constantly (≥51%)
        • Up to 25 pounds – Constantly (≥51%)
        • Up to 50 pounds – Constantly (≥51%)
      • Working Environment:
        • Exposed to unpleasant or disagreeable physical environment such as high noise level and/or exposure to heat and cold – Constantly (≥51%)
        • Exposed to electrical hazards; risk of electrical shock – Occasionally (up to 20%)
        • Handles or works with potentially dangerous equipment – Constantly (≥51%)
      But note we have nested
        inside
      • which is okay but might be messy. Could instead make Requirements section with multiple
          lists. Simpler: after a brief paragraph, we can have separate
            for Knowledge/Skills, another for Physical Demands, etc. But instruction: use
            • for any list of duties/requirements/benefits. So we can have multiple lists. Let's structure:

              Requirements

              1+ years of experience in a similar role and/or experience working in a Distribution Center or Warehouse preferred; High School or GED required.

              Knowledge, Skills & Abilities

                ...

              Physical Demands

                ...

              Weight and Force Demands

                ...

              Working Environment

                ...
              But we are only supposed to use

              for section headings. Using

              might be okay but not specified. Could just use

              for subheadings? Might be okay to use . But to keep simple, we can just have one

                with all items, but that mixes categories. Might be okay. Better: Keep Requirements as a

                summarizing experience and education, then separate

                  for Knowledge/Skills, another for Physical Demands, etc. Use

                  only for main sections; subheadings can be

                  ...

                  . That's acceptable. Now Benefits section:

                  Benefits

                  • Medical, Dental, and Vision Insurance
                  • Life Insurance
                  • Short-Term and Long-Term Disability Insurance
                  • 401K with Employer Match
                  • Paid vacation and sick time
                  • Paid company holidays plus flexible personal days per year
                  • Tuition Reimbursement
                  • Health & Wellness Programs
                  • Flexible Spending Accounts
                  • HSA Accounts
                  • Commuter Transit Benefits
                  • Additional Optional Insurance such as Pet Insurance, Legal Assistance, Critical Illness, Home and Auto Insurance
                  • Employee Discount Programs
                  • Professional Training & Development Programs
                  • Career Advancement Opportun

Similar jobs