DevOps

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule as headings only if content exists. We must not repeat job title. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, etc. Must not include sections with placeholder/filler like "commensurate with experience". Must include Pay if posting states compensation range. It does: "The base compensation range for this role in the posted location is: 89,000 to 115,000." Also mentions variable incentives etc. So Pay section should include that. Benefits: they describe benefits package. So include Benefits. Schedule: location mentions hybrid but not schedule specifics; no explicit schedule like full-time, part-time. Might not include Schedule unless explicit. The posting says "Location Westlake, TX - HYBRID Merrimack, NH - HYBRID". That's location, not schedule. So we may omit Schedule. Also we need sections: About the role (intro paragraph), Responsibilities (list of duties), Requirements (maybe qualifications?), Qualifications, Skills, Benefits, Pay. We need to decide what content goes where. The posting includes a job description with many bullet-like sentences. We need to parse into sections. We must not invent or summarize away detail. Must preserve all substantive info. So we need to extract each piece of info and place appropriately. Let's parse the posting: Intro: "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 go under About the role. Location: "Location Westlake, TX - HYBRID Merrimack, NH - HYBRID". Could be a short p under About the role or separate? Not a heading. We'll include as a p maybe. Job Description: list of responsibilities/requirements: - Hands-on experience with one or more of the languages (Python, Java, Go, Javascript etc.) - Solid experience working with public cloud and cloud infrastructure build - Cloud platform experience with certifications preferred (AWS or Azure) - Experience provisioning compute resources or managing IAAM roles and subscriptions in the cloud - Experience building VPCs, private networks and network routes and rules in the public cloud. - Demonstrated ability to utilize modern monitoring tools (DataDog, Prometheus, Splunk, ...) - Experience managing systems using infrastructure as code tools (CloudFormation, Terraform, ARM etc..) - Experience building CI-CD pipelines for DevSecOps functions - Hands on Experience on Deployments tools like Udeploy, Starling, Mario... - Knowledge of WS Cloud DevOps services such as Jenkins, IAM, VPC, ECS, Lambda, RDS, CloudFormation - Knowledge of Docker containers and PaaS (such as Cloud Foundry, Kubernetes, OpenShift, Rancher) highly desired. - Hands-on Kubernetes skills and knowledge - Experience managing systems using infrastructure as code tools (IAM, ARM, Terraform, ...). (duplicate) - Expertise in Production support, including incident management, root cause analysis, real-time monitoring, and high availability and reliability of critical systems in a fast-paced environment. - Azure application deployment Process. - Create and maintain docker files, manifest files, and HELM Charts for different environments\orchestrators - Experience engineering/sizing, installing, configuring, and maintaining mission critical applications. - Azure Active Directory hands on experience. - Strong analytical, technical, and problem-solving skills to troubleshoot issues in the cloud. - Experienced in Instrumentation with systems skills on building and operating, monitoring, logging, alerting services of distributed systems at scale - Your ability to learn and experiment with new technologies and patterns. Then compensation paragraph. Benefits paragraph: "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" Then disclaimer about compensation not earned etc. That's legal boilerplate; we should remove. Then EEO etc: remove. Then description of Capgemini: maybe about the company; could go under About the role as extra. We need to avoid duplication. Also note duplicate lines: "Experience managing systems using infrastructure as code tools (IAM, ARM, Terraform, ...)" appears twice; we should keep only once. We need to decide sections: About the role (intro + location + company overview). Responsibilities: maybe the hands-on experience items? Requirements: maybe certifications, experience? Qualifications: maybe education? Not present. Skills: maybe technical skills list. Could combine. But we must not create thin sections. Perhaps we can have About the role, Responsibilities, Requirements, Skills, Benefits, Pay. Avoid Qualifications if no specific qualifications like degree. Let's extract: About the role: Intro paragraph + location + company overview paragraph (the later paragraph about Capgemini being global etc). That's substantive. Responsibilities: The duties like "Experience provisioning compute resources...", "Experience building VPCs...", "Experience managing systems using infrastructure as code tools...", "Experience building CI-CD pipelines...", "Hands on Experience on Deployments tools...", "Knowledge of WS Cloud DevOps services...", "Knowledge of Docker containers and PaaS...", "Hands-on Kubernetes skills and knowledge", "Expertise in Production support...", "Azure application deployment Process.", "Create and maintain docker files, manifest files, and HELM Charts...", "Experience engineering/sizing, installing, configuring, and maintaining mission critical applications.", "Azure Active Directory hands on experience.", "Strong analytical, technical, and problem-solving skills to troubleshoot issues in the cloud.", "Experienced in Instrumentation with systems skills on building and operating, monitoring, logging, alerting services of distributed systems at scale", "Your ability to learn and experiment with new technologies and patterns." Requirements: maybe the items that are prerequisites: "Hands-on experience with one or more of the languages (Python, Java, Go, Javascript etc.)", "Solid experience working with public cloud and cloud infrastructure build", "Cloud platform experience with certifications preferred (AWS or Azure)", "Experience provisioning compute resources or managing IAAM roles and subscriptions in the cloud", "Experience building VPCs, private networks and network routes and rules in the public cloud.", "Demonstrated ability to utilize modern monitoring tools (DataDog, Prometheus, Splunk, ...)", "Experience managing systems using infrastructure as code tools (CloudFormation, Terraform, ARM etc..)", "Experience building CI-CD pipelines for DevSecOps functions", "Hands on Experience on Deployments tools like Udeploy, Starling, Mario...", "Knowledge of WS Cloud DevOps services such as Jenkins, IAM, VPC, ECS, Lambda, RDS, CloudFormation", "Knowledge of Docker containers and PaaS (such as Cloud Foundry, Kubernetes, OpenShift, Rancher) highly desired.", "Hands-on Kubernetes skills and knowledge", "Experience managing systems using infrastructure as code tools (IAM, ARM, Terraform, ...)", "Expertise in Production support...", "Azure application deployment Process.", "Create and maintain docker files, manifest files, and HELM Charts...", "Experience engineering/sizing, installing, configuring, and maintaining mission critical applications.", "Azure Active Directory hands on experience.", "Strong analytical, technical, and problem-solving skills to troubleshoot issues in the cloud.", "Experienced in Instrumentation with systems skills on building and operating, monitoring, logging, alerting services of distributed systems at scale", "Your ability to learn and experiment with new technologies and patterns." Actually many overlap. Could treat Responsibilities as the duties (like building, managing, etc.) and Requirements as the experience/skills needed. But it's fuzzy. Given instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Responsibilities and Requirements into one section called Responsibilities (or Requirements). But we need to follow headings list: we can include only those with real content. Could do About the role, Responsibilities, Benefits, Pay. That's four sections. Responsibilities section can contain all the technical duties/requirements as a list. Benefits section as described. Pay section with compensation range. Let's craft. We must not include boilerplate like "Capgemini provides compensation range information...". That's part of Pay section? It's explanatory but still substantive about pay. We can include it. We must not include legal disclaimer about compensation not earned etc. That's boilerplate; remove. We must not include EEO etc. We must not include the final paragraph about Capgemini being global etc? That's substantive about company; could go under About the role. Let's draft 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.

