Jobs · Purchasing · New York

Senior Strategic Sourcing Manager

Moog Inc. · Buffalo, NY · 1 mo ago
Purchasing$135k–$180k/yrFull-time
We need to output HTML fragment with sections: About the role? The posting includes description of company culture at start, but not a heading. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include a section only when posting has real specific content for it. We need to parse content. We have: - Intro paragraph about Moog culture: "Moog is a performance culture..." This could be considered "About the role"? Actually it's about company. Could be "About the role" maybe but it's not role-specific. However we can treat as "About the role" maybe. But we need to preserve all substantive info. The intro is substantive. We could put it under

About the role

with a

. That seems okay. - Job Title line: "Senior Strategic Sourcing Manager" but we must NOT repeat the job title as a heading. So we can ignore that line or put in a short

as metadata? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." Job title is not a heading but we already have it displayed elsewhere; we should not repeat as heading. We can maybe include it in a short

at top? But they said "the page already shows it" and "do NOT repeat the job title as a heading". So we can omit it entirely or put in a

as metadata. Safer to omit. - Reporting To, Work Schedule: these are metadata. Could fold into a short

. We'll include a

with "Reporting To: Director, Strategic Sourcing. Work Schedule: Fully Remote or Hybrid if Local – Buffalo, NY." - Then description of role responsibilities: "The Senior Strategic Sourcing Manager leads..." This is responsibilities. So we can have

Responsibilities

with a

containing that paragraph. - Then "Role To be considered for the Senior Strategic Sourcing Manager role, here’s what you’ll typically need to bring with you:" This is requirements/qualifications. We'll split maybe into Requirements and Qualifications? The instruction: prefer few substantive sections over many thin ones. Could combine Requirements and Qualifications into one section? But we have headings for both. We could put under

Requirements

the list of bullet points (Bachelor's degree etc). Then maybe

Qualifications

for preferred qualifications? However the text includes both required and preferred. Could just have one section "Requirements" covering all. But we have to follow instruction: use headings only when posting has real specific content for it. It does have content for Requirements (education, experience). It also has content for Qualifications (maybe same). To avoid thin sections, we can combine into one section "Requirements". Or we could have "Requirements" and "Qualifications" but risk thin. Better to combine. Thus:

Requirements

with a
  • list of items. List items: - Bachelor’s degree in Supply Chain Management, Business, Engineering, or a related field. - Advanced degree and/or professional Supply Chain certification preferred. - 7+ years of global supply chain, strategic sourcing, and leadership experience. - Demonstrated experience negotiating and managing complex supplier contracts and long-term agreements. - Strong knowledge of supply chain network design, supplier development, strategic sourcing, and risk management. - Proven ability to influence and collaborate within a global, cross-functional, and geographically dispersed organization. - Strong communication, negotiation, and presentation skills. - Ability to manage multiple priorities and deliver results in a fast-paced environment. - Knowledge of international trade, import/export compliance, and global regulatory requirements is preferred. - Ability and willingness to travel globally up to 30%. We need to preserve all substantive info. The bullet list includes both required and preferred; we keep as is. - Then "As a Senior Strategic Sourcing Manager, You Will" followed by list of duties. That's responsibilities again but more detailed. Could merge with earlier responsibilities paragraph. But we already have responsibilities section; we could add more detail there. Could either create a second responsibilities section (thin) or extend the first. Better to extend the responsibilities

    to include the list. However we need to use

    • for any list of duties/requirements/benefits. So we should turn the duties list into a
        . So responsibilities section could have a

        summarizing then a

          for duties. Or we could just have a
            directly under responsibilities heading. The instruction: Use
            • for any list of duties/requirements/benefits, and

              for prose. So we can have a

              for introductory prose then

                for list. Thus responsibilities section:

                Responsibilities

                The Senior Strategic Sourcing Manager leads the development and execution of global sourcing strategies, supply chain network design, and end-to-end supplier lifecycle management. Supporting the Commercial Aircraft Group (CAG) and Integrated Supply Chain (ISC) organization, this role aligns sourcing strategies with broader business objectives and strategic initiatives. Key priorities include negotiating Long-Term Agreements (LTAs) to increase secured spend, regionalizing supply chains to support Moog operations, reducing supplier complexity, developing strategic supplier partnerships, and driving cost reduction initiatives. This position is responsible for a global spend portfolio exceeding $200M across machined components and complex assemblies.

                • Collaborate with key stakeholders to develop and execute both tactical and long-term strategic sourcing plans across assigned commodity groupings.
                • Provide strategic input to Make vs. Buy decisions and lead Buy-to-Buy and Make-to-Buy supplier transition initiatives.
                • Research, identify, and develop suppliers to create a high-performing supply chain network optimized for quality, lead time, vendor-managed inventory (VMI), continuity of supply, and total landed cost.
                • Provide proposal support for existing programs and new business pursuits.
                • Lead cross-functional supplier selection activities and determine optimal sourcing strategies, including single-source and multi-source approaches, to mitigate risk and maintain long-term competitiveness.
                • Develop supplier capabilities and competencies through strategic partnerships and supplier development initiatives.
                • Establish and manage the relationships, investments, training, and resources necessary to achieve supplier performance objectives.
                • Partner with global supply chain teams and business stakeholders to analyze supply and demand trends, evaluate lead times and total landed costs, and identify opportunities for continuous improvement.
                • Collaborate with Contracts and Legal teams to define, negotiate, and manage supplier contractual requirements and long-term agreements.
                • Serve as the senior escalation point for supplier performance and contractual issues and lead corrective action efforts when necessary.
                • Oversee supplier participation in New Product Introduction (NPI) activities in partnership with Program Management and business stakeholders.
                • Build and maintain effective long-term supplier partnerships while supporting regional and site supply chain teams with supplier relationship management and contract administration.
                • Lead, mentor, and develop a global Strategic Sourcing team, fostering accountability, engagement, and professional growth.
                - Then "How We Care For You" with subcategories: Financial Rewards, Work/Life Balance, Health & Welfare, Professional Skills Development, Collaborative and Welcoming Workplace, Additional site-specific benefits may be available. This is benefits. So we can have

                Benefits

                with a
                  list of each benefit category as items? Or we could keep prose. The instruction: Use
                  • for any list of duties/requirements/benefits. So we should list each benefit as
                  • . Could break down each bullet. Thus:

                    Benefits

                    • Financial Rewards: Great compensation package, annual profit sharing, matching 401(k), Employee Stock Purchase Plan, Flexible Spending Accounts, and Health Savings Accounts.
                    • Work/Life Balance: Flexible paid time off, company holidays, parental leave program, and relocation assistance.
                    • Health & Welfare: Comprehensive medical, dental, vision, life, disability, Employee Assistance Program (EAP), and supplemental benefit coverage.
                    • Professional Skills Development: Tuition assistance, mentorship, coaching opportunities, leadership development programs, and ongoing career growth support.
                    • Collaborative and Welcoming Workplace: Inclusive culture rooted in our values, supported by Employee Resource Groups and team-building activities.
                    • Additional site-specific benefits may be available.
                    - Then Salary Range Transparency: "Buffalo, NY $135,000.00–$180,000.00 Annually" plus disclaimer. This is Pay. So we need a

                    Pay

                    with

                    containing the salary range and disclaimer. The instruction: include a section ONLY when 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. Here we have specific salary range, so we include Pay. Thus:

                    Pay

                    Salary Range Transparency: Buffalo, NY $135,000.00–$180,000.00 Annually. Salary Range Disclaimer: The base salary range represents the low and high end of the Moog salary range for this position in the given work location. Actual salaries will vary depending on factors including but not limited to location, experience, and performance. The range(s) listed is just one component of Moog's total compensation package for employees. Other rewards may include annual bonuses, employee stock purchase plan, an open paid time off policy, and many region-specific benefits.

                    - Schedule: The posting includes Work Schedule: Fully Remote or Hybrid if Local – Buffalo, NY. That's specific content, so we should include a Schedule section. Thus:

                    Schedule

                    Fully Remote or Hybrid if Local – Buffalo, NY.

                    We also have Reporting To line; we could include that in a short

                    under maybe a generic "About the role" or separate metadata. Since we already have About the role section with intro paragraph, we could add Reporting To and Work Schedule there? But we already used Work Schedule for Schedule section. Reporting To could be included in About the role paragraph as a short sentence. However we should not duplicate. Let's incorporate Reporting To into About the role

                    after the intro. Thus About the role:

                    About the role

                    Moog is a performance culture that empowers people to achieve great things. Our people enjoy solving interesting technical challenges in a culture where everyone trusts each other to do the right thing. For you, working with us can mean deeper job satisfaction, better rewards, and a great quality of life inside and outside of work. Reporting To: Director, Strategic Sourcing.

                    But we already have Schedule section for work schedule. So we keep that separate. Now we need to ensure we didn't include any boilerplate like EEO, legal, scam warning, application instructions, cookie/navigation. We removed those at end. Check that we didn't repeat job title as heading. We didn't. We used

                    for each section: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Did we include Qualifications? We combined into Requirements. That's okay. We didn't include Skills section separately; we could incorporate skills into Requirements but it's fine. We need to ensure we used
                    • for any list of duties/requirements/benefits. We have: - Requirements: we used
                      • for each bullet. - Responsibilities: we used
                        • for duties list

Similar jobs