Sr Software AI Engineer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (maybe Qualifications), Skills? The posting includes "About The Role", "Responsibilities", "Required Qualifications", "Preferred Qualifications". Also "About The AES Group" maybe not needed? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Thus we need sections: About the role (maybe from "About The Role"), Responsibilities, Requirements (maybe combine Required and Preferred Qualifications? Could separate but they said prefer few substantive sections over many thin ones. Could have "Qualifications" section covering both required and preferred. Or separate "Required Qualifications" and "Preferred Qualifications" as subheadings? But they only allow headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use "Qualifications" for both required and preferred. Could also have "Skills" if needed. But we can put qualifications in a

  list. We need to preserve all substantive information. So we need to include details from About The AES Group? The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." The "About The AES Group" is not a required heading but could be part of "About the role"? Actually "About The AES Group" is company overview. Could be included in a short paragraph under "About the role"? But they said use headings for sections like About the role, Responsibilities, etc. The "About The AES Group" could be considered part of "About the role" or maybe we can include it as a paragraph before the headings? The instruction: Output ONLY the HTML fragment — no /, no markdown code fences. So we can start with a

  containing company overview, then

  About the role

  etc. Or we could incorporate company overview into About the role section. Probably better to have a short

  for company overview then headings. We must not include boilerplate like EEO etc. There's none. We need to preserve all substantive information: responsibilities list, required qualifications list, preferred qualifications list. Let's extract: About The AES Group: description. About The Role: description of role: Senior Software Engineer I (AI) is a senior individual contributor on a small, focused AI-Native team, building production software using AI-native development workflows under guidance of AI-Native Tech Lead. AI Engineers use AI tools (Claude, Copilot) as a first-class part of daily workflow to accelerate development, testing, feedback loops -- applied on top of strong backend/enterprise foundation in Java, Spring Boot, microservices, workflow orchestration platforms. This role is not focused on training AI models or building ML pipelines; it is about building software efficiently, safely, and at high quality using AI-assisted engineering practices. Responsibilities: bullet points under AI-Native Engineering, Collaboration & Delivery, Quality & Continuous Improvement. We need to convert each bullet into

  • . Could group under subheadings? But we only have

    for section headings; we could keep the subheadings as plain text within

    or . Probably better to keep them as

    AI-Native Engineering

    then

    • ... etc. But instruction: Use
      • for any list of duties/requirements/benefits, and

        for prose. So we can have prose paragraphs for headings and then lists. Thus structure:

        About The AES Group: ...

        About the role

        Senior Software Engineer I (AI) ...

        Responsibilities

        AI-Native Engineering

        • Build and enhance production-grade Java/Spring Boot backend services, APIs, and microservices using AI-assisted workflows (Claude, Copilot) for coding, testing, debugging, and documentation.
        • Review, validate, and refine AI-generated code for correctness, performance, security, and maintainability.
        • Integrate services with workflow orchestration platforms (e.g., Temporal.io, Camunda) to support automation, intelligent routing, and decision support.
        • Orchestrate AI tool usage across development activities and help refine AI-native engineering standards set by the Tech Lead.

        Collaboration & Delivery

        • Collaborate with the AI-Native Tech Lead, data teams, and adjacent teams to deliver features end-to-end, balancing speed, quality, and long-term maintainability.
        • Participate in design discussions and code reviews; communicate technical issues and tradeoffs clearly to engineering and product stakeholders.

        Quality & Continuous Improvement

        • Ensure adherence to Cotiviti technology standards, secure coding practices, and SDLC requirements; resolve production issues and improve system performance and reliability.
        • Contribute to CI/CD, DevSecOps, and cloud-native deployments (OpenShift/Kubernetes, AWS).
        • Continuously build AI-assisted development knowledge and help improve team engineering practices.
        • Complete all responsibilities on the annual Performance Plan and any special projects/duties as assigned.

        Qualifications

        Required Qualifications

        • BS or MS in Computer Science, Information Technology, Engineering, or equivalent experience.
        • 5+ years of professional backend/enterprise software engineering experience.
        • Strong proficiency in Java, Spring Boot, and microservices architecture, with solid REST API and integration-pattern experience.
        • Demonstrated experience building and shipping production applications, using AI-assisted tools (Claude, Copilot, or similar) as part of daily workflow.
        • Strong debugging, problem-solving, and code-review skills, with a detail-oriented, ownership-driven approach to quality.
        • Experience with relational databases/SQL (PostgreSQL/Oracle), data modeling, and performance tuning.
        • Experience with event-driven/distributed systems and CI/CD, DevOps, and container/cloud platforms (OpenShift, Kubernetes, AWS).
        • Exposure to workflow orchestration platforms (Temporal, Camunda, Flowable, JBPM, or Drools).
        • Strong communication and collaboration skills; ability to learn quickly in a fast-evolving technical environment; Agile experience (SAFe preferred).

        Preferred Qualifications

        • Experience building workflow-driven or decision-automation solutions, or with enterprise workflow platforms (Temporal.io or similar).
        • Exposure to AI-native development practices, prompt-assisted workflows, and governance practices for AI-assisted development.
        • Experience contributing to shared platforms/integration frameworks, or building internal developer tools and automation.
        • Experience with cloud platforms (AWS, Azure, OCI) and containerization (Docker, Kubernetes).
        • Background in Healthcare IT or regulated environments.
        We should not include Pay, Schedule, Benefits sections as none given. We need to ensure we didn't miss any substantive info: The location: "Blue Bell, PA (Remote)" - maybe include as a short paragraph after company overview? The instruction: fold minor metadata into a short

        or drop it. Location is minor metadata; we can include in a short

        after company overview. Also the role title: "Sr. Software AI Engineer" but we shouldn't repeat as heading. Already we have About the role section. We need to preserve all substantive information: The description about using AI tools, not focusing on training models, etc. Already included. Check for duplication: The "About The AES Group" paragraph we included as prose. Good. Now output only HTML fragment. Let's craft final HTML:

        The AES Group is a premier technology and engineering consulting company that has been bringing businesses and talent together for over 20 years to deliver innovative solutions that have the greatest positive impact on society. AES has helped over 40 business enterprises, including Fortune 500 companies, engage their customers, empower their employees, and transform their business operations with the power of cloud, data, AI, engineering, and other emerging technologies.

        Location: Blue Bell, PA (Remote)

        About the role

        The Senior Software Engineer I (AI) is a senior individual contributor on a small, focused AI-Native team, building production software using AI-native development workflows under the guidance of the AI-Native Tech Lead. AI Engineers use AI tools (Claude, Copilot) as a first-class part of their daily workflow to accelerate development, testing, and feedback loops -- applied on top of a strong backend/enterprise foundation in Java, Spring Boot, microservices, and workflow orchestration platforms. This role is not focused on training AI models or building ML pipelines; it is about building software efficiently, safely, and at high quality using AI-assisted engineering practices.

        Responsibilities

        AI-Native Engineering

        • Build and enhance production-grade Java/Spring Boot backend services, APIs, and microservices using AI-assisted workflows (Claude, Copilot) for coding, testing, debugging, and documentation.
        • Review, validate, and refine AI-generated code for correctness, performance, security, and maintainability.
        • Integrate services with workflow orchestration platforms (e.g., Temporal.io, Camunda) to support automation, intelligent routing, and decision support.
        • Orchestrate AI tool usage across development activities and help refine AI-native engineering standards set by the Tech Lead.

        Collaboration & Delivery

        • Collaborate with the AI-Native Tech Lead, data teams, and adjacent teams to deliver features end-to-end, balancing speed, quality, and long-term maintainability.
        • Participate in design discussions and code reviews; communicate technical issues and tradeoffs clearly to engineering and product stakeholders.

        Quality & Continuous Improvement

        • Ensure adherence to Cotiviti technology standards, secure coding practices, and SDLC requirements; resolve production issues and improve system performance and reliability.
        • Contribute to CI/CD, DevSecOps, and cloud-native deployments (OpenShift/Kubernetes, AWS).
        • Continuously build AI-assisted development knowledge and help improve team engineering practices.
        • Complete all responsibilities on the annual Performance Plan and any special projects/duties as assigned.

        Qualifications

        Required Qualifications

        • BS or MS in Computer Science, Information Technology, Engineering, or equivalent experience.
        • 5+ years of professional backend/enterprise