D365 CRM Project Manager

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Remove boilerplate. We need to parse the posting. Key parts: Intro paragraph: "Choosing Capgemini means choosing a company where you will be empowered to shape your career in the way you’d like, where you’ll be supported and inspired by a collaborative community of colleagues around the world, and where you’ll be able to reimagine what’s possible. Join us and help the world’s leading organizations unlock the value of technology and build a more sustainable, more inclusive world." That's about the role/company. Could be "About the role" or maybe "About Capgemini". Use heading "About the role". We'll put that paragraph in

. Then "Long Description" then "Key Responsibilities" list. Responsibilities bullet list: - Lead end-to-end Dynamics 365 CRM implementation and enhancement projects. - Manage project scope, timelines, budgets, risks, and resources. - Partner with Sales, Customer Service, Marketing, and IT teams to gather requirements and deliver solutions. - Oversee Dynamics 365 Sales, Customer Service, and Power Platform initiatives. - Manage data migrations, system integrations, testing, and deployments. - Drive user adoption, training, and change management activities. - Provide project status updates to stakeholders and executive leadership. We'll put under

Responsibilities

with

• each. Then "Required Qualifications" list: - 5+ years of project management experience. - 3+ years managing Microsoft Dynamics 365 CRM projects. - Strong knowledge of Dynamics 365 Customer Engagement (CE) modules. - Experience with Agile and/or Waterfall methodologies. - Excellent communication, leadership, and stakeholder management skills. We could put under

  Requirements

  or

  Qualifications

  . The instruction says use headings like Requirements, Qualifications, Skills. We have both Required Qualifications and Preferred Skills. So we can map Required Qualifications to

  Requirements

  (or Qualifications). Preferred Skills to

  Skills

  . We'll decide: Use Requirements for required qualifications, Skills for preferred skills. Preferred Skills list: - PMP, Scrum Master, or Microsoft Dynamics certifications. - Experience with Power Apps, Power Automate, Power BI, and Dataverse. - Knowledge of Azure integrations and CRM data migrations. - Experience leading cross-functional and global teams. We'll put under

  Skills

  . Then "Key Technologies" maybe could be part of Skills or separate? Not required heading; we could incorporate into Skills or maybe not needed. But we have to preserve all substantive information. Could add a

  under Skills or maybe a separate section "Technologies". However headings list does not include Technologies; we could add as part of Skills or maybe as a

  within Skills. Probably better to include as a

  after Skills heading: "Key Technologies: Microsoft Dynamics 365 Sales & Customer Service; Power Platform (Power Apps, Power Automate, Power BI); Dataverse; Azure DevOps; Microsoft Project / Jira". But we must not invent headings not allowed? The instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples but we can use others? It says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It seems they expect only those headings. It says "include a section ONLY when the posting has real, specific content for it". So we should stick to those headings. So we need to fit Key Technologies somewhere, maybe within Skills or Responsibilities. Could add a

  under Skills describing key technologies. Then "Success Measures" list: On-time, on-budget project delivery. Increased CRM user adoption and satisfaction. Improved business processes through automation. Successful integrations and high-quality CRM solutions. We could put under maybe a heading? Not in list. Could incorporate into Responsibilities or maybe a separate section like "Performance Expectations". But not allowed. Could add as a

  under Responsibilities or maybe under Skills. Probably best to add as a

  under Responsibilities after the list, describing success measures. Then compensation: "The base compensation range for this role in the posted location is 100000 - 128989". Then a paragraph about compensation range info. We need to include Pay section only if posting states them. Yes, they state base compensation range. So we create

  Pay

  with

  containing that info. We should preserve the substantive info: base compensation range 100000 - 128989, plus the explanation about range may change, etc. We should include all that? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include the whole compensation paragraph(s). However we must avoid boilerplate like "Capgemini provides compensation range information in accordance with applicable national, state, provincial, and local pay transparency laws." That is substantive? It's part of the posting; it's not boilerplate? It's legal disclosure. Might be considered boilerplate but it's part of the posting. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is legal/compensation disclosure; not sure if considered boilerplate. It's about compensation transparency; likely we should keep it as it's substantive about pay. However it's somewhat generic. But we can keep it. Then benefits: "Capgemini offers a comprehensive, non-negotiable benefits package to all regular, full-time employees. In the U.S. and Canada, available benefits are determined by local policy and eligibility and may include: ..." Then list of benefits. So we need Benefits section. We should not include Schedule section because no schedule info. We should not include About the role? We have intro paragraph. We should not include Qualifications heading separate from Requirements? We have Requirements for required qualifications; we could also have Qualifications for something else but we don't have extra. Could combine Required Qualifications under Requirements and maybe also have Qualifications for something else like "Education"? Not present. So we can omit Qualifications heading. We need to ensure we don't create empty headings. Thus final HTML:

  About the role

  Choosing Capgemini means choosing a company where you will be empowered to shape your career in the way you’d like, where you’ll be supported and inspired by a collaborative community of colleagues around the world, and where you’ll be able to reimagine what’s possible. Join us and help the world’s leading organizations unlock the value of technology and build a more sustainable, more inclusive world.

  Responsibilities

  • Lead end-to-end Dynamics 365 CRM implementation and enhancement projects.
  • Manage project scope, timelines, budgets, risks, and resources.
  • Partner with Sales, Customer Service, Marketing, and IT teams to gather requirements and deliver solutions.
  • Oversee Dynamics 365 Sales, Customer Service, and Power Platform initiatives.
  • Manage data migrations, system integrations, testing, and deployments.
  • Drive user adoption, training, and change management activities.
  • Provide project status updates to stakeholders and executive leadership.

  Success measures include on-time, on-budget project delivery; increased CRM user adoption and satisfaction; improved business processes through automation; successful integrations and high-quality CRM solutions.

  Requirements

  • 5+ years of project management experience.
  • 3+ years managing Microsoft Dynamics 365 CRM projects.
  • Strong knowledge of Dynamics 365 Customer Engagement (CE) modules.
  • Experience with Agile and/or Waterfall methodologies.
  • Excellent communication, leadership, and stakeholder management skills.

  Skills

  • PMP, Scrum Master, or Microsoft Dynamics certifications.
  • Experience with Power Apps, Power Automate, Power BI, and Dataverse.
  • Knowledge of Azure integrations and CRM data migrations.
  • Experience leading cross-functional and global teams.

  Key technologies: Microsoft Dynamics 365 Sales & Customer Service; Power Platform (Power Apps, Power Automate, Power BI); Dataverse; Azure DevOps; Microsoft Project / Jira.

  Benefits

  Capgemini offers a comprehensive, non-negotiable benefits package to all regular, full-time employees. In the U.S. and Canada, available benefits are determined by local policy and eligibility and may include:

  • 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

  Pay

  The base compensation range for this role in the posted location is 100000 - 128989. 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 also include the notice about compensation not earned etc? That's also part of compensation section. Might be considered boilerplate but it's about compensation. The instruction says remove legal/EEO boilerplate. This is legal compensation disclaimer; maybe we should keep as it's part of Pay section. However it's quite long. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should include it. However it's somewhat generic but it's about compensation. I'd include it after the previous paragraph. Add another

  under Pay: "Important Notice: Compensation (including bonuses, commissions, or other forms of incentive pay) is not considered earned, vested, or payable until it becomes due under the terms of applicable plans or agreements and is subject to Capgemini’s discretion, consistent with applicable laws. The Company reserves the right to amend or withdraw compensation programs at any time, within the limits of applicable legislation." We should not include the rest of the boilerplate about EEO etc. That's after compensation; we should remove. Thus final HTML includes sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay. We omitted Qualifications heading (we used Requirements). We omitted