Java Developer with Python & DB2

We need to output HTML fragment with sections: About the role? The posting includes a paragraph about choosing Capgemini (intro). Then Job Role, Location, Duration, Job Summary, Key Responsibilities, Required Skills & Qualifications, Preferred Qualifications, Key Competencies, Base compensation range, Benefits. Also there is some boilerplate about compensation disclaimer, EEO, etc. We need to remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Also we should not repeat job title as heading. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content. We have: - Intro paragraph: "Choosing Capgemini means choosing a company where you will be empowered..." This could be "About the role" or maybe "About the company". Use

About the role

with that paragraph. - Job Summary: "Capgemini is seeking a skilled and motivated Java Full Stack Developer..." That's also about role. Could combine with intro? But we can have separate sections: About the role (intro + job summary). Or we could have About the role (intro) and then Job Summary as part of same? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose which headings to include. We need to include sections only when posting has real, specific content. We have content for: - About the role: intro paragraph + job summary. - Responsibilities: Key Responsibilities list. - Requirements / Qualifications / Skills: There's Required Skills & Qualifications, Preferred Qualifications, Key Competencies. We need to map to headings: Requirements, Qualifications, Skills. Possibly combine Required Skills & Qualifications under Requirements, Preferred Qualifications under Qualifications, Key Competencies under Skills? Or we could have Requirements (required skills), Qualifications (preferred qualifications), Skills (key competencies). The instruction says prefer a few substantive sections over many thin ones. Could combine Required Skills & Qualifications and Preferred Qualifications into one "Requirements" section? But they are distinct. However we could have "Requirements" for required skills, "Preferred Qualifications" as a subsection? But we only allowed headings list; we could still include "Qualifications" for preferred qualifications. And "Skills" for key competencies. We also have Pay: base compensation range. So we need a Pay section with that range. Benefits: there is a Benefits section describing benefits. So include Benefits. Schedule: not mentioned (duration fulltime but not schedule details). The posting mentions Duration: Fulltime. That's not a schedule like shift times. We could maybe include Schedule if we have info about fulltime? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state Duration: Fulltime, which could be considered schedule? But schedule usually refers to work schedule (e.g., full-time, part-time, shift). The posting includes Duration: Fulltime. That could be considered schedule. However they said "Schedule" as a possible heading. We could include Schedule with "Fulltime". But we need to avoid filler like "not specified". It's specified: Fulltime. So we can include Schedule section with that. But we also have Location: Alpharetta, GA. Could be part of About the role or maybe a separate metadata. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. Location is minor metadata; we could fold into a short

under About the role or maybe a separate paragraph. Since we already have About the role section, we can include location there. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all responsibilities list items, required skills list, preferred qualifications list, key competencies list, benefits details, compensation range. We must remove boilerplate: the long disclaimer about compensation, EEO, etc. Also the "Important Notice: Compensation (including bonuses...)" etc. Also the "Disclaimers" about EEO, etc. Also the paragraph about Capgemini being a global business etc at the end. Also the "Click the following link..." etc. Also the "Important Notice: Compensation..." etc. Also the "This is a general description..." etc. Also the "Physical, mental, sensory..." etc. Also the "Capgemini is committed to providing reasonable accommodation..." etc. Also the "Please be aware that Capgemini may capture your image..." etc. Also the "Click the following link..." etc. Also the "Capgemini is a global business..." etc. All that should be removed. We need to keep the benefits description: "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 LeaveMedical, 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 insuranceEmployee assistance programsOther benefits as provided by local policy and eligibility". That's substantive. We need to keep compensation range: "The base compensation range for this role in the posted location is: $61087 - $104364". Also the following sentences about compensation range information etc. That's boilerplate? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The compensation range explanation might be considered legal boilerplate? It's about pay transparency laws. Might be considered legal. However the base compensation range itself is substantive; the explanation about it being in accordance with laws may be considered boilerplate. The instruction says: "Prefer a few substantive sections over many thin ones." It didn't explicitly say to remove compensation explanation, but it's likely boilerplate. However we need to preserve ALL substantive information; the explanation is not substantive about the job; it's legal. I'd remove the explanation paragraphs after the range, keeping only the range statement. Similarly, the "In addition to base salary, this role may be eligible for additional compensation such as variable incentives, bonuses, or commissions..." is also boilerplate? Might be considered part of compensation details. Could keep? It's substantive about potential additional compensation. Might be worth keeping. But it's also somewhat generic. The instruction: do not invent or summarize away detail. It's a detail about additional compensation. I'd keep it. But we need to check for duplication: there is also "Important Notice: Compensation (including bonuses, commissions, or other forms of incentive pay) is not considered earned..." That's legal boilerplate; remove. Thus for Pay section we can include: - Base compensation range: $61087 - $104364 - Additional compensation: variable incentives, bonuses, or commissions depending on position and applicable laws. We could combine into a

