SAP Delivery and Solution Architect (GTM)- CPRS Industry

We need to output HTML fragment with sections: headings

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 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 a 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 have content: About The Job You're Considering (description). Then "Your Role" (list of responsibilities). Then "Your Skills And Experience" (list of qualifications). Then compensation range: "The base compensation range for this role in the posted location is: $123,750 - $340,750". Then "Benefits" paragraph describing benefits. Also there is some other text about Capgemini etc. We need to remove boilerplate: the initial paragraph about choosing Capgemini (intro) maybe considered boilerplate? It's not exactly legal but it's generic marketing. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The intro about choosing Capgemini might be considered marketing fluff but not explicitly prohibited. However we need to preserve ALL substantive information. The intro is somewhat generic but still part of posting. It may be considered substantive? It describes company culture. Could keep as a paragraph maybe under "About the role"? But we have a section "About The Job You're Considering". That is like a description. We could treat that as "About the role". Use

  About the role

  then paragraph(s). Then responsibilities: "Your Role" bullet list. Use

  Responsibilities

  then
  • ... each bullet. Then qualifications/skills: "Your Skills And Experience". Use

    Requirements

    or

    Skills

    ? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose appropriate. Probably "Requirements" for minimum qualifications, and "Skills" for skills/experience. But we have combined list. Could split: Requirements (education, years experience) and Skills (specific expertise). However we must not create thin sections. Might combine into one "Requirements" or "Skills". Let's see content: "Your Skills And Experience Minimum- Bachelors Degree15+ years of SAP professional experience including consulting, architecture, and transformation leadership experience.Deep expertise in (CPRS) Consumer Products, Retail, Wholesale Distribution, or Services industries.Demonstrated leadership of large SAP S/4HANA transformation programs.Strong experience with SAP BTP, SAP Business AI, Supply Chain, Commerce, Customer Experience, and Digital Transformation solutions.Successful track record leading pursuits and programs exceeding $25M–$50M+ TCV.Executive-level communication and stakeholder management capabilities.SAP certifications and enterprise architecture credentials preferred.Consulting experience within a large global systems integrator or professional services organization strongly preferred". That's a mix of requirements and skills. Could put under

    Requirements

    and list as
    . Or

    Skills

    . The instruction says prefer a few substantive sections over many thin ones. So maybe one section for "Requirements and Skills". But we have headings list includes both Requirements and Skills; we could use either. I'd choose "Requirements". Then Benefits: we have a paragraph describing benefits. Use

    Benefits

    then
    • items? The benefits paragraph is prose listing items separated by commas. Could convert to 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. That's a list. Use
      • each. Pay: we have compensation range. Use

        Pay

        then

        The base compensation range for this role in the posted location is: $123,750 - $340,750

        . Also note there is additional text about compensation range info, variable incentives etc. That's also substantive. Should we include that? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should include the explanation about compensation range, variable incentives, etc. That is under the compensation section. Could include as

        after the range. However we must avoid filler like "commensurate with experience". The text includes: "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." That's substantive. So include under Pay section. Schedule: no mention of schedule (e.g., full-time, part-time). Not present, so we should NOT create Schedule section. Now we need to remove boilerplate: The initial paragraph about choosing Capgemini (the first paragraph) maybe considered marketing but not prohibited. However we might consider it as part of "About the role"? Actually we already have "About The Job You're Considering". That paragraph is separate. Could combine them? The instruction: Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

        or drop it. The initial paragraph is not metadata; it's descriptive. Could keep as part of About the role. But we already have a heading "About the role". We could put that paragraph under that heading. However we also have "About The Job You're Considering" heading in the source; we could treat that as the About the role content. So we can ignore the first paragraph? It's somewhat generic but still substantive about company culture. Might be okay to keep. But to avoid duplication, we could merge. Let's extract substantive sections: - About the role: The paragraph starting "Choosing Capgemini means choosing a company where you will be empowered..." plus the paragraph "About The Job You're Considering The SAP CPRS Delivery & Solutioning Architect (GTM) is a senior transformation leader..." Actually the latter is more about the job. We'll combine. Better: Use

        About the role

        then

        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.

        then another

        The SAP CPRS Delivery & Solutioning Architect (GTM) is a senior transformation leader responsible for shaping, selling, architecting, and delivering large-scale SAP-enabled business transformation programs for Consumer Products, Retail, and Services (CPRS) clients. This role combines deep SAP expertise with industry-specific knowledge across consumer goods, retail, wholesale distribution, and customer-centric business models to design end-to-end solutions that drive measurable business outcomes. The architect serves as a trusted advisor to executive stakeholders and is accountable for developing solution strategies, leading complex pursuits, driving innovation, and ensuring successful delivery of enterprise transformation programs. The role plays a critical part in Capgemini's Go-to-Market (GTM) strategy by creating compelling client value propositions, building reusable assets and accelerators, and contributing to thought leadership across the CPRS industry sector. Build the offering and drive growth through pre-sales activities related to a Group priority. Manage CoEs and a global alignement across regions. Be visible internally and externally to produce Go To Market content and participate to global events. Keep in touch closely with client expectations by contributing to delivery engagements. This position requires a strong balance of business consulting, solution architecture, pre-sales leadership, and delivery governance, while leveraging SAP innovations including S/4HANA, SAP Business AI, SAP BTP, Industry Cloud solutions, and emerging digital capabilities.

        That seems to capture the About the job description. Then Responsibilities: from "Your Role" bullet list. We'll list each sentence as
      • . The bullet list includes multiple sentences separated by periods. We'll split at each period that starts a new bullet? The original list: "Serve as a trusted advisor and SAP CPRS industry expert, leading large-scale business transformation initiatives across Consumer Products, Retail, and Services clients. Lead solution strategy, architecture, and roadmap development for SAP S/4HANA and related digital transformation programs. Drive strategic pursuits, RFP responses, client workshops, and executive presentations, translating business objectives into compelling solution visions. Partner with sales, account, and delivery teams to develop differentiated go-to-market offerings and win strategies. Architect scalable, future-ready solutions leveraging SAP S/4HANA, SAP BTP, SAP Business AI, Commerce, Supply Chain, and Customer Experience capabilities. Guide clients through ERP modernization, supply chain transformation, digital commerce, customer experience, and AI-enabled business initiatives. Provide leadership throughout the program lifecycle, ensuring delivery excellence, business value realization, client satisfaction, and commercial success. Champion innovation and AI-enabled solutioning methodologies, creating reusable assets, accelerators, and industry-specific offerings. Build and maintain executive stakeholder relationships while influencing strategic business and technology decisions. Lead and mentor cross-functional teams in complex environments, supporting capability growth, thought leadership, and sales enablement activities." We'll make each line a
      • . Then Requirements/Skills: from "Your Skills And Experience". We'll list each bullet: "- Bachelors Degree" "15+ years of SAP professional experience including consulting, architecture, and transformation leadership experience." "Deep expertise in (CPRS) Consumer Products, Retail, Wholesale Distribution, or Services industries." "Demonstrated leadership of large SAP S/4HANA transformation programs." "Strong experience with SAP BTP, SAP Business AI, Supply Chain, Commerce, Customer Experience, and Digital Transformation solutions." "Successful track record leading pursuits and programs exceeding $25M–$50M+ TCV." "Executive-level communication and stakeholder management capabilities." "SAP certifications and enterprise architecture credentials preferred." "Consulting experience within a large global systems integrator or professional services organization strongly preferred" We'll make each a
      • . Note the first line "Minimum- Bachelors Degree" maybe combine as "Bachelors Degree". We'll keep as is. Then Benefits: list as described. Then Pay: include range and explanation. We must not include any boilerplate like EEO, disclaimer, etc.