Location: Westlake, TX - HYBRID; Merrimack, NH - HYBRID.

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.

Responsibilities

• Hands-on experience with one or more of the languages (Python, Java, Go, Javascript etc.)
• Solid experience working with public cloud and cloud infrastructure build
• Cloud platform experience with certifications preferred (AWS or Azure)
• Experience provisioning compute resources or managing IAAM roles and subscriptions in the cloud
• Experience building VPCs, private networks and network routes and rules in the public cloud.
• Demonstrated ability to utilize modern monitoring tools (DataDog, Prometheus, Splunk, ...)
• Experience managing systems using infrastructure as code tools (CloudFormation, Terraform, ARM etc..)
• Experience building CI-CD pipelines for DevSecOps functions
• Hands on Experience on Deployments tools like Udeploy, Starling, Mario...
• Knowledge of WS Cloud DevOps services such as Jenkins, IAM, VPC, ECS, Lambda, RDS, CloudFormation
• Knowledge of Docker containers and PaaS (such as Cloud Foundry, Kubernetes, OpenShift, Rancher) highly desired.
• Hands-on Kubernetes skills and knowledge
• Experience managing systems using infrastructure as code tools (IAM, ARM, Terraform, ...)
• Expertise in Production support, including incident management, root cause analysis, real-time monitoring, and high availability and reliability