Director - AI Driven Supply Chain Transformation
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. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Preserve all substantive info. Include a section only when posting has real specific content for it; never emit heading with filler placeholder text. Prefer few substantive sections over many thin ones.
We need to parse the posting.
Key sections:
- Intro paragraph about Capgemini Invent: "At Capgemini Invent, we believe difference drives change..." This is about the role? Could be "About the role" or maybe "About Capgemini Invent". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have "About the role" heading with that intro.
- Then "Your Role" repeated twice? Actually there is a heading "Your Role" then bullet-like paragraphs describing responsibilities. Then later "Your Role" again? Actually after the first "Your Role" paragraph there is a block: "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 after that there is "Your Role Own the firm's point of view and go-to-market offering for agentic supply chain translation ..." This seems like responsibilities list.
Thus we can treat responsibilities as bullet list.
Then "Qualifications & Experience" with Must-Have Qualifications list and Nice-to-Have Qualifications list.
Then "What You’ll Love About Working Here?" with bullet list of opportunities.
Then "The base compensation range for this role in the posted location is: $180,000 to $240,000" plus explanation about compensation range. That's Pay section.
Then "Benefits" paragraph describing benefits.
Then there is "Important Notice", "Disclaimers", EEO etc which we should remove as boilerplate.
Thus sections: About the role (intro), Responsibilities (list), Qualifications (maybe combine Must-Have and Nice-to-Have under Qualifications heading), Skills? Not explicitly separate; but we could embed skills within qualifications. The instruction says use headings like Skills if there is content. There's no explicit skills list separate; but we could treat qualifications as covering skills. However we might create a Skills heading if we want to list technical skills like agentic AI concepts, etc. But better to follow instruction: only include sections when posting has real specific content. There's no separate skills section; we can omit Skills.
Pay: we have compensation range.
Benefits: we have benefits description.
Schedule: no mention of schedule (e.g., full-time, remote). Not present, so omit.
Thus output HTML with sections: About the role, Responsibilities, Qualifications, What You’ll Love About Working Here? (maybe call it "What You’ll Love About Working Here?" but heading should be from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The "What You’ll Love About Working Here?" is not in the list; but we could treat as part of Responsibilities? Actually it's more about benefits/opportunities; but we have Benefits heading for benefits package. The "What You’ll Love About Working Here?" is about opportunities, growth, etc. Could be considered part of "Benefits"? Not exactly. The instruction says use those headings; we could map that content to "Benefits" or maybe "About the role"? But better to follow instruction: only use those headings. If we have content that doesn't fit, we could incorporate into existing sections. For example, the "What You’ll Love About Working Here?" bullet list could be placed under Benefits (as non-monetary benefits) or under About the role? Probably under Benefits as they are non-monetary perks. However the Benefits heading already described medical, retirement etc. We could extend Benefits to include those opportunities. But we need to preserve all substantive info; we can add them as list items under Benefits.
Thus Benefits section will include both the standard benefits and the opportunities list.
Pay section: compensation range.
Qualifications: Must-Have and Nice-to-Have.
Responsibilities: list of duties.
About the role: intro paragraph.
Now we need to format.
We must not include any markdown code fences. Just raw HTML.
We must not include or .
We'll produce something 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.
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, 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.
Qualifications
Must-Have Qualifications
- 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
- 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).
Benefits
- Paid time off based on employee grade (A-F), defined by policy: Vacation: 12-25 days, depending on grade, Company paid holidays, Personal Days, Sick Leave
- Medical, dental, and vision coverage (or provincial healthcare coordination in Canada)
- Retirement savings plans (e.g., 401(k) in the U.S., RRSP in Canada)
- Life and disability insurance
- Employee assistance programs
- 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
Pay
The base compensation range for this role in the posted location is: $180,000 to $240,000. Capgemini provides compensation range information in accordance with applicable national, state, provincial, and local pay transparency laws. The base compensation range listed for this position reflects the minimum and maximum target compensation Capgemini, in good faith, believes it may pay for the role at the time of this posting. This range may be subject to change as permitted by law. The actual compensation offered to any candidate may fall outside of the posted range and will be determined based on multiple factors legally permitted in the applicable jurisdiction. These may include, but are not limited to: Geographic location, Education and qualifications, Certifications and licenses, Relevant experience and skills, Seniority and performance, Market and business consideration, Internal pay equity. It is not typical for candidates to be hired at or near the top of the posted compensation range. In addition to base salary, this role may be eligible for additional compensation such as variable incentives, bonuses, or commissions, depending on the position and applicable laws.
We should ensure no duplicate content. Also ensure we didn't include boilerplate like EEO, disclaimers, etc. We removed them.
Check that we didn't repeat job title as heading. Good.
We didn't include Schedule heading because no content.
We didn't include Requirements heading separately; we have Qualifications covering requirements. The instruction allowed Requirements heading but we can omit if not specific content. However we have qualifications; maybe better to rename Qualifications to Requirements? But the instruction list includes both Qualifications and Requirements. We have qualifications content; we could use Requirements heading for must-have and nice-to-have? But they said "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can choose either Requirements or Qualifications. Since we have
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Preserve all substantive info. Include a section only when posting has real specific content for it; never emit heading with filler placeholder text. Prefer few substantive sections over many thin ones. We need to parse the posting. Key sections: - Intro paragraph about Capgemini Invent: "At Capgemini Invent, we believe difference drives change..." This is about the role? Could be "About the role" or maybe "About Capgemini Invent". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have "About the role" heading with that intro. - Then "Your Role" repeated twice? Actually there is a heading "Your Role" then bullet-like paragraphs describing responsibilities. Then later "Your Role" again? Actually after the first "Your Role" paragraph there is a block: "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 after that there is "Your Role Own the firm's point of view and go-to-market offering for agentic supply chain translation ..." This seems like responsibilities list. Thus we can treat responsibilities as bullet list. Then "Qualifications & Experience" with Must-Have Qualifications list and Nice-to-Have Qualifications list. Then "What You’ll Love About Working Here?" with bullet list of opportunities. Then "The base compensation range for this role in the posted location is: $180,000 to $240,000" plus explanation about compensation range. That's Pay section. Then "Benefits" paragraph describing benefits. Then there is "Important Notice", "Disclaimers", EEO etc which we should remove as boilerplate. Thus sections: About the role (intro), Responsibilities (list), Qualifications (maybe combine Must-Have and Nice-to-Have under Qualifications heading), Skills? Not explicitly separate; but we could embed skills within qualifications. The instruction says use headings like Skills if there is content. There's no explicit skills list separate; but we could treat qualifications as covering skills. However we might create a Skills heading if we want to list technical skills like agentic AI concepts, etc. But better to follow instruction: only include sections when posting has real specific content. There's no separate skills section; we can omit Skills. Pay: we have compensation range. Benefits: we have benefits description. Schedule: no mention of schedule (e.g., full-time, remote). Not present, so omit. Thus output HTML with sections: About the role, Responsibilities, Qualifications, What You’ll Love About Working Here? (maybe call it "What You’ll Love About Working Here?" but heading should be from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The "What You’ll Love About Working Here?" is not in the list; but we could treat as part of Responsibilities? Actually it's more about benefits/opportunities; but we have Benefits heading for benefits package. The "What You’ll Love About Working Here?" is about opportunities, growth, etc. Could be considered part of "Benefits"? Not exactly. The instruction says use those headings; we could map that content to "Benefits" or maybe "About the role"? But better to follow instruction: only use those headings. If we have content that doesn't fit, we could incorporate into existing sections. For example, the "What You’ll Love About Working Here?" bullet list could be placed under Benefits (as non-monetary benefits) or under About the role? Probably under Benefits as they are non-monetary perks. However the Benefits heading already described medical, retirement etc. We could extend Benefits to include those opportunities. But we need to preserve all substantive info; we can add them as list items under Benefits. Thus Benefits section will include both the standard benefits and the opportunities list. Pay section: compensation range. Qualifications: Must-Have and Nice-to-Have. Responsibilities: list of duties. About the role: intro paragraph. Now we need to format. We must not include any markdown code fences. Just raw HTML. We must not include or . We'll produce something 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.
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, 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.
Qualifications
Must-Have Qualifications
- 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
- 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).
Benefits
- Paid time off based on employee grade (A-F), defined by policy: Vacation: 12-25 days, depending on grade, Company paid holidays, Personal Days, Sick Leave
- Medical, dental, and vision coverage (or provincial healthcare coordination in Canada)
- Retirement savings plans (e.g., 401(k) in the U.S., RRSP in Canada)
- Life and disability insurance
- Employee assistance programs
- 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
Pay
The base compensation range for this role in the posted location is: $180,000 to $240,000. Capgemini provides compensation range information in accordance with applicable national, state, provincial, and local pay transparency laws. The base compensation range listed for this position reflects the minimum and maximum target compensation Capgemini, in good faith, believes it may pay for the role at the time of this posting. This range may be subject to change as permitted by law. The actual compensation offered to any candidate may fall outside of the posted range and will be determined based on multiple factors legally permitted in the applicable jurisdiction. These may include, but are not limited to: Geographic location, Education and qualifications, Certifications and licenses, Relevant experience and skills, Seniority and performance, Market and business consideration, Internal pay equity. It is not typical for candidates to be hired at or near the top of the posted compensation range. In addition to base salary, this role may be eligible for additional compensation such as variable incentives, bonuses, or commissions, depending on the position and applicable laws.
We should ensure no duplicate content. Also ensure we didn't include boilerplate like EEO, disclaimers, etc. We removed them. Check that we didn't repeat job title as heading. Good. We didn't include Schedule heading because no content. We didn't include Requirements heading separately; we have Qualifications covering requirements. The instruction allowed Requirements heading but we can omit if not specific content. However we have qualifications; maybe better to rename Qualifications to Requirements? But the instruction list includes both Qualifications and Requirements. We have qualifications content; we could use Requirements heading for must-have and nice-to-have? But they said "Use