Warehouse Team Lead

We need to output HTML fragment with sections: About the role? Actually we have POSITION SUMMARY, KEY RESPONSIBILITIES, SUCCESS METRICS, QUALIFICATIONS, WORK ENVIRONMENT, About Scentbird (maybe not needed). We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should map content accordingly. We must not repeat job title as heading. No Job ID etc. Remove boilerplate (EEO etc). We need to preserve all substantive info. We need sections only when posting has real specific content. We have: - About the role: could be POSITION SUMMARY (maybe "About the role"). - Responsibilities: KEY RESPONSIBILITIES. - Requirements/Qualifications: QUALIFICATIONS (Required and Preferred). Could split into Requirements and Preferred? But we have only Qualifications heading allowed. Could use

Qualifications

and list required and preferred. - Skills: maybe not separate; we could embed within Qualifications. - Benefits, Pay, Schedule: not provided explicitly. There's WORK ENVIRONMENT mentions schedule may include early morning, evening, or weekend shifts depending on operational needs. That's schedule info. So we can create a Schedule section with that info. Benefits not mentioned; Pay not mentioned. So we omit those sections. - Also we have SUCCESS METRICS maybe could be under Requirements? But we could create a separate section like "Performance Expectations" but not allowed headings. Only allowed headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to fit SUCCESS METRICS somewhere. Could be under Requirements or Qualifications? Probably under Requirements (as performance expectations). We'll include them in Requirements section. - Also we have WORK ENVIRONMENT details: on-site, full-time, standing, walking, lifting, PPE required. That's not schedule but could be part of Schedule? Actually schedule is separate. Work environment could be part of About the role? Might be okay to include in About the role or maybe we can add a separate section? Not allowed headings. Could incorporate into About the role paragraph. - Also About Scentbird description: could be part of About the role? Might be considered company overview; we could include in About the role. We must not invent or summarize away detail. Must preserve all substantive info. So we need to include all details from the posting. We need to use

• for any list of duties/requirements/benefits. So for responsibilities list, we need to convert each bullet into
• . For qualifications required and preferred, also list. We need to use

  for prose. We must not include any markdown fences. Let's extract content. POSITION SUMMARY paragraph: "The Warehouse Lead is responsible for leading daily warehouse shift operations at Scentbird's fulfillment facility. This role ensures the safe, accurate, and efficient execution of all warehouse activities — from order picking and staging through quality control and shipping. The Warehouse Lead is both a hands-on operator and a frontline people leader, coaching associates, driving performance, and continuously improving processes to meet and exceed facility benchmarks." We can put that in

  under About the role. KEY RESPONSIBILITIES: multiple bullet-like paragraphs each starting with a heading like Shift Leadership & Operations, Work Order & Inventory Management, SNAP System Operations, Safety & Compliance, Team Development & Coaching, Cross-Functional Collaboration, Continuous Improvement. Each has sub-bullets. We need to flatten into a list? The instruction: Use

  • for any list of duties/requirements/benefits. So we can treat each responsibility category as a
  • with its details maybe as nested
    ? But we can just make each bullet a
    • and include the sub-details as part of the
    • text (maybe using

      inside?). Simpler: each responsibility category as a

    • and inside we can have

      for the description. But we must not violate rule: Use

      • for any list of duties/requirements/benefits, and

        for prose. So we can have

        with
        • each containing

          prose. Thus:

          Responsibilities

          • Shift Leadership & Operations: Run structured daily shift briefings and debriefs, setting clear priorities and expectations; Assign tasks based on volume, associate strengths, and operational priorities; Manage shift performance to ensure on-time completion of all work orders and KPIs; Escalate issues proactively — resolve problems before they impact downstream operations; Present weekly shift KPIs (UPH, order accuracy, on-time completion) to leadership.

          • Work Order & Inventory Management: Execute the full work order lifecycle independently: picking, staging, transfers, bulk processing, and QC documentation; Own cycle count scheduling and inventory reconciliation for assigned zone; Ensure zero work order errors on shift; investigate and document root causes when issues arise; Maintain strict adherence to brand-specific storage logic and location ownership rules; Never adjust inventory outside your team's designated locations without prior communication.

          • SNAP System Operations: Navigate SNAP confidently for task assignments, inventory lookups, and transactions; Execute all key transaction types: Transfers, STRAs, BRP, and SPW; Troubleshoot routine SNAP issues independently before escalating to supervisor.

          • Safety & Compliance: Model and enforce Scentbird's safety standards and PPE requirements at all times; Communicate professionally with peers, leads, and supervisors across all departments; Report safety concerns and near-misses immediately — zero tolerance for delayed reporting; Maintain zero safety violations on shift.

          • Team Development & Coaching: Deliver real-time coaching to associates on performance, accuracy, and conduct; Conduct formal performance check-ins for all direct reports; Identify high-potential associates for cross-training or advancement opportunities; Recognize strong performance consistently and address performance gaps directly and professionally; Train associates on work order procedures and SNAP operations.

          • Cross-Functional Collaboration: Build trusted working relationships across Warehouse, Manufacturing, Quality, and Inventory Control; Partner with Receiving, Transportation, and Procurement to resolve SLA issues proactively; Participate in capacity planning for upcoming peak periods; Communicate operational changes and risks to all affected teams — no surprises.

          • Continuous Improvement: Identify recurring floor pain points and develop documented solutions aligned with management; Lead Continuous Improvement and 5S initiatives from kickoff through completion; Submit operational improvement roadmaps with clear owners and timelines; Document before/after results and share outcomes with the team and leadership.

          Now SUCCESS METRICS: we can include under Requirements maybe as a

          list. Could also be its own section but not allowed. We'll put under Requirements. Requirements section: maybe

          Requirements

          with

          containing success metrics and maybe also some other requirements? Actually Qualifications already covers required/preferred. So Requirements could be the success metrics. We'll do that. Thus:

          Requirements

          • Order accuracy at or above 99%.

          • Shift KPIs (UPH, on-time completion) at or above facility benchmark.

          • Zero safety violations on shift.

          • All associates receive regular coaching and formal performance check-ins.

          • At least one measurable process improvement delivered within the first 90 days.

          • Partner teams recognize the Warehouse Lead as a reliable, solutions-first collaborator.

          Now Qualifications: we have Required and Preferred. We'll make

          Qualifications

          with two sub-lists maybe
          for Required and another for Preferred. Could also separate with headings inside but not allowed. We'll just make two
          with
          • each. Thus:

            Qualifications

            Required

            but we cannot use h4? Not prohibited but we should stick to allowed headings? The instruction only says use

            for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe we can avoid extra headings and just incorporate Required and Preferred as or within

            . But we need to preserve detail. Could do:

            Qualifications

            • Required:
            ... but nested lists maybe okay. Better: Use

            for prose and

            • for lists. So we can have:

              Qualifications

              Required:

              • Demonstrated experience in warehouse, fulfillment, or logistics operations
              • Prior experience in a team lead, supervisor or frontline leadership role
              • Proficiency with warehouse management systems and inventory transaction processes
              • Strong communication skills — written and verbal — across all levels of the organization
              • Ability to prioritize and manage multiple tasks simultaneously in a fast-paced environment
              • Commitment to safety, accuracy, and accountability

              Preferred:

              • Experience with SNAP or similar WMS platforms
              • Familiarity with 5S, Lean, or Continuous Improvement methodologies
              • Experience in a subscription-box, e-commerce, or direct-to-consumer fulfillment environment
              • Bilingual (English/Spanish) a plus
              That seems fine. Now Schedule: from WORK ENVIRONMENT: "This is an on-site, full-time position based at Scentbird's warehouse facility. The role requires standing, walking, and lifting throughout the shift. Schedule may include early morning, evening, or weekend shifts depending on operational needs. PPE is required and provided." We need Schedule section: include schedule info. Also maybe mention on-site, full-time, physical demands, PPE. Since schedule section is for schedule, we can put schedule details there. The other details (on-site, full-time, physical demands, PPE) could go in About the role or maybe we can add a separate section? Not allowed. We'll incorporate them into About the role paragraph maybe. Thus About the role will include POSITION SUMMARY plus work environment details. Let's craft About the role:

              The Warehouse Lead is responsible for leading daily warehouse shift operations at Scentbird's fulfillment facility. This role ensures the safe, accurate, and efficient execution of all warehouse activities — from order picking and staging through quality control and shipping. The Warehouse Lead is both a hands-on operator and a frontline people leader, coaching associates, driving performance, and continuously improving processes to meet and exceed facility benchmarks. This is an on-site, full-time position based at Scentbird's warehouse facility. The role requires standing, walking, and lifting throughout the shift. Schedule may include early morning, evening, or weekend shifts depending on operational needs. PPE is required and provided.

              We could also include About Scentbird description? Might be considered company overview; but we can add as a separate paragraph under About the role maybe. Add:

              Scentbird inspires fragrance lovers to go beyond the ordinary and sample scents that evoke passion, confidence, and the unknown. Our mission is to revolutionize the way we perfume by bringing the ultimate fragrance playground right to your fingertips and offering a digital subscription service that lets members choose from over 1000+ designer perfumes each month.

              plus the brand descriptions. That is a lot of text; we must preserve all substantive info. So we need to include all that brand