AI Transformation Lead - Supply Chain & Procurement

We need to output HTML fragment with sections: h3 headings for sections present: About the role? Actually we have Company Overview, Position Overview, Job Responsibilities (with subheadings), Minimum Qualifications, Preferred Qualifications, Critical Success Factors, What Success Looks Like, Other (but we should drop boilerplate like EEO, etc). We should not repeat job title. We should not include Job ID etc. We should include only sections with real content. We need to use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). However the headings we have may not exactly match those; but we must use

for section headings. Likely we should map content to those generic headings: About the role (company overview + position overview), Responsibilities (job responsibilities), Requirements (minimum qualifications), Qualifications (preferred qualifications), Skills maybe not present, Benefits maybe not present, Pay not present, Schedule not present. We should only include sections that have real content. So we will have About the role, Responsibilities, Requirements, Qualifications, Critical Success Factors? Not in list but we could treat as maybe Skills? But instructions: 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. But we should prefer those headings if applicable. However we have sections like Critical Success Factors and What Success Looks Like which are not in the list but could be considered as Skills? Might be better to include them as separate headings? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should use those headings for sections; but we can also use other headings if needed? It says "e.g." meaning examples, not limited. However later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can include any heading that matches content. Probably safe to use headings that reflect content: About the role, Responsibilities, Requirements, Qualifications, Critical Success Factors, What Success Looks Like. But the examples list didn't include those; but it's okay as examples. However to be safe, we could map Critical Success Factors to Skills? Not exactly. Could treat as Skills. What Success Looks Like could be maybe Outcomes? Not in list. Might be better to just use the examples headings and put content under them accordingly, even if not perfect. But we must preserve all substantive information; we cannot lose info. If we put Critical Success Factors under Skills heading, it's still preserved. Similarly What Success Looks Like could go under Responsibilities? Not ideal. Better to follow 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 using those. I'd produce those headings only if we have content. We have content for About the role (company overview + position overview). Responsibilities (job responsibilities). Requirements (minimum qualifications). Qualifications (preferred qualifications). Skills maybe we can put Critical Success Factors under Skills. Benefits, Pay, Schedule not present so omit. Thus output:

About the role

Company Overview ... Position Overview ...

But we need to preserve all substantive information. We'll combine company overview and position overview into a single

maybe multiple paragraphs. Could split into two

but still under same heading. Then Responsibilities: we need

