AI Powered SDLC Architect

We need to output HTML fragment with sections: h3 for headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. We need to parse the job posting. Given text includes: - Location: hybrid role based at Seattle Area (Everett/Bellevue, WA) – location info, but we don't have a specific heading for location; we could fold into a short p. - About The Job You’re Considering: description. - Your Role: bullet list of responsibilities. - Your Skills And Experience: list of requirements/qualifications. - The base compensation range: $88,544 - $207,401/Year – that's Pay. - Benefits: description of benefits package. - Schedule: not explicitly mentioned; hybrid role implies schedule? Not explicit. We should not create Schedule unless stated. So omit. - Qualifications: maybe combine with Skills. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. 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. We need to 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. Thus we need to strip out the long EEO, disclaimer, etc. Also remove the "Important Notice: Compensation..."? That's compensation detail but maybe part of Pay section? It includes details about compensation not being earned etc. Might be considered boilerplate? It's part of compensation description; but we can keep the base compensation range and maybe note that additional compensation may be variable incentives etc. The "Important Notice" is legal boilerplate; we should remove it as per instruction to remove legal/EEO boilerplate. However the compensation range itself is substantive; we can keep that in a Pay section. The extra legal text about compensation not being earned etc is likely boilerplate; we should remove. Similarly the benefits description includes some legal? It's substantive benefits; we can keep. We need to avoid duplication. Let's extract substantive content: - Intro paragraph about Capgemini Engineering: "At Capgemini Engineering, the world leader in engineering services, we bring together a global team of engineers, scientists, and architects to help the world’s most innovative companies unleash their potential. From autonomous cars to life-saving robots, our digital and software technology experts think outside the box as they provide unique R&D and engineering services across all industries. Join us for a career full of opportunities. Where you can make a difference. Where no two days are the same." That's about the company; could be placed under "About the role" or maybe a general intro. The instruction: use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have an "About the role" section with that intro plus location maybe. - Location: "Location This is a hybrid role based at Seattle Area (Everett/Bellevue, WA)". Could be a short p. - About The Job You’re Considering: "Capgemini is hiring an AI-Powered SDLC Architect to design and run the AI-Powered software factory behind a large, complex Siemens Teamcenter PLM modernization for a major Aerospace & Defense OEM. You make AI-accelerated delivery the norm - AI-assisted coding, testing and documentation inside a modern DevSecOps pipeline and you architect that pipeline to be agent-ready, all governed responsibly and operated across a blended onshore–offshore team." That's also about the role. - Your Role: bullet list: - Architect the AI-Powered software factory. - Design a modern DevSecOps / CI-CD pipeline and an agent-ready delivery toolchain. - Define productivity and quality metrics. - Integrate the factory with Teamcenter customization and extension delivery. - Establish responsible-AI governance. - Enable onshore-offshore squads on shared standards and tooling. - Mentor technical leads. - Advise client and program leadership on AI-Powered SDLC strategy. That's responsibilities. - Your Skills And Experience: list: - 10+ years in software engineering or delivery architecture. - Proven use of AI-accelerated SDLC. - Experience designing agent-ready pipelines and responsible-AI governance. - Experience enabling onshore-offshore squads. - Working knowledge of PLM / Teamcenter customization delivery. - Advisory and pre-sales experience is a plus. - Experience with agentic development frameworks and MCP-based tooling is preferred. - Cloud (AWS / Azure) and infrastructure-as-code experience is preferred. That's qualifications/skills. - Compensation: "The base compensation range for this role in the posted location is: $88,544 - $207,401/Year". Also mention that Capgemini provides compensation range information... but we can keep just the range. - 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" We can keep that as Benefits. - Schedule: Not explicitly stated; hybrid role implies some flexibility but not explicit schedule. So we should not create Schedule section. - Also there is a line: "Location This is a hybrid role based at Seattle Area (Everett/Bellevue, WA)" – we can include location in About the role or as a short p. We need to avoid repeating job title as heading; we won't. We need to output only HTML fragment, no /, no markdown fences. Thus produce something like:

  About the role

  At Capgemini Engineering, the world leader in engineering services, we bring together a global team of engineers, scientists, and architects to help the world’s most innovative companies unleash their potential. From autonomous cars to life-saving robots, our digital and software technology experts think outside the box as they provide unique R&D and engineering services across all industries. Join us for a career full of opportunities. Where you can make a difference. Where no two days are the same.

  Location: This is a hybrid role based at Seattle Area (Everett/Bellevue, WA).

  Responsibilities

  • Architect the AI-Powered software factory.
  • Design a modern DevSecOps / CI-CD pipeline and an agent-ready delivery toolchain.
  • Define productivity and quality metrics.
  • Integrate the factory with Teamcenter customization and extension delivery.
  • Establish responsible-AI governance.
  • Enable onshore-offshore squads on shared standards and tooling.
  • Mentor technical leads.
  • Advise client and program leadership on AI-Powered SDLC strategy.

  Requirements

  • 10+ years in software engineering or delivery architecture.
  • Proven use of AI-accelerated SDLC.
  • Experience designing agent-ready pipelines and responsible-AI governance.
  • Experience enabling onshore-offshore squads.
  • Working knowledge of PLM / Teamcenter customization delivery.
  • Advisory and pre-sales experience is a plus.
  • Experience with agentic development frameworks and MCP-based tooling is preferred.
  • Cloud (AWS / Azure) and infrastructure-as-code experience is preferred.

  Pay

  The base compensation range for this role in the posted location is: $88,544 - $207,401 per year.

  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 need to ensure we didn't include any boilerplate like EEO etc. We removed them. Check if any content duplicated: we have location line maybe duplicated? It's fine. We need to ensure we didn't create sections with filler like "commensurate with experience". Not present. We used

  for sections: About the role, Responsibilities, Requirements, Pay, Benefits. Could also have Skills but we combined into Requirements. The instruction allowed Skills as a heading; we can use Requirements or Skills. We used Requirements. That's okay. We didn't include Schedule. We didn't include Qualifications separate; we used Requirements. We preserved all substantive info: intro, location, role description, responsibilities, skills/experience, pay, benefits. We omitted the "Your Role" heading; we turned into Responsibilities. We omitted "Your Skills And Experience" heading; turned into Requirements. We omitted the long legal disclaimer about compensation, EEO, etc. We omitted the "Important Notice" about compensation not being earned etc. We omitted the "Disclaimers" etc. We omitted the final paragraph about Capgemini being global etc? Actually that is also boilerplate? It's more company description but we already have intro; but the final paragraph after the legal stuff is also company overview. It might be considered substantive? It repeats some of the intro but also adds details: "It is a responsible and diverse group of 340,000 team members in more than 50 countries...". That's additional info about company size. Should we preserve? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that as well. It's not boilerplate; it's about the company. Could be included in About the role section. Thus we need to add that paragraph after the intro. Let's capture: "Capgemini is a global business and technology transformation partner, helping organizations to accelerate their dual transition to a digital and sustainable world, while creating tangible impact for enterprises and society. It is a responsible and diverse group of 340,000 team members in more than 50 countries. With its strong over 55-year heritage, Capgemini is trusted by its clients to unlock the value of technology to address the entire breadth of their business needs. It delivers end-to-end services and solutions leveraging strengths from strategy and design to engineering, all fueled by its market leading capabilities in AI, generative AI, cloud and data, combined with its deep industry expertise and partner ecosystem." We can add that to About the role. Thus About the role will have two paragraphs: first intro, second company overview. We'll keep location p. Now check for any other substantive content: "Capgemini provides compensation range information in accordance with applicable national, state, provincial, and local pay transparency laws." That's legal but could be considered part of Pay section? It's about transparency law; maybe we