Java Full Stack Developer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (or Skills), Benefits, Pay, Schedule if present. The posting includes location, about the role, responsibilities, required skills & experience, preferred qualifications, soft skills, experience level, nice to have, compensation range, benefits. No schedule info. So we should include sections: About the role, Responsibilities, Requirements (maybe combine required skills & experience and preferred qualifications?), Benefits, Pay. Also maybe "Qualifications" but we can combine. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Include a section only when posting has real, specific content. So we need to include About the role (the paragraph after "About The Role You Are Considering Seeking..."). Responsibilities (list). Requirements (maybe combine required skills & experience and preferred qualifications? Could separate as Requirements and Preferred Qualifications but they said prefer few substantive sections over many thin ones. Could combine into Requirements (including required and preferred). But we have separate headings: Requirements, Qualifications, Skills. Might be better to have Requirements (required skills) and Qualifications (preferred). However they said prefer few substantive sections over many thin ones. We could have Requirements (including required and preferred) and Skills (maybe not needed). But we have a "Skills" heading possible. Let's think: The posting has "Required Skills & Experience", "Preferred Qualifications", "Soft Skills", "Experience Level", "Nice to Have". Could combine into a single Requirements section with subpoints? But we must use

• for any list of duties/requirements/benefits. So we can make a list for responsibilities, and a list for requirements (maybe combine required and preferred). Could also separate into Required Skills and Preferred Qualifications as separate sections but that may be many thin sections. However they said prefer a few substantive sections over many thin ones. So better to combine into one Requirements section that includes both required and preferred (maybe label within list items). But we must preserve all substantive information; we cannot invent or summarize away detail. We can keep the details as list items, preserving the text. So we can have a single

  Requirements

  with a
  containing all the bullet points from Required Skills & Experience, Preferred Qualifications, Soft Skills, Experience Level, Nice to Have. That preserves all info. However we need to be careful not to lose nuance like "Preferred Qualifications" vs "Required". But we can keep the wording as is; it's still substantive. It's okay. Benefits: we have a Benefits paragraph describing benefits. We'll output as

  Benefits

  then

  with the benefits text. Pay: we have compensation range. We'll output

  Pay

  then

  with the compensation range text. Schedule: none, so omit. Location: location info is minor metadata; we can fold into a short

  maybe after About the role? 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 can include a short

  after About the role or before. Probably include a

  Location: Riverwoods, IL; Frisco, TX; Richmond, VA; and New Jersey, and requires onsite participation.

  after About the role. We must not repeat job title as heading. The page already shows it, so we don't add. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we need to strip out the EEO paragraphs, disclaimer about image capture, link, etc. Also remove the "Important Notice:" about compensation? That is part of compensation details; it's substantive? It's about compensation, but it's more legal disclaimer. Might be considered boilerplate? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Important Notice:" about compensation is legal but related to compensation; maybe keep? It's not exactly EEO. It's about compensation. Might be considered legal but it's directly about compensation. The instruction says remove legal boilerplate; but compensation notice is legal. However it's part of compensation details; but we already have compensation range. The notice is about compensation not being earned etc. Could be considered boilerplate. Safer to remove it? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. That includes legal. So we should remove the Important Notice paragraph. Also remove the "Disclaimers" section about EEO, PAIR, etc. Remove the paragraph about Capgemini being a global business etc at the end (that's boilerplate). Also remove the "Click the following link..." etc. Also remove the "Physical, mental, sensory..." paragraph about accommodations? That's EEO/legal; remove. Also remove the "All qualified applicants..." paragraph (EEO). Remove the "Capgemini is an Equal Opportunity Employer..." etc. Remove the "Capgemini is a global business..." paragraph at end. We must preserve all substantive information: location, about the role, responsibilities, required skills & experience, preferred qualifications, soft skills, experience level, nice to have, benefits, pay. Also maybe the "Experience Level 8 to 12+ years of Java development experience." is substantive. Now craft HTML. Structure:

  About the role

  You Are Considering Seeking a Java Full Stack Developer with expertise in Java, Spring Boot, Microservices, REST APIs, AWS, and modern DevOps practices to develop and support scalable enterprise applications.

  But the original text: "About The Role You Are Considering Seeking a Java Full Stack Developer with expertise in Java, Spring Boot, Microservices, REST APIs, AWS, and modern DevOps practices to develop and support scalable enterprise applications." We'll keep that as a sentence. Then location paragraph:

  Location: Riverwoods, IL; Frisco, TX; Richmond, VA; and New Jersey, and requires onsite participation.

  Then responsibilities:

  Responsibilities

  • Develop and maintain Java-based enterprise applications and microservices.
  • Build REST APIs using Java 17/21, Spring Boot, and Spring Data JPA.
  • Develop and deploy cloud-native solutions on AWS.
  • Participate in Agile development, code reviews, and release activities.
  • Implement automated testing using JUnit, Cucumber/Karate, TDD, and BDD.
  • Build and maintain CI/CD pipelines.
  • Troubleshoot production issues and optimize application performance.
  Then requirements:

  Requirements

  • Strong expertise in Java 17/21, Spring Boot, Spring Framework, Spring Data JPA, and Microservices.
  • Experience with REST APIs, OAuth2, and cloud-native application development.
  • Hands-on experience with AWS services (EC2, ECS/EKS, Lambda, CloudWatch, S3, Spark).
  • Experience with Oracle, PostgreSQL, DynamoDB, Docker, and SQL optimization.
  • Proficiency in GitHub and source control systems.
  • Proven expertise in software development methodologies (Agile, Scrum)
  • Hands-on experience with CI/CD tools (Jenkins)
  • Experience with Artifact Repository tools (Artifactory)
  • Experience With Docker / Kubernetes (OCP Preferred)
  • Hands-on experience with Drools Rule Engine
  • Strong experience in TDD (JUnit) and BDD (Cucumber)
  • Experience with Relational (SQL) and NoSQL databases
  • Experience in writing unit and service-level tests
  • Knowledge of high availability and scalability design
  • Experience with API architecture and development
  • Understanding of messaging systems such as Kafka, RabbitMQ
  • AWS Architect Certification
  • Experience in performance tuning and monitoring tools
  • Strong analytical and problem-solving skills
  • Excellent communication and stakeholder management skills
  • Strong communication and collaboration abilities
  • Ability to multitask and work in fast-paced environments
  • Adaptability in working with business and technical teams
  • Experience Level 8 to 12+ years of Java development experience.
  • Nice to Have: Experience with front-end technologies (React/Angular)
  • Nice to Have: Exposure to large-scale distributed systems
  But we duplicated "Strong communication and collaboration abilities" similar to earlier "Excellent communication and stakeholder management skills". Keep both as they are distinct. Now 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, 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 preserve the original text exactly? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the benefits text as close as possible. The original benefits paragraph: "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 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" Note there are missing spaces after commas. We should preserve exactly? Probably we can keep as is but we can add spaces for readability? The instruction says preserve ALL substantive information; not necessarily exact formatting but we should not lose info. Adding spaces doesn't lose info. Safer to keep the text as given but we can fix obvious missing spaces? Might be considered altering. I'd keep it exactly as given, but it's hard to read. However the instruction didn't require preserving exact punctuation spacing. I think we can keep the substance; adding spaces is fine. Now pay:

  Pay

  The base compensation range for this role in the posted location is: 86129 to 127189 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