Sr. Director of Operations

We need to output HTML fragment with headings

for sections present: About the role? The posting includes Overview, General Description, Responsibilities, Qualifications, Education/Certifications, Work Conditions, maybe Benefits? There's a line "***Will pay relocation for out of state candidates***" which is a benefit/relocation. Also maybe Pay? No explicit pay. Schedule? Not mentioned. So we include sections: About the role? Could use "Overview" as About the role? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map sections accordingly. We have Overview (company description) maybe not needed as About the role? The "General Description" is essentially role description. Could treat as About the role. Then Responsibilities, Qualifications, Education/Certifications (maybe under Qualifications? but we can separate). Work Conditions maybe under Requirements? Not exactly. Could create a section "Work Conditions". Benefits: we have relocation pay. So Benefits section. We must not repeat job title as heading. No Job ID. We must preserve all substantive information, not invent. Remove boilerplate like EEO etc. Remove EEO paragraph. Also remove navigation etc. We need to output only HTML fragment. Let's extract content: Overview: Sprout is a global IT hardware retirement provider... (the paragraph). Also note "***Will pay relocation for out of state candidates***". That's a benefit. General Description: The Senior Director of Operations owns Sprout's core ITAD business end to end... (long paragraph). We'll keep that as About the role. Responsibilities: list of responsibilities broken into sub-sections: Garland Site Leadership (Both Facilities) with bullet points, Strategy and Business Leadership, Network Operating Rhythm and SLA Performance, Financial Accountability, Standardization and Compliance, Continuous Improvement, People Leadership. We need to output

