Capgemini Invent: Organizational Purpose & Strategy Managing Consultant
About the role
with. Then "Your Role" bullet list: many sentences describing responsibilities. We can extract responsibilities as list items. Responsibilities list includes: - Lead change strategy and execution for transformation workstreams - Run change impact assessments and translate into adoption plans, optimized with AI - Design/facilitate workshops for leaders and impacted teams - Create executive-ready communications, narratives, and enablement approaches - Establish change adoption KPIs; track progress and track progress and drive corrective actions - Strong collaboration across business and technology teams - Coach junior team members and maintain quality standards - Shape organizational change management deliverables (e.g., stakeholder management maps, change impact assessment, roles and RACI, governance), including the evolving human-AI change adoption models - Build narratives and communications tied to organizational change management - Shape client executive-ready content and structured recommendations for the transformation roadmap Also earlier: "Heorshe is responsible for the completion of a small or medium sized project can lead a team. Heorshe develops a reputation for its specific domain expertise internally and stats to develop market visibility. Heorshe is involved in training delivery to share knowledge in the organization." Could be responsibilities too. We'll include those as list items. Next: "Your Skills + Experience" section: list of skills/experience. We can put under
Skills
(or Skills + Experience). Use- .
Items:
- Strong AI literacy, including core AI and generative AI concepts, and understand how these capabilities apply to enterprise transformation.
- Able to identify and support AI‑enabled opportunities that improve business outcomes and delivery effectiveness, and have experience working in AI‑augmented ways of working to enhance research, analysis, and solution development.
- Collaborate effectively across strategy, technology, data, and design to enable AI‑driven solutions, with a solid understanding of responsible AI principles such as ethics, privacy, security, and governance.
- Demonstrate curiosity and a continuous learning mindset around emerging AI capabilities and their practical application in client environments.
- Required Experience: 8-10+ years OCM/transformation experience with client-facing leadership
- Strong facilitation and stakeholder management skills
- Experience with shaping communications, training, and readiness activities at scale
- Ability to tie change activities to outcomes and adoption metrics
- Clear, pragmatic communicator with strong delivery discipline
- Working understanding of how AI‑enabled tools and solutions are applied in organizational change contexts, including their role in shaping change approaches, supporting execution, and enabling adoption across the human change journey.
- Fluency with OCM frameworks and adoption measurement and agentic workflows
We could separate Requirements and Qualifications but they overlap. The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to include.
We have content for About the role, Responsibilities, Skills (maybe also Requirements/Qualifications). The "Required Experience" etc could be Requirements. The skills list could be Skills. We could combine Requirements and Qualifications into one? But better to separate: Requirements (experience, years, etc) and Qualifications (maybe education? Not present). There's no explicit qualifications like degree. So we might omit Qualifications if no specific content. Similarly, Schedule not mentioned. Pay is present: base compensation range $127,500-$249,350. Also mention variable incentives etc. So we can include Pay section.
Benefits: there is a Benefits paragraph describing benefits. So include Benefits.
Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay.
We must not include empty sections.
Now format: Use
for each heading. Then content: For prose use
. For lists use
- .
We need to preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like EEO, disclaimers, etc. Remove duplicated lines.
We need to ensure we don't include navigation/cookie etc.
Let's craft.
About the role: combine the introductory paragraphs after "About The Job You’re Considering". Might also include the first paragraph about Capgemini? That is generic but could be considered about the company not role. Might be okay to include as part of About the role? The instruction: "About the role" heading for section headings (e.g. About the role, Responsibilities...). So we can put the description of the role there.
We'll include:
The Strategy and Transformation consultant supports Capgemini clients to innovate and develop new strategies, services and products. He/she designs and implements new business and operating models and brings to life the organizations of the future. He/she develops customer insights, organizational knowledge and market perspectives. As AI reshapes how organizations operate, compete, and create value, we are evolving our consulting model to be AI-enabled by design — augmenting human judgment with analytics, automation, and generative AI. Our Enterprise Transformation team is looking for consultants who are not only strong problem solvers, but who are excited to work differently in an AI-first world: curious, adaptable, and ready to help clients reimagine how work gets done. The Workforce & Organization (W&O) is Capgemini Invent’s people‑led transformation capability, focused on helping organizations adapt their workforce, operating models, and ways of working to deliver sustainable business outcomes. W&O partners with clients to design and implement future‑ready organizations—aligning strategy, talent, culture, and technology to enable large‑scale transformation and improved workforce performance.
That seems good. Responsibilities: list items as above. We'll include also the earlier sentences about leading small/medium project, developing reputation, training delivery. Let's compile list: - Lead change strategy and execution for transformation workstreams - Run change impact assessments and translate into adoption plans, optimized with AI - Design and facilitate workshops for leaders and impacted teams - Create executive-ready communications, narratives, and enablement approaches - Establish change adoption KPIs; track progress and drive corrective actions - Collaborate strongly across business and technology teams - Coach junior team members and maintain quality standards - Shape organizational change management deliverables (e.g., stakeholder management maps, change impact assessment, roles and RACI, governance), including the evolving human‑AI change adoption models - Build narratives and communications tied to organizational change management - Shape client executive‑ready content and structured recommendations for the transformation roadmap - Responsible for the completion of small or medium‑sized projects and can lead a team - Develops a reputation for specific domain expertise internally and begins to develop market visibility - Involved in training delivery to share knowledge in the organization Make sure each is a - .
Now Requirements: we have "Required Experience 8-10+ years OCM/transformation experience with client-facing leadership", "Strong facilitation and stakeholder management skills", "Experience with shaping communications, training, and readiness activities at scale", "Ability to tie change activities to outcomes and adoption metrics", "Clear, pragmatic communicator with strong delivery discipline", "Working understanding of how AI‑enabled tools and solutions are applied in organizational change contexts, including their role in shaping change approaches, supporting execution, and enabling adoption across the human change journey.", "Fluency with OCM frameworks and adoption measurement and agentic workflows". Also maybe "Strong AI literacy" etc but that's skills.
We'll put those as list under Requirements.
Skills: list from "Your Skills + Experience" before Required Experience.
Items:
- Strong AI literacy, including core AI and generative AI concepts, and understand how these capabilities apply to enterprise transformation.
- Able to identify and support AI‑enabled opportunities that improve business outcomes and delivery effectiveness, and have experience working in AI‑augmented ways of working to enhance research, analysis, and solution development.
- Collaborate effectively across strategy, technology, data, and design to enable AI‑driven solutions, with a solid understanding of responsible AI principles such as ethics, privacy, security, and governance.
- Demonstrate curiosity and a continuous learning mindset around emerging AI capabilities and their practical application in client environments.
We could also include "Strong collaboration across business and technology teams" but that's already in responsibilities.
Now Benefits: paragraph about benefits. We'll extract the substantive benefits list:
- 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'll put as
- .
Pay: include base compensation range $127,500-$249,350. Also mention variable incentives etc. We'll include that as prose.
We must not include boilerplate like "The base compensation range for this role in the posted location is:" maybe we can keep that as part of the prose. It's substantive.
We should not include the disclaimer about compensation not typical etc. That's also substantive? It's about compensation details; we could include but it's somewhat boilerplate but still part of posting. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep that info as well. However, we must avoid filler like "commensurate with experience". The disclaimer is not filler; it's detail about compensation. So we can include.
Thus Pay section:
The base compensation range for this role in the posted location is: $127,500‑$249,350. 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
- .
Pay: include base compensation range $127,500-$249,350. Also mention variable incentives etc. We'll include that as prose.
We must not include boilerplate like "The base compensation range for this role in the posted location is:" maybe we can keep that as part of the prose. It's substantive.
We should not include the disclaimer about compensation not typical etc. That's also substantive? It's about compensation details; we could include but it's somewhat boilerplate but still part of posting. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep that info as well. However, we must avoid filler like "commensurate with experience". The disclaimer is not filler; it's detail about compensation. So we can include.
Thus Pay section:
- .
We need to preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like EEO, disclaimers, etc. Remove duplicated lines.
We need to ensure we don't include navigation/cookie etc.
Let's craft.
About the role: combine the introductory paragraphs after "About The Job You’re Considering". Might also include the first paragraph about Capgemini? That is generic but could be considered about the company not role. Might be okay to include as part of About the role? The instruction: "About the role" heading for section headings (e.g. About the role, Responsibilities...). So we can put the description of the role there.
We'll include: