Jobs · Education · Washington

Principal Supply Chain Data Excellence

Brooks Running · Seattle, WA · 1 mo ago
On-siteEducation$145k–$232k/yrFull-time
We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes "Who We Are" (maybe About the role?), "Your Job" (maybe About the role?), "Your Responsibilities", "Qualifications". There's also "Compensation" (Pay). There's "Other" with benefits, PTO, bonus, perks, location (maybe schedule?). There's travel 5% (maybe schedule?). There's no explicit Skills section separate from qualifications; but we could treat Qualifications as covering skills. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to include sections only when posting has real specific content. So we need About the role (maybe combine Who We Are and Your Job). Responsibilities (clear). Qualifications (clear). Benefits (clear). Pay (clear). Schedule? There's travel 5% and location "You will spend 4 days per week in o" (cut off). The posting cut off at "You will spend 4 days per week in o". Likely meant "office". So schedule: 4 days per week in office, travel 5%. That's schedule info. So we can include Schedule section with that content. Requirements? The qualifications section includes requirements; but we could separate Requirements as maybe the qualifications list. However we have Qualifications already. The instruction includes Requirements as a possible heading; but we can decide to not include Requirements if we think Qualifications covers it. But we could include Requirements as a subset of qualifications? Safer to include Qualifications only, not Requirements, unless we have explicit requirements separate. The posting has "Qualifications:" then bullet list. So we will have Qualifications section. Skills: Not explicitly separate; we could omit. Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule. We need to use

for each heading. Use
  • for any list of duties/requirements/benefits. Use

    for prose. We must preserve ALL substantive information; do not invent or summarize away detail. Remove boilerplate etc. We need to extract content. Let's parse: Who We Are: paragraph about Brooks mission, culture, values list. Your Job: description of role. We can combine into About the role section: include both Who We Are and Your Job? The instruction: About the role heading likely for role description. Could include both the company overview and role summary. We'll put prose. Responsibilities: list of bullet points under "Your Responsibilities:" with subheadings: Supply Chain Digital Excellence Strategy & Stewardship, End-to-End Digital Data Thread Development, Digital Supply Chain Systems & Analytics Enablement, Prioritization & Cross-Functional Alignment, Change Management & Capability Building. Each has multiple sentences. We need to preserve all substantive information. We'll create

    • for each responsibility bullet? The instruction: Use
      • for any list of duties/requirements/benefits. So we can treat each top-level responsibility as a list item, and inside we can have

        for prose? But we can just put the prose inside

      • . That's fine. Qualifications: list after "Qualifications:" with bullet points (some semicolon separated). We'll make
        • each. Benefits: Under "Other:" there is "Brooks is proud to offer a robust benefits package..." then list: Benefits - Including medical, dental, vision, life and AD&D insurance, disability insurance, HSA and employer contribution, FSA, family & fertility assistance, 401K Savings Plan and match, employee assistance program, and transportation assistance. Paid Time Off - Brooks offers generous time off, including five weeks of paid time off, eleven paid holidays, and paid sick and parental leave. Bonus - In addition to base pay, Brooks employees may also be offered an annual bonus based on company performance. Perks - Including product discounts, employee recognition, fitness discounts, volunteer and donation benefits. Location - You will spend 4 days per week in o (cut). Travel 5% throughout the year. We need Benefits section: include medical etc. Also maybe include PTO, Bonus, Perks as part of benefits? Could be separate but we can include all under Benefits heading. The instruction: Use
          • for any list of benefits. So we can list each benefit item. Pay: Compensation section: "The pay range for this position, based out of the Brooks Seattle HQ, is $145,098 - $232,157 per year. Base pay offered will vary depending on job-related knowledge, skills, and experience." Schedule: Travel 5% throughout the year and location 4 days per week in office (assuming). We'll put that. We must not repeat job title as heading. Not include Job ID etc. We must output only HTML fragment. Let's craft. We'll start with

            About the role

            then

            combine Who We Are and Your Job. Who We Are paragraph: "At Brooks, we believe movement is the key to feeling more alive. That’s why we’re driven to create gear and experiences that take people to the place that makes them feel more alive — whether it’s a headspace, a feeling, or a finish line. Everyone who works at Brooks is propelled by a company culture that sparks excitement, fuels collaboration, inspires creativity, and ignites innovation. Our brand values help bond us together and drive our success: Runner FirstWe act in the best interest of the runner Word is BondWe do what we say we’ll do Champion HeartWe give our all in everything we do There is no “I” in Run We stay generous with our humanity Keep Moving We find ways to move every day, because joy is kinetic! We welcome everyone from every walk of life looking to inspire others through the power of movement - because we’re all moving towards something. Let’s run there." Note there are missing spaces between values; we keep as is. Your Job paragraph: "As the Principal Supply Chain Data Excellence at Brooks, you will enable Brooks’ global Supply Chain strategy by defining how critical Supply Chain data is governed, measured, trusted, and used across the source-to-market ecosystem. You will own the functional strategy for Supply Chain Data Excellence and translate business priorities into scalable standards, stewardship models, quality rules, governance decisions, reporting definitions, and prioritized improvement roadmaps. As the enterprise authority of Supply Chain data, you will connect business process expertise with data governance, systems delivery, analytics enablement, and change adoption. You will establish the end-to-end digital data thread linking critical master data, transactional data, process milestones, controls, KPI definitions, and decision points so teams can trace, understand, and trust the data that powers planning, execution, performance management, and strategic transformation. You will lead through influence across Supply Chain functional teams, IT, Data & Analytics, Product, regional partners, and leadership stakeholders. Success requires the ability to frame ambiguous data and process challenges, align senior stakeholders on standards and tradeoffs, sequence work against Run Trail Map priorities, and drive measurable improvements in data trust, usability, traceability, and adoption across multiple concurrent initiatives." We'll combine into one

            maybe two paragraphs? Could be two

            but okay. Next Responsibilities:

            Responsibilities

            then
              with
            • each major responsibility. We need to keep the subheadings inside li? Could include but not required. We'll just include the text. List items: 1. Supply Chain Digital Excellence Strategy & Stewardship: define and own the multi-year Supply Chain Digital Excellence strategy, roadmap, and operating rhythm that improve trust, consistency, usability, and accountability across planning, sourcing, logistics, fulfillment, product, finance-adjacent reporting, and regional processes; set the functional standards for critical Supply Chain data elements, ownership expectations, quality dimensions, business rules, validation logic, acceptable thresholds, stewardship routines, escalation paths, and issue-resolution decision rights; lead senior-level governance reviews that move data quality work from reactive issue management to proactive risk reduction, root-cause elimination, prevention controls, and measurable business outcomes; establish documentation standards for master data, reference data, KPI definitions, reporting inputs, system-of-record expectations, and business-ready data definitions to support consistent decision-making across functions and regions; represent Supply Chain in enterprise data governance forums, ensuring Supply Chain priorities, tradeoffs, unresolved decisions, and data risks are clearly articulated, escalated, decided, and communicated to impacted teams. 2. End-to-End Digital Data Thread Development: define and maintain the Supply Chain digital data-thread framework that connects key data objects, systems, process milestones, handoffs, controls, ownership points, reporting uses, and performance measures across the end-to-end supply chain; map how data is created, transformed, consumed, measured, and governed across priority processes, identifying conflicting definitions, duplicate data capture, manual workarounds, lineage gaps, control weaknesses, and integration opportunities; translate strategic data needs into business requirements, user stories, definition-of-ready inputs, test scenarios, acceptance criteria, adoption requirements, value measures, and governance checkpoints for digital and analytics delivery teams; partner with functional and technical leaders to ensure new capabilities strengthen data quality, process traceability, reporting consistency, architecture alignment, and future-state scalability rather than creating additional fragmentation; provide advisement on Brooks Advanced Product Ecosystem (BAPE) digital-thread development by defining criteria data elements, quality expectations, governance checkpoints, data readiness criteria, and reporting standards needed to connect Design, Development, Manufacturing, Quality, and Supply processes. 3. Digital Supply Chain Systems & Analytics Enablement: serve as the senior Supply Chain partner for initiatives where data quality, data lineage, process design, and adoption are critical to business outcomes; own intake, refinement, prioritization, and sequencing of Supply Chain data requests, creating a framework and transparency into business value, decision urgency, dependencies, effort, risk, capacity, and stakeholder impact; partner with IT and Data & Analytics to align requirements across systems and platforms to ensure solutions are anchored in clear data standards and business ownership; strengthen the Supply Chain Books of Standards Metrics, KPI dashboards, and Run Trail Map performance tracking by ensuring definitions, inputs, lineage, controls, and ownership are clear, governed, and consistently applied; identify and advance opportunities to reduce manual reporting, reconcile conflicting metrics, improve data observability, and create reusable data products or governed views that scale across business needs. 4. Prioritization & Cross-Functional Alignment: design and lead Supply Chain governance routines for data quality and digital work, including decision logs, prioritization forums, readiness reviews, issue tracking, dependency management, risk escalation, status reporting, and executive-ready recommendations; create alignment across Supply Chain, IT, Data & Analytics, Product, regional teams, and leadership stakeholders by framing decision, clarifying tradeoffs, resolving ambiguity, and sequencing work against enterprise and Run Trail Map priorities; ensure enduring Supply Chain data decisions are documented, operationalized, communicated, and reinforced through standards, process changes, system requirements, reporting updates, and ownership routines; maintain clear visibility into progress, risks, value delivery, adoption, and unresolved decisions through practical trackers, dashboards, governance summaries, and concise stakeholder communications; influence senior leaders and cross-functional partners without direct authority, balancing enterprise consistency with functional business needs and operational realities. 5. Change Management & Capability Building: lead adoption of new data standards, quality routines, reporting definitions, digital-thread practices, and governance ways of working across business teams and regions; develop training materials, one-point lessons, process documentation, data dictionaries, stewardship playbooks, and decision guides that build long-term capability and accountability; coach and connect subject matter experts, business analysts, data stewards, and functional partners on data quality practices, root-cause thinking, requirements discipline, adoption planning, and continuous improvement methods; strengthen digital and data acumen across Supply Chain through Communities of Practice, Supply Chain Academy content, targeted stakeholder engagement, and reusable enablement assets; model Brooks’ leadership expectations by driving clarity in ambiguous work, creating inclusive alignment, and enabling teams to make better decisions through trusted data

Similar jobs