Lead API Developer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must parse the job posting. Key info: - Position Description: "For this role on this particular client engagement, employer sponsorship of immigration‑related visa and/or green card status as part of the PERM process will not be available. Candidate must be located in Pittsburgh, PA, Cleveland, OH, Dallas, TX" - Then description: "Are you a seasoned Java developer with a passion for building robust scalable APIs? We are seeking a talented individual like you to join our team as a API developer and play a key role in shaping the future of the platform that we are building for the clients. As a senior API developer, you will be responsible for designing, developing, and maintaining high performance APIs that power to the system. You will work closely with cross functional teams to understand requirements come on architect solutions, and ensure scalability come on reliability, and security of the APIs. You will have the opportunity to mentor junior developers, lead technical discussions, and drive the adoption of best practices and standards." - Then "Your future duties and responsibilities Looking for a Lead API Developer who has . 10+ years of hands on experience in Java/J2EE development, troubleshooting, and deployment (Mandatory) Hands on experience with modern technologies such as Spring Boot and Microservices architecture Design, develop, maintain, and implement APIs, microservices, and backend components Lead and manage a team of API developers; provide technical guidance and mentorship Work with API developers across teams to build scalable features and solutions Drive API standards, best practices, and service improvements Develop and unit test Java based RESTful services integrating with external client systems Review design documents and provide feedback on architecture, approach, and estimates Create technical designs for new systems and enhancements to existing systems Translate detailed requirements into functional system designs Participate in and drive Release Planning activities Create and manage Change Requests (CRs) for deployments and production releases Attend and represent the team in Enterprise Release Management (ERM) calls Support and drive end to end release execution, including deployment and post release validation Troubleshoot, optimize, and support applications across environments Work with DevOps tools such as Jenkins, uDeploy, and Git Knowledge and hands on experience with API management platforms such as Apigee Research and recommend libraries, tools, and frameworks to accelerate development Collaborate closely with internal and external business, design, and technical stakeholders Ability to prioritize work, meet deadlines, and manage multiple initiatives effectively Establish and maintain strong working relationships with clients, team members, and cross functional partners Excellent interpersonal and communication skills with the ability to work across diverse teams and understand technical challenges" - Then "Required Qualifications To Be Successful In This Role At least 10+ years overall experience Java/J2EE development with REST API, Spring Boot, Angular, XML, JSON, Swagger 8+ years of RESTful or SOAP web services 5+ years Angular, CSS, JavaScript, HTML 5+ years of GitHub, Jenkins and CI/CD server Experience writing unit tests for JavaScript code. Experience using Agile methodologies for developing application Experienced with Release Management. Participate in and drive Release Planning activities Create and manage Change Requests (CRs) for deployments and production releases" - Then repeated description again. - Then "Other Information: CGI is required by law in some jurisdictions to include a reasonable estimate of the compensation range for this role. The determination of this range includes various factors not limited to skill set, level, experience, relevant training, and licensure and certifications. To support the ability to reward for merit based performance, CGI typically does not hire individuals at or near the top of the range for their role. Compensation decisions are dependent on the facts and circumstances of each case. A reasonable estimate of the current range for this role in the U.S. is $100,800.00 $223,200.00. CGI's benefits are offered to eligible professionals on their first day of employment to include: Competitive compensation Comprehensive insurance options Matching contributions through the 401(k) plan and the share purchase plan Paid time off for vacation, holidays, and sick time Paid parental leaveLearning opportunities and tuition assistance Wellness and Well being programs Together, as owners, let’s turn meaningful insights into action. Life at CGI is rooted in ownership, teamwork, respect and belonging. Here, you’ll reach your full potential because… You are invited to be an owner from day 1 as we work together to bring our Dream to life. That’s why we call ourselves CGI Partners rather than employees. We benefit from our collective success and actively shape our company’s strategy and direction. Your work creates value. You’ll develop innovative solutions and build relationships with teammates and clients while accessing global capabilities to scale your ideas, embrace new opportunities, and benefit from expansive industry and technology expertise. You’ll shape your career by joining a company built to grow and last. You’ll be supported by leaders who care about your health and well-being and provide you with opportunities to deepen your skills and broaden your horizons. Come join our team—one of the largest IT and business consulting services firms in the world." - Then EEO boilerplate etc. We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Thus we need to extract substantive content: location, immigration sponsorship note, role description, responsibilities, qualifications, skills, benefits, pay. We must 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 have content. - About the role: Could include the introductory paragraph describing role, location, sponsorship note. - Responsibilities: list of duties (design, develop, maintain APIs, lead team, mentor, etc.) - Requirements: maybe location and sponsorship? Or "Required Qualifications" could be Requirements. - Qualifications: maybe the "Required Qualifications" list (10+ years experience etc.) - Skills: maybe specific technologies: Java/J2EE, Spring Boot, Microservices, API management (Apigee), DevOps tools (Jenkins, uDeploy, Git), Angular, CSS, JavaScript, HTML, REST/SOAP, unit testing, Agile, Release Management. - Benefits: list from CGI's benefits: Competitive compensation, Comprehensive insurance options, Matching contributions through 401(k) plan and share purchase plan, Paid time off for vacation, holidays, sick time, Paid parental leave, Learning opportunities and tuition assistance, Wellness and Well being programs. - Pay: compensation range $100,800.00 $223,200.00 (note formatting: there is a space between numbers; we should preserve as is). Could present as "$100,800.00 - $223,200.00" but must preserve ALL substantive information; we can keep as given but maybe better to keep exactly as text: "$100,800.00 $223,200.00". However we should not invent punctuation. We'll keep as "$100,800.00 $223,200.00". Could also wrap in

