Jobs · Management · New Jersey

Warehouse Technician (Driving)

AdaptHealth · Cherry Hill, NJ · 1 mo ago
ManagementFull-time
We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use
  • for any list of duties/requirements/benefits, and

    for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info; remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Include a section only when posting has real specific content for it. Avoid filler like "commensurate with experience". Pay/Schedule/Benefits sections only if posting actually states them. We need to parse the posting. Key sections: - About AdaptHealth (company description) maybe not needed as a heading? The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should include headings only for those categories if content exists. The "About AdaptHealth" is more company overview; not listed as a heading category. Could we include as a

    without heading? Possibly yes, but we need to preserve substantive info. 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 suggests using those for those sections. We could still include a heading like "About AdaptHealth" but not in list; but safer to follow instruction: only use those headings when appropriate. However we need to convey company description; maybe we can put it under a

    without heading, or under a heading like "About AdaptHealth" but that is not in the list; risk of deviating. The instruction says "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are examples; we could still use other headings if needed, but better to stick to those. The company description could be placed under a heading like "About AdaptHealth" but not required. The instruction: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings, but to be safe we could embed the company description in a

    before any headings. We must not repeat the job title as heading. The job title is "Warehouse Technician – Driving". So we should not have an

    with that. We need sections: - About the role: we have a paragraph describing the role: "About The Role Warehouse Technician – Driving The Warehouse Technician – Driving operates in a key role that supports patients through daily warehouse operations. The position combines hands-on equipment management with shipping and inventory support. If you’re detail-oriented and passionate about safe warehouse operations, this is the role for you." We can put that under

    About the role

    and then a

    . - Responsibilities: list of core responsibilities. We'll put under

    Responsibilities

    and a
    • for each bullet. - Requirements: we have "Why You’re the Best Fit" bullet list: High School Diploma or equivalent work experience required; One (1) year of experience in warehouse, construction, general labor, military, equipment repair, maintenance or work that is transferrable to the job duties of the role is required; Valid and unrestricted Driver’s License; Able to manage priorities in a fast-paced environment; Basic technical/mechanical and computer skills; Strong attention to detail including problem solving skills. We can put under

      Requirements

      (or Qualifications?). The instruction includes both Requirements and Qualifications as possible headings. We have requirements; we could use Requirements. - Qualifications: maybe not separate; we could combine with Requirements. But we have also "Work Environment" and "Physical Requirements". Those could be under Requirements or maybe under a separate section like "Work Environment". Not in the list but we could incorporate into Requirements or a separate

      . The instruction says we should prefer a few substantive sections over many thin ones. So we could include Work Environment under Requirements as a paragraph. - Skills: we have "Basic technical/mechanical and computer skills; Strong attention to detail including problem solving skills". Those could be under Skills heading. But we already have them in Requirements. Might be redundant. Better to separate: Requirements for education/experience/license; Skills for technical/mechanical, attention to detail, problem solving. We'll decide. - Benefits: we have "Total Rewards & Benefits Program" list: Comprehensive medical, dental and vision coverage (eligible first of the month following hire); 401(k) with company match; Paid Time Off Plans including 6 paid holidays; Employee Stock Purchase Plan; Paid Parental Bonding Leave; Short and Long-term Disability Insurance; Life and AD&D Insurance; Flexible Spending Accounts (FSA) and Health Savings Accounts (HSA); CVS Minute Clinic and Teledoc access; Spousal Advantage Reimbursement Plan; Identity Theft Protection and Legal Plan; Applicable waiting periods apply. We'll put under

      Benefits

      with
        . - Pay: The posting says "Compensation Compensation is based on experience, location and role level". That's vague; not a specific number or range. According to instruction: 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 they state compensation is based on experience, location and role level - that's somewhat vague but still a statement. Is that considered filler? It's not a specific number, but it's a statement about how compensation is determined. The instruction says avoid filler like "commensurate with experience". This is similar. Likely we should not create a Pay section because it's not specific. So we omit Pay. - Schedule: Not mentioned. So omit Schedule. - Work Environment: we have a paragraph: "This position requires driving/travel. Physical Requirements: Each role has a unique set of physical demands and work environment(s) that an employee will encounter while performing the essential function of the job. Reasonable accommodations may be made to enable individuals with disability(s) to perform the essential functions. For more detail surrounding these requirements please inquire upon application selection." We could incorporate that under Requirements or as a separate

        without heading. Since we prefer few substantive sections, we could add a

        Work Environment

        but it's not in the list; but we could still use it as a heading? The instruction only gave examples; not prohibited. However to be safe, we could incorporate into Requirements section as a paragraph after the list. We also have "Why You’re the Best Fit" which we treat as Requirements. We also have "Requirements Disclosure" about background checks, MVR, Florida, California, EEO etc. That's legal boilerplate; we should remove EEO/equal-opportunity/scams etc. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should drop the Requirements Disclosure section (background check, MVR, Florida, California, EEO). Also drop the "Ready to Make an Impact?" and "Apply today" as application instructions. Also drop "The Adapt Difference" bullet list? That's about company values; could be considered part of About AdaptHealth? It's a list: Commitment to Our People – Support, Development, and Advancement Opportunities; Competitive Compensation and Incentives; Comprehensive Total Rewards & Benefits; Industry-Leading Care & Innovation; Responsible Environmental Stewardship. This is substantive about company; we could keep it under About AdaptHealth paragraph. It's not boilerplate; it's company values. We'll keep. Now we need to output only HTML fragment, no /, no markdown fences. Structure:

        About AdaptHealth paragraph including The Adapt Difference list maybe as

          .

          Then

          About the role

          ...

          Then

          Responsibilities

          • ...
          • ...
          Then

          Requirements

          • ...
          • ...
          Then

          Skills

          • ...
          • ...
          (if we separate) Then

          Benefits

          • ...
          • ...
          Potentially also include Work Environment as a

          under Requirements or separate. We need to ensure we don't duplicate content. Let's extract exact text. About AdaptHealth: "At AdaptHealth we offer full-service home medical equipment and related services that empower patients to live their best lives – beyond the hospital and at home. With supporting locations across the nation, AdaptHealth is the vital link in the healthcare ecosystem that bridges the gap between patients, providers, and high-quality, compassionate care. If you’re passionate about making a meaningful and lasting difference in the lives of patients, we invite you to explore a career with AdaptHealth." Then The Adapt Difference list: "Commitment to Our People – Support, Development, and Advancement Opportunities Competitive Compensation and Incentives Comprehensive Total Rewards & Benefits Industry-Leading Care & Innovation Responsible Environmental Stewardship" We can format as

          • Commitment to Our People – Support, Development, and Advancement Opportunities
          • ... etc. Now About the role paragraph: "About The Role Warehouse Technician – Driving The Warehouse Technician – Driving operates in a key role that supports patients through daily warehouse operations. The position combines hands-on equipment management with shipping and inventory support. If you’re detail-oriented and passionate about safe warehouse operations, this is the role for you." We should remove duplicate "Warehouse Technician – Driving". The heading is About the role; we can just have the description. Now Responsibilities list (Core Responsibilities): - Pick, pack, and prepare orders for shipment; verify accuracy against invoices - Receive, inspect, and stock incoming inventory - Clean, disinfect, test, and perform minor repairs on returned equipment - Track inventory, monitor stock levels and expirations, and report shortages - Maintain a clean, organized, and compliant warehouse environment - Perform data entry, order tracking, and basic administrative tasks (scanning, filing, etc.) - Assist with loading/unloading equipment and staging deliveries - Follow driving policies and complete deliveries safely and on time - Deliver and set up respiratory and home medical equipment in patient homes and healthcare facilities - Educate patients and caregivers on proper use, care, and safety of equipment - Perform basic patient assessments and follow-up visits as needed - Troubleshoot equipment issues and provide support in urgent situations - Complete visit documentation and ensure accurate patient records - Maintain strict confidentiality and adhere to HIPAA guidelines - Follow all infection control, PPE, and safety protocols - Performs other duties as assigned We'll put each as
          • . Now Requirements list (Why You’re the Best Fit): - High School Diploma or equivalent work experience required - One (1) year of experience in warehouse, construction, general labor, military, equipment repair, maintenance or work that is transferrable to the job duties of the role is required - Valid and unrestricted Driver’s License - Able to manage priorities in a fast-paced environment - Basic technical/mechanical and computer skills - Strong attention to detail including problem solving skills We'll put as
          • . Now Skills: maybe we could separate technical/mechanical and computer skills, attention to detail, problem solving as Skills. But they are already in Requirements. To avoid duplication, we could keep them under Requirements and not have

Similar jobs