DevOps/API Developer

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 as heading. Must not include Job ID etc. Must preserve all substantive info, no invention, no summarizing away detail. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. We need to parse the posting. Content: - Intro: "Capgemini Government Solutions (CGS) LLC is seeking a DevOps/API Developer to support mission‑critical government clients. DevOps/API Developer will be responsible to design, build, and maintaining the CI/CD pipelines, API integrations, and infrastructure that power our hybrid environment. You will bridge the gap between our development teams and IT operations, ensuring seamless integration between our on-premises data centers and our gov cloud footprint (AWS and Azure). Your goal is to automate everything, build robust application interfaces, minimize downtime, and accelerate the delivery of secure, high-quality software." That's prose about role. Could go under "About the role" heading. - "Key Responsibilities" then bullet list (though not bullet but sentences). We'll need to extract each responsibility as list items. List: 1. Design and manage end-to-end CI/CD pipelines that deploy software consistently across local servers and cloud environments. 2. Use DevOps tools to ensure local hardware and cloud environments are managed as code. 3. Design, build, document, and maintain secure, scalable RESTful APIs, microservices, and web services to enable seamless integration between on-premises applications, cloud-native services, and third-party systems. 4. Manage and monitor the networking, API request routing, and data synchronization between on-prem storage and cloud-native services. 5. Leverage site-reliability best practices to ensure continuous service delivery, API resilience, and high-availability across hybrid environments. 6. Embed security scanning, compliance checks, API authentication protocols (e.g., OAuth 2.0, SAML, API keys), and rate-limiting directly into the development lifecycle. 7. Demonstrate a strong commitment to automation, consistently identifying opportunities to replace manual workflows with scalable, programmatic solutions and automated API integrations. 8. Exhibit excellent communication skills with the ability to bridge the gap between engineering complexities and business objectives. 9. Maintain composure and provide clear leadership during high-pressure system outages, API failures, or production incidents. These are responsibilities. - "Required Qualifications" then bullet list: 1. Must have an active Secret clearance that requires U.S. citizenship. 2. Bachelor’s degree in computer science, Information Technology, Engineering, or a related technical field is required. 3. 3-5 years of progressive experience. 4. Active CompTIA Security+ CE certification (or higher DoD 8570/8140 IAT Level II compliant certification, such as CYSA+, GSEC, or CISSP). These are qualifications. - "Technical Experience" then bullet list: 1. Proven experience with CI/CD tools (e.g., Jenkins, GitLab CI, GitHub Actions, Azure DevOps). 2. Strong background in API engineering, including experience with API gateways, Open API/Swagger specifications, and web service protocols. 3. Proficiency in Infrastructure as Code (IaC) tooling (e.g., Terraform, Ansible, CloudFormation). 4. Hands-on scripting and programming capabilities (e.g., Python, Bash, Go, or Node.js). These could be under Skills or Requirements? The instruction: Use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content. "Requirements" could include required qualifications (clearance, degree, experience, cert). "Qualifications" maybe technical experience? But they are similar. However we must not create thin sections. We could combine Required Qualifications and Technical Experience into "Requirements" and "Skills". Let's think. We have: - About the role: intro paragraph. - Responsibilities: list. - Requirements: maybe the mandatory qualifications (clearance, degree, experience, cert). Could be "Required Qualifications". - Skills: technical experience (CI/CD tools, API engineering, IaC, scripting). Could be "Skills". - Benefits: The posting mentions "Full-time regular employees are eligible for paid time off, medical/dental/vision insurance, 401(k), and any other benefits to eligible employees." Also mentions variable compensation, bonus, commission. Also mentions salary range: $90k-$100K. Also mentions "Capgemini discloses salary range information...". So we have Pay and Benefits info. - Schedule: Not mentioned explicitly. Could be full-time regular employees. Might infer schedule is full-time. But we should not create Schedule section unless posting actually states it. It says "Full-time regular employees are eligible...". That implies full-time schedule. Could we consider that as schedule? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state full-time regular employees, which implies schedule. But is that enough? It states "Full-time regular employees are eligible for paid time off...". That is a statement about schedule (full-time). So we could include Schedule section with that detail. However we need to avoid filler like "not specified". It's specified as full-time. So we can include Schedule. - Pay: The posting includes base salary range $90k-$100K, plus variable compensation, bonus, commission. So we can include Pay section. - Benefits: includes paid time off, medical/dental/vision insurance, 401(k), any other benefits. So Benefits section. We must not include boilerplate like disclaimer about image capture, work authorization, etc. Those are legal/EEO etc. Remove them. Also remove "About Capgemini" paragraph? That's company description, not required but could be considered boilerplate? It's not navigation/legal/EEO, but it's about the company. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Capgemini" is not explicitly listed to remove, but it's generic company description. Might be considered boilerplate? Not sure. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The "About Capgemini" is substantive about the company, but not about the role. However the instruction about sections: we only need to output sections relevant to the job posting. The "About Capgemini" could be considered filler but not prohibited. However we might keep it under "About the role"? Actually "About the role" is for role description, not company. The company description could be omitted as not required for the role. The instruction says preserve ALL substantive information; but does that mean we must keep everything except boilerplate? The "About Capgemini" is not boilerplate per se, but it's not about the role. However it's still part of the posting. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." It does not say to remove company description. So we should keep it. But where to put? Could be part of "About the role" or a separate section like "About the company". But we only have allowed headings list; we could add it under "About the role" as extra prose. However "About the role" heading is for role description; we could still include company info there. It might be okay. Alternatively we could create a section "About Capgemini" but not in allowed headings; we should not create extra headings. So we incorporate into "About the role" prose. Now we need to ensure we don't repeat job title as heading. We'll not. We need to output only HTML fragment, no /, no markdown. We'll produce something like:

