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. Preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Include a section only when posting has real, specific content for it — never emit 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 posting actually states them.
We need to parse the posting.
Key sections:
- Intro paragraph: "At Capgemini Invent, we believe difference drives change..." etc. That's about the role? Could be "About the role" or "About Capgemini Invent". We need to decide headings.
The posting includes:
- "Your Role" repeated twice? Actually there is "Your Role" then bullet points describing responsibilities.
- Then "Qualifications & Experience" with Must-Have Qualifications and Nice-to-Have Qualifications.
- Then "What You’ll Love About Working Here?" with bullet points.
- Then compensation: "The base compensation range for this role in the posted location is: $180,000 to $240,000" plus explanation.
- Then "Benefits" section describing benefits.
- Then "Important Notice", "Disclaimers", etc which are boilerplate (EEO, legal). Should be removed.
Thus we need sections: About the role (maybe intro), Responsibilities (Your Role bullet points), Qualifications (Must-Have and Nice-to-Have), What You’ll Love About Working Here? (maybe "Why Join Us" or "What You’ll Love"), Pay (compensation range), Benefits.
We must not include sections with filler. Pay is present; we have a specific range, so include Pay section.
Benefits: present; include Benefits section.
Schedule: not mentioned; do not include.
We must not repeat job title as heading.
We must use
for section headings.
We must use - for any list of duties/requirements/benefits, and
for prose.
Thus for each section we need to decide if content is list or prose.
- About the role: intro paragraph(s) maybe prose. Could be multiple paragraphs. We'll wrap in
.
- Responsibilities: bullet points under "Your Role". We'll make
- .
- Qualifications: Must-Have and Nice-to-Have. Could be two sub-sections? But we only have headings for Qualifications (maybe one). Inside we can have two lists: Must-Have Qualifications and Nice-to-Have Qualifications. Could be headings inside? Not allowed? Only headings allowed are those specified; we could still use
? Not specified. Better to keep within Qualifications section using
for intro and then
- for each list, maybe with a preceding or just plain text. But we must use
- for any list. So we can have two lists: one for Must-Have, one for Nice-to-Have. Could preface each with a
like "Must-Have Qualifications" then
. That's okay.
- What You’ll Love About Working Here?: bullet points; use - .
- Pay: we have compensation range and explanation. That's prose; could be
.
- Benefits: list of benefits; could be
- .
We must remove boilerplate: EEO, disclaimers, important notice, etc.
Also remove duplicated lines: The "Your Role" appears twice? Actually there is a duplicated heading "Your Role" then bullet list then later "Your Role Own the firm's point of view..." It seems the bullet list is under that heading. We'll just capture the bullet points after the first "Your Role". The second "Your Role" seems to be a repeat of the heading but then continues with responsibilities. We'll just treat all responsibilities as list.
We need to preserve all substantive information; do not invent or summarize away detail.
Let's extract the responsibilities bullet points from the text:
From after first "Your Role":
"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."
These are sentences separated by periods but no bullet markers. We need to turn each into a list item. Likely each sentence corresponds to a responsibility. We'll split by periods that end a sentence (but careful with abbreviations). We'll approximate.
List items:
1. 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).
2. 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.
3. 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).
4. 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.
5. Drive practice/offering P&L: revenue targets, pipeline ownership, deal shaping, and investment decisions for the agentic supply chain offering within Data Driven Transformation.
6. 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.
7. 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.
8. Publish thought leadership establishing Capgemini's differentiated point of view.
Now Qualifications:
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:
- 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).
Now "What You’ll Love About Working Here?" bullet points:
- 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
Now Pay: The base compensation range for this role in the posted location is: $180,000 to $240,000 plus explanation paragraph. We'll include that as prose.
Benefits: list of 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
- Other benefits as provided by local policy and eligibility
We should keep as list items.
Now we need to output HTML fragment only, no /, no markdown.
We'll structure:
About the role
Intro paragraph(s).
Responsibilities
- ...
...
Qualifications
Must-Have Qualifications
...
Nice-to-Have Qualifications
...
What You’ll Love About Working Here?
...
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
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Include a section only when posting has real, specific content for it — never emit 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 posting actually states them. We need to parse the posting. Key sections: - Intro paragraph: "At Capgemini Invent, we believe difference drives change..." etc. That's about the role? Could be "About the role" or "About Capgemini Invent". We need to decide headings. The posting includes: - "Your Role" repeated twice? Actually there is "Your Role" then bullet points describing responsibilities. - Then "Qualifications & Experience" with Must-Have Qualifications and Nice-to-Have Qualifications. - Then "What You’ll Love About Working Here?" with bullet points. - Then compensation: "The base compensation range for this role in the posted location is: $180,000 to $240,000" plus explanation. - Then "Benefits" section describing benefits. - Then "Important Notice", "Disclaimers", etc which are boilerplate (EEO, legal). Should be removed. Thus we need sections: About the role (maybe intro), Responsibilities (Your Role bullet points), Qualifications (Must-Have and Nice-to-Have), What You’ll Love About Working Here? (maybe "Why Join Us" or "What You’ll Love"), Pay (compensation range), Benefits. We must not include sections with filler. Pay is present; we have a specific range, so include Pay section. Benefits: present; include Benefits section. Schedule: not mentioned; do not include. We must not repeat job title as heading. We must use
for section headings.
We must use - for any list of duties/requirements/benefits, and
for prose.
Thus for each section we need to decide if content is list or prose.
- About the role: intro paragraph(s) maybe prose. Could be multiple paragraphs. We'll wrap in
.
- Responsibilities: bullet points under "Your Role". We'll make
- .
- Qualifications: Must-Have and Nice-to-Have. Could be two sub-sections? But we only have headings for Qualifications (maybe one). Inside we can have two lists: Must-Have Qualifications and Nice-to-Have Qualifications. Could be headings inside? Not allowed? Only headings allowed are those specified; we could still use
? Not specified. Better to keep within Qualifications section using
for intro and then
- for each list, maybe with a preceding or just plain text. But we must use
- for any list. So we can have two lists: one for Must-Have, one for Nice-to-Have. Could preface each with a
like "Must-Have Qualifications" then
. That's okay.
- What You’ll Love About Working Here?: bullet points; use - .
- Pay: we have compensation range and explanation. That's prose; could be
.
- Benefits: list of benefits; could be
- .
We must remove boilerplate: EEO, disclaimers, important notice, etc.
Also remove duplicated lines: The "Your Role" appears twice? Actually there is a duplicated heading "Your Role" then bullet list then later "Your Role Own the firm's point of view..." It seems the bullet list is under that heading. We'll just capture the bullet points after the first "Your Role". The second "Your Role" seems to be a repeat of the heading but then continues with responsibilities. We'll just treat all responsibilities as list.
We need to preserve all substantive information; do not invent or summarize away detail.
Let's extract the responsibilities bullet points from the text:
From after first "Your Role":
"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."
These are sentences separated by periods but no bullet markers. We need to turn each into a list item. Likely each sentence corresponds to a responsibility. We'll split by periods that end a sentence (but careful with abbreviations). We'll approximate.
List items:
1. 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).
2. 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.
3. 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).
4. 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.
5. Drive practice/offering P&L: revenue targets, pipeline ownership, deal shaping, and investment decisions for the agentic supply chain offering within Data Driven Transformation.
6. 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.
7. 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.
8. Publish thought leadership establishing Capgemini's differentiated point of view.
Now Qualifications:
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:
- 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).
Now "What You’ll Love About Working Here?" bullet points:
- 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
Now Pay: The base compensation range for this role in the posted location is: $180,000 to $240,000 plus explanation paragraph. We'll include that as prose.
Benefits: list of 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
- Other benefits as provided by local policy and eligibility
We should keep as list items.
Now we need to output HTML fragment only, no /, no markdown.
We'll structure:
About the role
Intro paragraph(s).
Responsibilities
- ...
...
Qualifications
Must-Have Qualifications
...
Nice-to-Have Qualifications
...
What You’ll Love About Working Here?
...
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
for prose. Thus for each section we need to decide if content is list or prose. - About the role: intro paragraph(s) maybe prose. Could be multiple paragraphs. We'll wrap in
. - Responsibilities: bullet points under "Your Role". We'll make
- .
- Qualifications: Must-Have and Nice-to-Have. Could be two sub-sections? But we only have headings for Qualifications (maybe one). Inside we can have two lists: Must-Have Qualifications and Nice-to-Have Qualifications. Could be headings inside? Not allowed? Only headings allowed are those specified; we could still use
? Not specified. Better to keep within Qualifications section using
for intro and then
- for each list, maybe with a preceding or just plain text. But we must use
- for any list. So we can have two lists: one for Must-Have, one for Nice-to-Have. Could preface each with a
like "Must-Have Qualifications" then
- . That's okay.
- What You’ll Love About Working Here?: bullet points; use
- .
- Pay: we have compensation range and explanation. That's prose; could be
. - Benefits: list of benefits; could be
- .
We must remove boilerplate: EEO, disclaimers, important notice, etc.
Also remove duplicated lines: The "Your Role" appears twice? Actually there is a duplicated heading "Your Role" then bullet list then later "Your Role Own the firm's point of view..." It seems the bullet list is under that heading. We'll just capture the bullet points after the first "Your Role". The second "Your Role" seems to be a repeat of the heading but then continues with responsibilities. We'll just treat all responsibilities as list.
We need to preserve all substantive information; do not invent or summarize away detail.
Let's extract the responsibilities bullet points from the text:
From after first "Your Role":
"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."
These are sentences separated by periods but no bullet markers. We need to turn each into a list item. Likely each sentence corresponds to a responsibility. We'll split by periods that end a sentence (but careful with abbreviations). We'll approximate.
List items:
1. 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).
2. 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.
3. 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).
4. 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.
5. Drive practice/offering P&L: revenue targets, pipeline ownership, deal shaping, and investment decisions for the agentic supply chain offering within Data Driven Transformation.
6. 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.
7. 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.
8. Publish thought leadership establishing Capgemini's differentiated point of view.
Now Qualifications:
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:
- 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).
Now "What You’ll Love About Working Here?" bullet points:
- 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
Now Pay: The base compensation range for this role in the posted location is: $180,000 to $240,000 plus explanation paragraph. We'll include that as prose.
Benefits: list of 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
- Other benefits as provided by local policy and eligibility
We should keep as list items.
Now we need to output HTML fragment only, no /, no markdown.
We'll structure:
About the role
Intro paragraph(s).
Responsibilities
- ... ...
Qualifications
Must-Have Qualifications
- ...
Nice-to-Have Qualifications
- ...
What You’ll Love About Working Here?
- ...
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
- .
We must remove boilerplate: EEO, disclaimers, important notice, etc.
Also remove duplicated lines: The "Your Role" appears twice? Actually there is a duplicated heading "Your Role" then bullet list then later "Your Role Own the firm's point of view..." It seems the bullet list is under that heading. We'll just capture the bullet points after the first "Your Role". The second "Your Role" seems to be a repeat of the heading but then continues with responsibilities. We'll just treat all responsibilities as list.
We need to preserve all substantive information; do not invent or summarize away detail.
Let's extract the responsibilities bullet points from the text:
From after first "Your Role":
"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."
These are sentences separated by periods but no bullet markers. We need to turn each into a list item. Likely each sentence corresponds to a responsibility. We'll split by periods that end a sentence (but careful with abbreviations). We'll approximate.
List items:
1. 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).
2. 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.
3. 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).
4. 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.
5. Drive practice/offering P&L: revenue targets, pipeline ownership, deal shaping, and investment decisions for the agentic supply chain offering within Data Driven Transformation.
6. 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.
7. 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.
8. Publish thought leadership establishing Capgemini's differentiated point of view.
Now Qualifications:
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:
- 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).
Now "What You’ll Love About Working Here?" bullet points:
- 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
Now Pay: The base compensation range for this role in the posted location is: $180,000 to $240,000 plus explanation paragraph. We'll include that as prose.
Benefits: list of 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
- Other benefits as provided by local policy and eligibility
We should keep as list items.
Now we need to output HTML fragment only, no /, no markdown.
We'll structure:
- .
- Pay: we have compensation range and explanation. That's prose; could be
- for any list. So we can have two lists: one for Must-Have, one for Nice-to-Have. Could preface each with a
- for each list, maybe with a preceding or just plain text. But we must use