Distribution Center Manager - Salt Lake City, UT

We need to output HTML fragment with sections: About the role? Actually we have content: "Be part of something bigger..." intro paragraph. Then description of role, responsibilities, requirements, benefits, about company. 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. Output ONLY the HTML fragment — no /, no markdown code fences. We need to decide which sections to include based on content. We have: - Intro paragraph: "Be part of something bigger..." etc. Could be "About the role" or just a general intro. The instruction says we can use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only if there is real specific content. We have responsibilities: many bullet-like sentences. Could be a Responsibilities section with

  • . We have Minimum Work Experience Requirements Preferred qualifications: list of qualifications. Could be Requirements or Qualifications. We have benefits: list of benefits: "Our Competitive Benefits? 401K Plan, Competitive Medical Plans (medical, dental, and vision), Paid Vacation, Paid Sick, Paid Personal, Paid Holidays, Flexible Spending Accounts (Health and Dependent Care), Employee Assistance Program, Tuition Reimbursement, Employee Discounts, Long-term and Short-term Disability, Life Insurance and a Definitive Career Path." That's specific benefits, so we can have Benefits section. We have About Codale Electric And Sonepar USA: company description. Could be About the company but not in allowed headings; we could put under About the role? Or maybe we can omit because not required? But we need to preserve ALL substantive information. So we need to include that info somewhere. Could be a section "About the company" but not in allowed list. However instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, not exclusive? It says "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect we use those headings where appropriate. Could also use other headings if needed? 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 those are typical. Safer to stick to those. We have "About Codale Electric And Sonepar USA" which is about the company. Could fit under "About the role"? Not exactly. Maybe we can treat as "About the role" includes company context. The intro paragraph already mentions Codale's projects. The "About Codale Electric And Sonepar USA" gives more detail. Could be part of "About the role" or we could create a separate section "About the company" but not in list; risk of being considered not following instruction. However instruction says "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." implies those are examples, not exhaustive. So we could add other headings like "About the company". But to be safe, maybe we incorporate that info into "About the role" section. We also have "Minimum Work Experience Requirements Preferred qualifications" which is a mix. Could be Requirements and Qualifications sections. We have no explicit Pay or Schedule info, so we should not create those sections. We need to remove boilerplate: EEO statement, Pay Transparency, etc. Also remove navigation, cookie, legal, duplicated lines, application instructions. There's no explicit application instructions besides maybe the EEO contact; we remove that. We need to preserve all substantive information: intro paragraph, role description, responsibilities list, qualifications list, benefits list, company description. We need to format as HTML fragment: use

    for headings,

    for prose,

    • for lists. We need to avoid repeating job title as heading (not present). No Job ID. Let's craft:

      About the role

      Be part of something bigger. At Codale Electric, we’re proud of the role we’ve played in projects like the new Salt Lake Airport, the Las Vegas Raiders stadium and Soleil Lofts, as well as our role in housing, commercial, and industrial projects of every size throughout the Intermountain West. We strive to be the best wholesale distributor in the area and invite you to be part of building the future. The Central Distribution Center (CDC) Manager leads and develops a team of associates and department leaders through motivating, mentoring, coaching, and clear accountability. This role is responsible for safe, high-quality, productive, and customer-focused distribution operations, ensuring orders are processed and shipped accurately and without incident. As a member of the Site Leadership Team, the CDC Manager drives an employee-centric, customer-centric, and continuous improvement culture; provides the tools and expectations needed for team success; and oversees warehouse operations, inventory control, transportation, logistics, safety, budgeting, and talent development.

      Then responsibilities:

      Responsibilities

      • Lead and serve as an integral member of the Site and CDC Leadership Teams.
      • Lead, motivate, mentor, and coach CDC associates and department leaders; establish clear expectations, mutually agreed-upon goals, and accountability for performance.
      • Direct CDC departments and activities, including receiving, storing, handling, picking, packing, shipping, Wire Shop, Fabrication, Transportation, Automation, PLS, and Quality Assurance.
      • Ensure timely and accurate order processing, inventory control, warehouse management, and shipment execution while consistently meeting internal and external customer expectations.
      • Manage inbound and outbound logistics, fleet, and transportation processes to optimize material flow, supplier synergies, service levels, and cost.
      • Develop and improve warehouse operating systems, product-handling and storage requirements, equipment utilization, gate processes, shipping methods, workflows, space allocation, and equipment layouts.
      • Achieve inventory accuracy, coordinate order fulfillment, monitor shipping performance, and use data and analytics to forecast and plan across supply chain, operations, and logistics.
      • Provide leadership and accountability for safety, DOT, OSHA, and environmental compliance, and enforce Sonepar business and operating policies.
      • Partner with Sales Leaders, branch management, and company leadership to resolve issues and develop short- and long-term strategies that support growth and customer satisfaction.
      • Develop and review departmental budgets, proactively identifying savings opportunities, risks, and business concerns.
      • Partner with department managers to investigate and implement operational and administrative process improvements using continuous improvement, LEAN, and Kaizen principles.
      • Model servant leadership by being present, acting with accountability, remaining curious, demonstrating empathy, and holding courageous coaching and feedback conversations.
      • Develop self and others through stretch assignments, annual performance management, talent development, and succession planning in partnership with Human Resources.
      • Operate forklifts and similar equipment when required and maintain applicable certifications.
      • Perform other duties as assigned.
      Then Requirements/Qualifications: We have "Minimum Work Experience Requirements Preferred qualifications" then a list: Bachelor’s degree in Business, Operations, Logistics, or Supply Chain; Five or more years of progressive warehouse, distribution, logistics, or operations leadership experience.; Experience leading transformational change and continuous improvement at the business-unit or distribution-center level.; Background facilitating LEAN and/or Kaizen initiatives.; Fleet and transportation management experience.; Experience with Eclipse ERP and proficiency with Microsoft Office applications.; Strong working knowledge of federal DOT, safety, environmental, and OSHA standards.; Demonstrated ability to create and manage annual operating budgets. We could split into Requirements (minimum) and Qualifications (preferred). But the text lumps them. Could make a single section "Requirements" with list. Or we could have "Requirements" and "Qualifications". Since we have both mentioned, we can create two sections: Requirements (minimum) and Qualifications (preferred). However the text says "Minimum Work Experience Requirements Preferred qualifications". It might be that the first line is heading, then list includes both required and preferred. To be safe, we can make one section "Requirements" and include all items. Or we could make two: "Requirements" for the first few items (maybe degree and years) and "Qualifications" for the rest. But we risk splitting arbitrarily. Given instruction to prefer few substantive sections over many thin ones, maybe combine into one section "Requirements". Let's do that.

      Requirements

      • Bachelor’s degree in Business, Operations, Logistics, or Supply Chain
      • Five or more years of progressive warehouse, distribution, logistics, or operations leadership experience.
      • Experience leading transformational change and continuous improvement at the business-unit or distribution-center level.
      • Background facilitating LEAN and/or Kaizen initiatives.
      • Fleet and transportation management experience.
      • Experience with Eclipse ERP and proficiency with Microsoft Office applications.
      • Strong working knowledge of federal DOT, safety, environmental, and OSHA standards.
      • Demonstrated ability to create and manage annual operating budgets.
      Then Benefits:

      Benefits

      • 401K Plan
      • Competitive Medical Plans (medical, dental, and vision)
      • Paid Vacation
      • Paid Sick
      • Paid Personal
      • Paid Holidays
      • Flexible Spending Accounts (Health and Dependent Care)
      • Employee Assistance Program
      • Tuition Reimbursement
      • Employee Discounts
      • Long-term and Short-term Disability
      • Life Insurance
      • Definitive Career Path
      Then About Codale Electric And Sonepar USA: we could incorporate into About the role or make a separate section "About the company". Since we already used About the role for intro, we could add another paragraph after responsibilities? But we need to preserve that info. Could add a section "About the company" with

      About the company

      and paragraph. Is that allowed? The instruction says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive. So we can add About the company. However to be safe, we could incorporate that info into About the role section by extending the paragraph. Let's do that: after the intro paragraph, we can add another paragraph about Codale Electric And Sonepar USA. Thus About the role section will have