. - Schedule: not mentioned; no schedule info. So we should NOT include Schedule section. We must not include sections with filler like "commensurate with experience". We have actual content. We need to avoid duplication: The posting repeats some paragraphs; we should deduplicate. We need to output only HTML fragment, no /, no markdown fences. Let's craft. Structure:

About the role

For this role on this particular client engagement, employer sponsorship of immigration‑related visa and/or green card status as part of the PERM process will not be available. Candidate must be located in Pittsburgh, PA, Cleveland, OH, or Dallas, TX. Are you a seasoned Java developer with a passion for building robust scalable APIs? We are seeking a talented individual like you to join our team as an API developer and play a key role in shaping the future of the platform that we are building for the clients. As a senior API developer, you will be responsible for designing, developing, and maintaining high performance APIs that power the system. You will work closely with cross‑functional teams to understand requirements, architect solutions, and ensure scalability, reliability, and security of the APIs. You will have the opportunity to mentor junior developers, lead technical discussions, and drive the adoption of best practices and standards.

Note: we corrected some grammar but must preserve ALL substantive information; we can slightly adjust wording? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Changing grammar might be considered summarizing? It's okay to fix minor typos? The original had some errors like "power to the system", "come on architect solutions", "scalability come on reliability". We should preserve the original meaning but we can correct obvious errors? Safer to keep as is? The instruction says do not invent or summarize away detail; fixing grammar is not inventing new info, but could be considered altering. Safer to keep the original text exactly, but we can remove duplicated lines. However the original had some nonsensical phrasing; but we must preserve it. I'd rather keep the original phrasing exactly as given, but we can remove duplication. Let's extract the exact sentences from the posting: First paragraph after location note: "Are you a seasoned Java developer with a passion for building robust scalable APIs? We are seeking a talented individual like you to join our team as a API developer and play a key role in shaping the future of the platform that we are building for the clients. As a senior API developer, you will be responsible for designing, developing, and maintaining high performance APIs that power to the system. You will work closely with cross functional teams to understand requirements come on architect solutions, and ensure scalability come on reliability, and security of the APIs. You will have the opportunity to mentor junior developers, lead technical discussions, and drive the adoption of best practices and standards." We'll keep that exactly. Now responsibilities: The block after "Your future duties and responsibilities Looking for a Lead API Developer who has . 10+ years of hands on experience in Java/J2EE development, troubleshooting, and deployment (Mandatory) Hands on experience with modern technologies such as Spring Boot and Microservices architecture Design, develop, maintain, and implement APIs, microservices, and backend components Lead and manage a team of API developers; provide technical guidance and mentorship Work with API developers across teams to build scalable features and solutions Drive API standards, best practices, and service improvements Develop and unit test Java based RESTful services integrating with external client systems Review design documents and provide feedback on architecture, approach, and estimates Create technical designs for new systems and enhancements to existing systems Translate detailed requirements into functional system designs Participate in and drive Release Planning activities Create and manage Change Requests (CRs) for deployments and production releases Attend and represent the team in Enterprise Release Management (ERM) calls Support and drive end to end release execution, including deployment and post release validation Troubleshoot, optimize, and support applications across environments Work with DevOps tools such as Jenkins, uDeploy, and Git Knowledge and hands on experience with API management platforms such as Apigee Research and recommend libraries, tools, and frameworks to accelerate development Collaborate closely with internal and external business, design, and technical stakeholders Ability to prioritize work, meet deadlines, and manage multiple initiatives effectively Establish and maintain strong working relationships with clients, team members, and cross functional partners Excellent interpersonal and communication skills with the ability to work across diverse teams and understand technical challenges" We need to turn into list items (

• ). Each sentence or clause separated by periods? We'll split by sentences. But we must preserve ALL substantive information; we can keep as a paragraph? The rule: Use
  • for any list of duties/requirements/benefits. So responsibilities should be a list. Thus we will create
    with each duty as
    • . We'll need to parse. Let's list duties