. Now schedule: we have Duration: Fulltime. Could also include location. We'll put location and duration in About the role paragraph maybe. Let's craft 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. Job Role: Java Developer with Python & DB2. Location: Alpharetta, GA. Duration: Fulltime.

Capgemini is seeking a skilled and motivated Java Full Stack Developer to design, develop, and maintain scalable enterprise applications that support critical business functions across the firm. The ideal candidate should have strong backend expertise in Java and modern frameworks, along with solid frontend development skills and experience building secure, high-performance applications in cloud-enabled environments.

Then Responsibilities:

Responsibilities

• Design, develop, test, and deploy full stack applications using Java
• Build robust RESTful APIs and microservices for high-volume, low-latency systems.
• Collaborate with product owners, business analysts, architects, and QA teams to deliver high-quality solutions.
• Develop responsive, reusable UI components and integrate them with backend services.
• Participate in architecture, code reviews, and technical design discussions.
• Optimize application performance, reliability, and scalability.
• Implement best practices for security, data protection, and compliance in financial systems.
• Create and maintain technical documentation for code, APIs, and deployment processes.
• Troubleshoot production issues and provide timely resolution in collaboration with support teams.
• Contribute to CI/CD pipelines and DevOps automation practices.

Then Requirements (required skills):

Requirements

• Strong hands-on experience in Java (8/11/17) and Spring Boot, Spring MVC, Spring Security.
• Strong in Python work experience
• Solid experience with REST APIs, Microservices Architecture, and messaging systems (Kafka/RabbitMQ).
• Proficiency in frontend technologies: Angular / React, JavaScript/TypeScript, HTML5, CSS3.
• Experience with relational databases such as Oracle, SQL Server, or PostgreSQL.
• Good understanding of ORM frameworks like Hibernate/JPA.
• Familiarity with build and dependency tools: Maven/Gradle.
• Experience with version control systems such as Git.
• Strong knowledge of software design principles, data structures, and multithreading/concurrency.
• Excellent analytical, problem-solving, and communication skills.

Then Qualifications (preferred qualifications):

Qualifications

• Experience in financial services, investment banking, or capital markets.
• Exposure to cloud platforms (AWS / Azure / GCP) and containerization (Docker, Kubernetes).
• Knowledge of caching and performance tools (Redis, Elastic, profiling tools).
• Familiarity with CI/CD tools such as Jenkins, GitHub Actions, or similar.
• Experience with automated testing frameworks (JUnit, Mockito, Cypress/Selenium).
• Understanding of secure coding and regulatory/compliance requirements in banking environments.

Then Skills (key competencies):

Skills

• Ownership mindset and attention to detail
• Ability to work in agile, fast-paced teams
• Strong collaboration across global teams
• Commitment to engineering excellence and continuous improvement

Then Pay:

Pay

The base compensation range for this role in the posted location is: $61087 - $104364. 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.

Then Benefits:

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, S