Director - AI Driven Supply Chain Transformation

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. 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. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones. We need to parse the posting. Key content: - Intro paragraph about Capgemini Invent, difference drives change, etc. That's "About the role"? Actually "Your Role" sections. - "Your Role Sitting within Capgemini Invent's Data Driven Transformation capability, this Director role owns the point of view, offering, and delivery standard for how agentic AI moves supply chains from copilot-style productivity tools to orchestrated, autonomous decision-making. You will define where human judgment stays in the loop, where it moves to 'human-on-the-loop' oversight, and how clients govern that shift safely at enterprise scale." - Then "Your Role" again? Actually they repeated "Your Role" heading then bullet list of responsibilities. Let's extract responsibilities bullet list: - Own the firm's point of view and go-to-market offering for agentic supply chain translation - translating agent orchestration, multi-agent workflows, and autonomous decision systems into client-ready value cases (not just proofs of concept). - Lead redesign of end-to-end supply chain decision architecture - demand-supply balancing, exception management, scenario planning - where agents coordinate across functions rather than operating as isolated copilots. - Set and enforce governance standards for agentic deployments: autonomy boundaries, human-in-the-loop vs. human-on-the-loop design, audit trails, and alignment with emerging regulatory frameworks (EU AI Act, NIST AI RMF). - Own alliance and technology partnerships relevant to agentic orchestration (e.g., Microsoft/Copilot, SAP, AWS/Azure agent platforms, Kinaxis, o9) - co-develop assets and joint go-to-market motions. - Drive practice/offering P&L: revenue targets, pipeline ownership, deal shaping, and investment decisions for the agentic supply chain offering within Data Driven Transformation. - Advise C-suite (CSCO, CDO, CTO) on the total cost and value of agentic transformation - infrastructure, governance, change management, and 'Agent FinOps' - not just the technology narrative. - Build and scale a team spanning supply chain domain expertise and agentic engineering literacy (agent frameworks, RAG, orchestration patterns); set technical hiring bar and career paths. - Publish thought leadership establishing Capgemini's differentiated point of view. These are responsibilities. Qualifications & Experience: Must-Have Qualifications list: - 15+ years in supply chain transformation, including 10+ years in consulting/advisory with P&L or offering-ownership accountability. - Demonstrated experience taking clients from AI pilot/copilot deployments to scaled, governed, autonomous or semi-autonomous workflows. - Working fluency in agentic AI concepts and architecture - agent orchestration, multi-agent systems, RAG, relevant protocols (MCP/A2A) - sufficient to be technically credible with CTO/CDO buyers, even if not hands-on coding. - Proven business development ownership - Experience building or enforcing AI governance frameworks: risk tiering, autonomy boundaries, audit/compliance alignment. - Bachelor's degree required. Nice-to-Have Qualifications list: - MBA or advanced technical degree. - Existing ownership of a technology alliance relationship (Microsoft/Copilot, SAP, AWS/Azure agent platforms, Kinaxis, o9) with a track record of joint go-to-market motions. - Hands-on exposure to agent frameworks (LangChain, LangGraph) or vector/graph databases - not required to code, but a strong signal of technical depth. - Published thought leadership or external speaking on agentic AI or supply chain transformation. - Familiarity with specific regulatory frameworks (EU AI Act, NIST AI RMF, ISO/IEC 42001). - Industry vertical depth in a priority sector (CPG, Life Sciences, Manufacturing, Retail). What You’ll Love About Working Here? list: - You’ll Have The Opportunity To Build a network within the Capgemini Group and contribute to the education of other Business Units around practice offerings to support existing account expansion - Play a significant role in client proposals and RFI/RFP responses from initial brief to final sales presentations - Nurture and expand existing account relationships - Identify potential personal business relationships that can be leveraged by the practice to develop new business - Identify potential project extension and expansion opportunities while staffed on projects - Support the development of thought leadership and innovative offerings as they relate to AI/Data Science, Digital Customer Analytics, and Operational Analytics. - Support the upskilling of the team members on topics related to Data & Analytics Compensation: "The base compensation range for this role in the posted location is: $180,000 to $240,000". Also description about compensation range, etc. We need Pay section only if posting actually states them. It does state base compensation range. So we can include Pay section with that range. Also mention that additional compensation may be eligible (variable incentives, bonuses, commissions). That is part of compensation description. We'll include that in Pay section. Benefits: They have a Benefits paragraph describing benefits. So we include Benefits section. Schedule: Not mentioned. No schedule info. So we should NOT create Schedule section. Skills: Not explicitly a separate list; but we could incorporate skills within Qualifications or Responsibilities. The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content. We have: - About the role: Could be the introductory paragraph describing the role and Capgemini Invent. That seems appropriate. - Responsibilities: The bullet list we extracted. - Qualifications: Could combine Must-Have and Nice-to-Have under Qualifications. Or separate Requirements? The instruction includes Requirements as a possible heading. We could put Must-Have under Requirements and Nice-to-Have under Qualifications? But they said "Prefer a few substantive sections over many thin ones." So maybe combine into one Qualifications section that includes both must-have and nice-to-have, maybe with subheadings? But we cannot add extra headings beyond the allowed ones? We can still use

  for section headings only; we could have subheadings using

  ? Not specified but likely not needed. Better to have two sections: Requirements (must-have) and Qualifications (nice-to-have). However they said prefer few substantive sections over many thin ones. Having both may be okay if they are substantive. But we could also have one Qualifications section that includes both must-have and nice-to-have, with bullet lists separated by headings inside? But that would be extra headings inside the section, not allowed? The instruction only says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings inside, but to be safe we can just have one Qualifications section containing both must-have and nice-to-have as separate bullet lists with maybe a

  introducing each. That would be one section. We also have "What You’ll Love About Working Here?" which could be considered Benefits? Actually it's more about role perks, not benefits. Could be "About the role" or maybe "Skills"? Not exactly. Could be considered "About the role" or maybe we could create a section "What You’ll Love" but not in allowed headings. So we might incorporate that into About the role or maybe into Responsibilities? It's more about opportunities. Could be considered part of "About the role". We'll include it in About the role as additional prose. Thus sections: - About the role: includes intro paragraph about Capgemini Invent, the role description, and the "What You’ll Love About Working Here?" bullet list. - Responsibilities: bullet list of duties. - Qualifications: includes Must-Have and Nice-to-Have bullet lists. - Benefits: bullet list of benefits (maybe as

  • ). - Pay: includes base compensation range and note about variable incentives. We should not include Schedule. We must not repeat job title as heading. No job title appears. We must not include Job ID/requisition numbers. We must remove boilerplate: EEO, disclaimers, legal, etc. So we need to strip out all that stuff after benefits: the "Important Notice", "Disclaimers", "Capgemini is an Equal Opportunity Employer", etc. Also the paragraph about Capgemini being a global business etc at the end. That's boilerplate; we should remove. Also remove "Click the following link for more information on your rights as an Applicant in the United States." etc. Also remove "Physical, mental, sensory or environmental demands may be referenced..." etc. Also remove "Capgemini is committed to providing reasonable accommodation..." etc. Also remove "Please be aware that Capgemini may capture your image..." etc. Also remove "Click the following link for more information on your rights as an Applicant in the United States." etc. Also remove the final paragraph about Capgemini being a global business etc. Thus we keep only substantive content: intro, role description, responsibilities, qualifications, what you love, benefits, pay. Now we need to format. We'll output HTML fragment like:

    About the role

    At Capgemini Invent, we believe difference drives change. As inventive transformation consultants, we blend our strategic, creative and scientific capabilities, collaborating closely with clients to deliver cutting-edge solutions. Join us to drive transformation tailored to our client's challenges of today and tomorrow. Informed and validated by science and data. Superpowered by creativity and design. All underpinned by technology created with purpose. Your Role Sitting within Capgemini Invent's Data Driven Transformation capability, this Director role owns the point of view, offering, and delivery standard for how agentic AI moves supply chains from copilot-style productivity tools to orchestrated, autonomous decision-making. You will define where human judgment stays in the loop, where it moves to 'human-on-the-loop' oversight, and how clients govern that shift safely at enterprise scale.

    You’ll Have The Opportunity To Build a network within the Capgemini Group and contribute to the education of other Business Units around practice offerings to support existing account expansion Play a significant role in client proposals and RFI/RFP responses from initial brief to final sales presentations Nurture and expand existing account relationships Identify potential personal business relationships that can be leveraged by the practice to develop new business Identify potential project extension and expansion opportunities while staffed on projects Support the development of thought leadership and innovative offerings as they relate to AI/Data Science, Digital Customer Analytics, and Operational Analytics. Support the upskilling of the team members on topics related to Data & Analytics

    But the "What You’ll Love..." list should be a
    • . So we need to convert that to list. Thus after the intro paragraph, we can have a
      with each bullet as
      • . Now Responsibilities:

        Responsibilities

        • Own the firm's point of view and go-to-market offering for agentic supply chain transformation - translating agent orchestration, multi-agent workflows, and autonomous decision systems into client-ready value cases (not just proofs of concept).
        • Lead redesign of end-to-end supply chain decision architecture - demand-supply balancing, exception management, scenario planning - where agents coordinate across functions rather than operating as isolated copilots.
        • Set and enforce governance standards for agentic deployments: autonomy boundaries,