• for any list of duties/requirements/benefits. The responsibilities have subheadings (AI Strategy & Transformation, Process Redesign & Continuous Improvement, Business Engagement & Change Management, Value Realization & Performance Management, Cross-Functional Collaboration). We could treat each as a
• with subpoints? The instruction: Use
  • for any list of duties/requirements/benefits. So we should produce a list where each responsibility area is a
  • . Inside each
  • we can have paragraphs describing details. That's acceptable. Then Requirements: list of minimum qualifications. Use
    • . Then Qualifications: list of preferred qualifications. Use
      • . Then Skills: maybe Critical Success Factors as list. We must not include boilerplate like EEO, etc. Also drop "Other" section that contains EEO etc. So we omit that. We must not include navigation, cookie, legal, EEO, etc. We must not repeat job title. We must not include Job ID etc. We must not include application instructions. We must not include duplicated lines. Now craft HTML. Let's extract content. Company Overview paragraph: "Imagine Everything. Build the Future with Hexion. At Hexion, we push boundaries, rethink possibilities, and create real impact. We activate science to deliver progress—developing breakthrough solutions that strengthen industries, protect communities, and drive a more sustainable future. This is where bold thinkers, problem-solvers, and innovators come together to shape what’s next. Whether you're engineering advanced materials, transforming manufacturing technologies, or leading strategic innovation, your ideas and actions leave a lasting mark. We cultivate an inclusive culture of growth, collaboration, and accountability, ensuring every contribution propels us forward. We don’t follow the status quo—we challenge it, disrupt it, and improve it. Every role at Hexion is part of something bigger. We invest in innovation, sustainability, and continuous development—equipping you with the tools, training, and opportunities to excel. With an unwavering commitment to safety, partnership, belonging, and impact, we empower you to lead change and strengthen industries worldwide. Your Future Starts Here. If you’re ready to push limits, reimagine what’s possible, and create the extraordinary, Hexion is where you belong. Anything is possible when you imagine everything." Position Overview: "The Manager, AI Transformation will help shape and accelerate the adoption of artificial intelligence, automation, and advanced analytics across Supply Chain and Procurement. Reporting directly to the Sr. Director, AI Transformation, Data & Intelligence, this role serves as a strategic business partner focused on identifying high-value opportunities, redesigning business processes, driving organizational adoption, and delivering measurable business outcomes. The successful candidate will bridge business and technology teams to ensure AI-enabled solutions are aligned to operational priorities, integrated into business processes, and generate meaningful value. The ideal candidate combines deep Supply Chain and Procurement expertise with strong continuous improvement, change management, and business transformation capabilities. They are energized by emerging technologies and are passionate about helping organizations work smarter, faster, and more effectively." We'll combine these into maybe two paragraphs under About the role. Responsibilities: list each major heading with its bullet points. Let's extract details: AI Strategy & Transformation: - Identify and prioritize opportunities where AI, automation, and advanced analytics can improve business performance. - Develop and maintain a portfolio of AI transformation initiatives aligned with strategic business objectives. - Partner with business leaders to evaluate opportunities, define expected outcomes, and build implementation roadmaps. - Establish frameworks for evaluating, prioritizing, and governing AI initiatives across Supply Chain and Procurement. Process Redesign & Continuous Improvement: - Lead process assessment and redesign efforts to maximize the value of AI-enabled solutions. - Challenge existing ways of working and identify opportunities to simplify, standardize, automate, or eliminate work. - Apply continuous improvement methodologies to drive productivity, efficiency, service, quality, and decision-making improvements. - Ensure AI solutions are embedded into business processes rather than implemented as standalone tools. Business Engagement & Change Management: - Facilitate workshops and working sessions with stakeholders to identify pain points, opportunities, and use cases. - Serve as a trusted advisor to Supply Chain, Procurement, Manufacturing, and cross-functional business teams. - Develop change management and adoption strategies that ensure successful implementation and sustained usage. - Build awareness and enthusiasm for AI capabilities while helping teams navigate organizational change. Value Realization & Performance Management: - Define business cases, success metrics, and value realization plans for AI initiatives. - Track and report benefits, including productivity improvements, cost savings, working capital impacts, risk reduction, and service improvements. - Monitor adoption and business outcomes to ensure initiatives deliver expected value. - Recommend course corrections or enhancements when initiatives are not meeting objectives. Cross-Functional Collaboration: - Act as the primary liaison between business stakeholders and technical delivery teams. - Translate business challenges into clearly defined requirements and use cases. - Collaborate with Data & Analytics, IT, Digital, and external partners to support solution delivery. - Drive alignment across functions where end-to-end process opportunities exist. Minimum Qualifications: - Bachelor's degree in Supply Chain, Operations, Business, Engineering, Finance, or a related field. - 7+ years of experience in Supply Chain, Procurement, Operations, or related business functions. - Demonstrated experience leading business transformation, process improvement, or digital transformation initiatives. - Strong understanding of end-to-end Supply Chain and Procurement processes. - Experience developing business cases and measuring financial and operational outcomes. - Strong facilitation, stakeholder management, and communication skills. - Proven ability to influence without direct authority. - Ability to work effectively across business and technical teams. Preferred Qualifications: - Experience supporting AI, automation, digital transformation, or advanced analytics initiatives. - Experience with S&OP, Integrated Business Planning, Procurement, Sourcing, Manufacturing, Logistics, or Planning processes. - Lean, Six Sigma, Change Management, or Project Management certifications. - Experience with platforms such as Microsoft Copilot, Power Platform, workflow automation tools, or enterprise AI solutions. - MBA or advanced degree. Critical Success Factors (maybe Skills): - The Ideal Candidate Sees business problems before they become business crises. - Understands where AI creates value and where it is simply a shiny object. - Thinks in terms of outcomes, not technology. - Can translate between operations leaders and technical teams. - Balances strategic thinking with practical execution. - Is naturally curious, adaptable, and energized by change. - Focuses relentlessly on adoption, value realization, and measurable business impact. What Success Looks Like (maybe could be under Skills or separate but we could put under Skills as well, but maybe better to put under a separate heading like "Outcomes"? Not in list. Could treat as Skills as well. But we already have Skills for Critical Success Factors. Could combine both under Skills heading as list items. That would preserve all. Thus under Skills heading we list both Critical Success Factors and What Success Looks Like items. Let's extract What Success Looks Like: - Established a prioritized AI transformation roadmap across Supply Chain and Procurement. - Implemented process redesign initiatives that successfully leverage AI and automation. - Delivered measurable business value through productivity, cost, service, and decision-quality improvements. - Increased adoption of AI-enabled tools and ways of working across business teams. - Built strong partnerships across Supply Chain, Procurement, Manufacturing, IT, Analytics, and other functional areas. - Created a repeatable framework for identifying, evaluating, governing, and scaling AI opportunities. Now we need to output HTML fragment only. We'll structure:

        About the role

        Company overview paragraph.

        Position overview paragraph.

        Responsibilities

        • AI Strategy & Transformation
          • Identify and prioritize opportunities where AI, automation, and advanced analytics can improve business performance.
          • Develop and maintain a portfolio of AI transformation initiatives aligned with strategic business objectives.
          • Partner with business leaders to evaluate opportunities, define expected outcomes, and build implementation roadmaps.
          • Establish frameworks for evaluating, prioritizing, and governing AI initiatives across Supply Chain and Procurement.
        ... etc. But note: we already have
        • for any list of duties/requirements/benefits. Using nested lists is okay but still
        • . Could also flatten: each responsibility area as a
        • with internal

          or

          . The instruction didn't forbid nested lists. We'll keep simple: