Director - AI Driven Supply Chain Transformation
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID/requisition numbers as headings. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove boilerplate: 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 a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to decide which sections to include based on content.
We have:
- Intro: "At Capgemini Invent, we believe difference drives change..." This is about the company and role context. Could be "About the role" or maybe "About the role" includes description of role and context.
- Then "Your Role" repeated: includes bullet-like paragraphs describing responsibilities. We can treat as Responsibilities section.
- Then "Qualifications & Experience" with Must-Have Qualifications and Nice-to-Have Qualifications. Could be Requirements or Qualifications sections. The spec says we have headings: Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content accordingly.
We have qualifications (must-have, nice-to-have). Could put under "Qualifications". Also "Requirements" maybe similar. But we should avoid duplicate sections. Choose one: maybe "Qualifications" for must-have and nice-to-have. "Requirements" could be omitted if no separate list. But we have "Must-Have Qualifications" and "Nice-to-Have Qualifications". That's qualifications.
We also have "What You’ll Love About Working Here?" which is more about benefits/opportunities. Could be "Benefits" or maybe "Skills"? Actually it's about opportunities: building network, proposals, etc. That's more like "Responsibilities"? Not exactly. Could be "Benefits" but it's not compensation/benefits; it's more about role aspects. The spec says we should include Benefits only if posting actually states them. There is a Benefits section later: "Benefits Capgemini offers a comprehensive, non-negotiable benefits package..." So we definitely have Benefits.
Pay: there is base compensation range: $180,000 to $240,000. So we need a Pay section.
Schedule: not mentioned. So we should not include Schedule.
Skills: maybe we could include technical skills from qualifications? But we already have Qualifications. Could we also have Skills? The spec says we can include Skills if there is real specific content. The posting mentions "agentic AI concepts and architecture - agent orchestration, multi-agent systems, RAG, relevant protocols (MCP/A2A)" etc. That's more qualifications. Could treat as Skills but we already have Qualifications. To avoid thin sections, we might combine qualifications and skills into one Qualifications section. But spec says we have separate headings possible; we should prefer few substantive sections over many thin ones. So we can have: About the role, Responsibilities, Qualifications, Benefits, Pay. That's five sections.
We need to ensure we don't include filler like "commensurate with experience". Not present.
We need to remove duplicated lines: The "Your Role" appears twice; we should combine.
We need to remove boilerplate: EEO, disclaimer, etc.
We need to preserve all substantive information: include details about responsibilities, qualifications, benefits, pay.
We need to format using
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
Thus for each section, we need to decide if content is list or prose.
About the role: likely prose describing role context. Could be a
.
Responsibilities: list of duties. Use
- .
Qualifications: list of must-have and nice-to-have. Could be two sublists? Could be
- for each qualification. Might separate must-have and nice-to-have as separate
with headings? But we cannot add extra headings besides . Could we include a
introducing then list? Probably we can have a
then
. That's fine.
Benefits: list of benefits. Use - .
Pay: maybe a
stating range.
We must not include application instructions, etc.
Let's extract substantive content.
Intro paragraph(s):
"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."
That's about the company and role context. We'll put under About the role.
Then "Your Role" paragraphs (first occurrence):
"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."
Second occurrence (duplicate but slightly different):
"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."
We need to combine these into a cohesive list of responsibilities. Remove duplication. Let's parse 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.
- Additionally from first paragraph: "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." This is somewhat covered by other points but we can include as a responsibility: Own point of view, offering, delivery standard for agentic AI supply chain transformation; define human judgment in loop vs human-on-the-loop oversight; govern shift safely at enterprise scale.
We can combine.
Now Qualifications & Experience:
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).
We'll list these as
- .
Now "What You’ll Love About Working Here?" section:
- 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
This could be considered Benefits or maybe "Opportunities". Since we already have Benefits section for compensation/benefits, we could treat this as part of Benefits? But the spec says Benefits section only if posting actually states them. The posting has a separate Benefits section later describing PTO, medical, etc. So we should keep that as Benefits. The "What You’ll Love About Working Here
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID/requisition numbers as headings. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove boilerplate: 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 a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to decide which sections to include based on content. We have: - Intro: "At Capgemini Invent, we believe difference drives change..." This is about the company and role context. Could be "About the role" or maybe "About the role" includes description of role and context. - Then "Your Role" repeated: includes bullet-like paragraphs describing responsibilities. We can treat as Responsibilities section. - Then "Qualifications & Experience" with Must-Have Qualifications and Nice-to-Have Qualifications. Could be Requirements or Qualifications sections. The spec says we have headings: Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content accordingly. We have qualifications (must-have, nice-to-have). Could put under "Qualifications". Also "Requirements" maybe similar. But we should avoid duplicate sections. Choose one: maybe "Qualifications" for must-have and nice-to-have. "Requirements" could be omitted if no separate list. But we have "Must-Have Qualifications" and "Nice-to-Have Qualifications". That's qualifications. We also have "What You’ll Love About Working Here?" which is more about benefits/opportunities. Could be "Benefits" or maybe "Skills"? Actually it's about opportunities: building network, proposals, etc. That's more like "Responsibilities"? Not exactly. Could be "Benefits" but it's not compensation/benefits; it's more about role aspects. The spec says we should include Benefits only if posting actually states them. There is a Benefits section later: "Benefits Capgemini offers a comprehensive, non-negotiable benefits package..." So we definitely have Benefits. Pay: there is base compensation range: $180,000 to $240,000. So we need a Pay section. Schedule: not mentioned. So we should not include Schedule. Skills: maybe we could include technical skills from qualifications? But we already have Qualifications. Could we also have Skills? The spec says we can include Skills if there is real specific content. The posting mentions "agentic AI concepts and architecture - agent orchestration, multi-agent systems, RAG, relevant protocols (MCP/A2A)" etc. That's more qualifications. Could treat as Skills but we already have Qualifications. To avoid thin sections, we might combine qualifications and skills into one Qualifications section. But spec says we have separate headings possible; we should prefer few substantive sections over many thin ones. So we can have: About the role, Responsibilities, Qualifications, Benefits, Pay. That's five sections. We need to ensure we don't include filler like "commensurate with experience". Not present. We need to remove duplicated lines: The "Your Role" appears twice; we should combine. We need to remove boilerplate: EEO, disclaimer, etc. We need to preserve all substantive information: include details about responsibilities, qualifications, benefits, pay. We need to format using
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
Thus for each section, we need to decide if content is list or prose.
About the role: likely prose describing role context. Could be a
.
Responsibilities: list of duties. Use
- .
Qualifications: list of must-have and nice-to-have. Could be two sublists? Could be
- for each qualification. Might separate must-have and nice-to-have as separate
with headings? But we cannot add extra headings besides . Could we include a
introducing then list? Probably we can have a
then
. That's fine.
Benefits: list of benefits. Use - .
Pay: maybe a
stating range.
We must not include application instructions, etc.
Let's extract substantive content.
Intro paragraph(s):
"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."
That's about the company and role context. We'll put under About the role.
Then "Your Role" paragraphs (first occurrence):
"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."
Second occurrence (duplicate but slightly different):
"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."
We need to combine these into a cohesive list of responsibilities. Remove duplication. Let's parse 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.
- Additionally from first paragraph: "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." This is somewhat covered by other points but we can include as a responsibility: Own point of view, offering, delivery standard for agentic AI supply chain transformation; define human judgment in loop vs human-on-the-loop oversight; govern shift safely at enterprise scale.
We can combine.
Now Qualifications & Experience:
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).
We'll list these as
- .
Now "What You’ll Love About Working Here?" section:
- 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
This could be considered Benefits or maybe "Opportunities". Since we already have Benefits section for compensation/benefits, we could treat this as part of Benefits? But the spec says Benefits section only if posting actually states them. The posting has a separate Benefits section later describing PTO, medical, etc. So we should keep that as Benefits. The "What You’ll Love About Working Here
for prose. Thus for each section, we need to decide if content is list or prose. About the role: likely prose describing role context. Could be a
. Responsibilities: list of duties. Use
- .
Qualifications: list of must-have and nice-to-have. Could be two sublists? Could be
- for each qualification. Might separate must-have and nice-to-have as separate
- with headings? But we cannot add extra headings besides
- .
Pay: maybe a
stating range. We must not include application instructions, etc. Let's extract substantive content. Intro paragraph(s): "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." That's about the company and role context. We'll put under About the role. Then "Your Role" paragraphs (first occurrence): "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." Second occurrence (duplicate but slightly different): "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." We need to combine these into a cohesive list of responsibilities. Remove duplication. Let's parse 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. - Additionally from first paragraph: "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." This is somewhat covered by other points but we can include as a responsibility: Own point of view, offering, delivery standard for agentic AI supply chain transformation; define human judgment in loop vs human-on-the-loop oversight; govern shift safely at enterprise scale. We can combine. Now Qualifications & Experience: 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). We'll list these as
- . Now "What You’ll Love About Working Here?" section: - 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 This could be considered Benefits or maybe "Opportunities". Since we already have Benefits section for compensation/benefits, we could treat this as part of Benefits? But the spec says Benefits section only if posting actually states them. The posting has a separate Benefits section later describing PTO, medical, etc. So we should keep that as Benefits. The "What You’ll Love About Working Here
. Could we include a
introducing then list? Probably we can have a
then
- . That's fine.
Benefits: list of benefits. Use
- .
Pay: maybe a
- for each qualification. Might separate must-have and nice-to-have as separate