About the role

Capgemini Government Solutions (CGS) LLC is seeking a DevOps/API Developer to support mission‑critical government clients. DevOps/API Developer will be responsible to design, build, and maintaining the CI/CD pipelines, API integrations, and infrastructure that power our hybrid environment. You will bridge the gap between our development teams and IT operations, ensuring seamless integration between our on‑premises data centers and our gov cloud footprint (AWS and Azure). Your goal is to automate everything, build robust application interfaces, minimize downtime, and accelerate the delivery of secure, high-quality software. 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. The Group reported 2024 global revenues of €22.1 billion.

Responsibilities

• Design and manage end-to-end CI/CD pipelines that deploy software consistently across local servers and cloud environments.
• Use DevOps tools to ensure local hardware and cloud environments are managed as code.
• Design, build, document, and maintain secure, scalable RESTful APIs, microservices, and web services to enable seamless integration between on-premises applications, cloud-native services, and third-party systems.
• Manage and monitor the networking, API request routing, and data synchronization between on-prem storage and cloud-native services.
• Leverage site-reliability best practices to ensure continuous service delivery, API resilience, and high-availability across hybrid environments.
• Embed security scanning, compliance checks, API authentication protocols (e.g., OAuth 2.0, SAML, API keys), and rate-limiting directly into the development lifecycle.
• Demonstrate a strong commitment to automation, consistently identifying opportunities to replace manual workflows with scalable, programmatic solutions and automated API integrations.
• Exhibit excellent communication skills with the ability to bridge the gap between engineering complexities and business objectives.
• Maintain composure and provide clear leadership during high-pressure system outages, API failures, or production incidents.

Requirements

• Must have an active Secret clearance that requires U.S. citizenship.
• Bachelor’s degree in computer science, Information Technology, Engineering, or a related technical field is required.
• 3-5 years of progressive experience.
• Active CompTIA Security+ CE certification (or higher DoD 8570/8140 IAT Level II compliant certification, such as CYSA+, GSEC, or CISSP).

Skills

• Proven experience with CI/CD tools (e.g., Jenkins, GitLab CI, GitHub Actions, Azure DevOps).
• Strong background in API engineering, including experience with API gateways, Open API/Swagger specifications, and web service protocols.
• Proficiency in Infrastructure as Code (IaC) tooling (e.g., Terraform, Ansible, CloudFormation).
• Hands-on scripting and programming capabilities (e.g., Python, Bash, Go, or Node.js).

Pay

The base salary range for the tagged location is $90k‑$100K. This role may be eligible for other compensation including variable compensation, bonus, or commission.

Benefits

• Paid time off
• Medical, dental, and vision insurance
• 40