• for any list of duties/requirements/benefits. So each bullet point under responsibilities should be
• . For subheadings within responsibilities, we could still use

  ? 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 we should follow that. Probably we keep only those top-level sections. Within Responsibilities we can have paragraphs and lists. Thus structure:

  About the role

  ...General Description...

  ***Will pay relocation for out of state candidates***

  maybe move to Benefits.

  Responsibilities

  • Garland Site Leadership (Both Facilities): ... (maybe we need to break into multiple li for each bullet). Could embed sub-bullets? But we only need
    • for any list. Could treat each top-level bullet as li, and inside li we can have further detail as text. Thus:
    • Garland Site Leadership (Both Facilities)
      • Be on the floor in both Garland facilities daily; run Gemba walks and join key huddles...
      ...
    But nested ul may be okay. The instruction didn't forbid nested lists. Similarly for other sections.

    Qualifications

    • Experience 10+ years in operations leadership, including 5+ years leading multiple facilities or a multi-site network, in ITAD, reverse logistics, refurbish/resell, electronics recycling, or 3PL.
    • ITAD, reverse logistics, or refurbish/resell facility experience is required.
    ... etc. We also have Knowledge, Education/Certifications, Work Conditions. We could combine Knowledge under Qualifications? But we have separate heading for Knowledge? Not in list but we could include as part of Qualifications. However instruction says use those headings only when posting has real specific content. Knowledge is present. Could make a section "Knowledge". But not in the example list; but we can still use

    for any heading? The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are typical but we can use others if needed? Safer to stick to those. Knowledge could be placed under Qualifications as a bullet. Education/Certifications: we can make a section "Education / Certifications" maybe as Qualifications? But we have separate heading for Qualifications; Education could be part of Qualifications. However we have distinct content; we could create a section "Education / Certifications" as a heading (though not in example). 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 says "use

    for section headings (e.g ...)". It might be okay to use other headings as long as they are

    . But to be safe, we could treat Education/Certifications as part of Qualifications. Work Conditions: could be under Requirements? Not exactly. Could be a section "Work Conditions". Might be okay. Benefits: we have relocation pay. Thus final sections: About the role, Responsibilities, Qualifications, Benefits, Work Conditions. We must not include empty sections. Now craft HTML. Let's extract precise text. Overview paragraph: "Sprout is a global IT hardware retirement provider for hyperscaler and enterprise clients. We leverage a nationwide footprint (and international partner network) combined with proprietary software to enable efficient end-to-end IT asset disposition, with a focus on data-bearing devices from the client to the cloud. Sprout is headquartered in Charlotte, NC, with additional operations near Sacramento, Dallas, and Boston, and provides IT Asset Disposition, Certified Destruction, and Responsible Recycling solutions. Since our founding as an electronic waste startup in a Duke University dorm room in 2014, we have grown at an average rate of more than 66% per year. By adhering to our three values (One Sprout, Deliver Excellence, and Integrity Matters), we move at #SproutSpeed to become the emerging leader in our industry. We are execution-obsessed, compliance-driven, and always improving through Lean and 5S. Learn more at www.sproutup.com." Then relocation line: "***Will pay relocation for out of state candidates***" General Description paragraph (starting after that): "The Senior Director of Operations owns Sprout's core ITAD business end to end: receiving, serialization, data sanitization, test and triage, refurbish/resell, de-manufacturing, recycling, and pack/ship. This is the second-in-command role in Sprout Operations, reporting to the VP of Operations and acting on the VP's behalf across the core business. The role is based in Garland, TX, and leads the two Garland facilities through an Operations Manager at each site, while directing core-business execution across all Sprout sites through their Facility Managers. The Operations Managers run the floor; the Senior Director sets direction, owns results, and removes constraints. Success means Garland runs to plan every day while the Senior Director still has time for strategy, capacity, margin, and transformation across the network. The Senior Director is accountable for production fundamentals (quality, cost, and units), SOW and SLA attainment, contribution margin, and conformity with R2v3, ISO 9001, ISO 14001, ISO 45001, and OSHA requirements. They lead facility transformation projects, including process improvements, asset deployments, and new capabilities, and partner closely with Compliance/QEHS, Engineering, Client Success, Sales, and Finance. Data Center Depot and AI-enabled server processing (Velerity Compute) are outside this role's scope and remain with the VP of Operations. Because Velerity Compute shares the Garland footprint, the Senior Director co-owns shared-site priorities with that team: space, dock, labor, safety, and security." Now Responsibilities: we need to capture bullet points. Let's list them: Garland Site Leadership (Both Facilities) - Be on the floor in both Garland facilities daily; run Gemba walks and join key huddles to see flow, quality, and safety firsthand. - Own Garland's daily and weekly production plan with the two Operations Managers: inbound schedule, WIP, units, turn time, and outbound commitments. - Review Garland performance every day (units, quality, labor hours, backlog, aging) and step in the same shift when a site is off plan. - Balance labor, equipment, and volume between the two buildings to protect SLAs and keep both sites loaded. - Complete the build-out and ramp of the Wood Drive facility: layout, equipment, staffing, and transfer of volume between buildings. - Own Garland facilities, EHS, and physical security: maintenance, housekeeping, 5S, access control, incident response, and landlord and vendor relationships. - Coordinate shared-site priorities with the Velerity Compute team at Garland: dock time, floor space, shared labor, and security zones. - Host client visits, audits, and certification assessments at Garland as the site's senior leader. - Own Garland staffing: hiring plan, onboarding, training matrix, and supervisor development. Strategy and Business Leadership - Act as second-in-command to the VP of Operations; represent Operations in leadership forums and make decisions on the VP's behalf for the core business. - Own the annual operating plan for the core business: volume, labor, capacity, capex, and contribution margin by site and service line. - Translate sales pipeline and client forecasts into capacity plans; flag constraints early with options and cost. - Build the business case (cost, throughput, payback) for automation and CI investments related to Core business and present them for approval. Network Operating Rhythm and SLA Performance - Set the cross-site operating rhythm: weekly Ops Review, monthly business review, and red/yellow escalation for labor, flow, quality, safety, and capacity. - Hold Operations Managers and Facility Managers accountable for production fundamentals: quality, cost, and units per labor hour. - Drive SOW and SLA attainment across all core programs (serialization accuracy, turn time, on-time delivery, inventory accuracy), treating targets as the minimum acceptable result. - Approve cross-site load balancing, overtime within guidelines, and temporary re-routing to protect SLAs. - Govern inventory integrity: cycle counts, aging and WIP control, and reconciliation to client and internal systems. - Own exception management for escalated issues (expedites, carrier failures, material holds, defect spikes) with root cause and corrective action. Financial Accountability - Own site-level P&L drivers for the core business: labor cost per unit, yield and recovery value, consumables, freight, and overhead absorption. - Partner with Finance on monthly forecasts, variance explanations, and budget. - Make disposition and routing decisions with contribution margin as the deciding metric. Standardization and Compliance - Deploy and enforce standard work across receiving, testing, triage, data sanitization, de-manufacturing, pack/ship, and inventory control. - Partner with Compliance/QEHS to maintain R2v3, ISO 9001, ISO 14001, and ISO 45001 conformity; ensure CAPAs are implemented, verified, and sustained. - Ensure chain-of-custody, security, and safety practices are followed; own audit readiness at every core-business site. - Publish the weekly and monthly OKRR report: KPI trends, risks, improvement results, and decisions needed. Continuous Improvement - Turn operational pain points into a prioritized CI and automation backlog with clear business cases. - Sponsor Kaizens and 5S at each site; lock gains into SOPs, training, visual management, and audits. People Leadership - Directly lead two Garland Operations Managers and the core-business Facility Managers at other sites. - Coach leaders on financial decision making, process thinking, and standard work