Senior AI Developer [AQ-19327]

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. Must preserve all substantive info. Remove boilerplate like EEO, etc. Also remove Aquent Talent description? That's about Aquent benefits, maybe considered benefits? It mentions benefits like subsidized health, vision, dental, paid sick leave, retirement plans with a match, free online training. That is benefits info. So we can include Benefits section with that. Pay and Schedule not mentioned, so omit. Skills maybe we can include under Requirements? But we need to follow headings list: we can include Skills if there is specific skill content. The posting includes many qualifications, must-have qualifications, nice-to-have qualifications. Could treat Must-Have Qualifications as Requirements, Nice-to-Have as Qualifications? Or separate. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content. We have an introductory paragraph about Aquent partnering etc. That could be About the role. Responsibilities: the bullet list starting with "What You’ll Do" etc. Requirements: Must-Have Qualifications. Qualifications: Nice-to-Have Qualifications. Skills: maybe we can extract specific skills like Java, Spring, cloud, containers, microservices, CI/CD, cloud platforms, databases, LLMs, Generative AI coding assistants, agentic workflows, spec-driven development, prompt engineering, broker-dealer capabilities, communication, leadership, collaborative mindset. Those are qualifications but could be placed under Skills. However we already have Requirements and Qualifications sections; maybe we can put technical skills under Skills. But we must not duplicate content. We need to preserve all substantive info; we can split. Better: Use Requirements for mandatory qualifications (education, years experience). Use Qualifications for nice-to-have. Use Skills for specific technical skills (Java, Spring, etc.) but those are also in requirements. Might be duplication. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we split, we need to ensure we don't lose any info. Could include all under Requirements and Qualifications, and omit Skills if no distinct content beyond those. But we need to follow rule: include a section ONLY when the posting has real, specific content for it. If we don't have distinct Skills content beyond what's already covered, we could omit Skills. However we have many specific skills listed; they could be considered Skills. But they are also part of Requirements. To avoid duplication, maybe we put them under Skills and keep Requirements more about education/experience thresholds. Let's parse: Must-Have Qualifications list includes: - Bachelor’s degree in CS, SE, or related technical field, or equivalent practical experience. - 7+ years of professional software engineering experience actively developing large-scale software using Java, Spring framework, cloud development, and Web Services supporting high-volume transactions in a highly available environment. - 2+ years of hands-on experience with AI/ML implementation and production deployment. - 6+ years of experience working with containers and microservices in the cloud. - 6+ years of experience in cloud deployment within a CI/CD model. - 2+ years of experience with major cloud platforms. - 2+ years’ experience working with various modern databases. - 2+ years prior experience in IT transformations and system modernization initiatives from legacy to distributed platforms. - Hands-on experience with Large Language Models. - Demonstrated exposure to, or hands-on experience with, Generative AI coding assistants used across day-to-day engineering workflows in the SDLC, applying engineering judgment and validation. - Working knowledge of agentic workflows, spec-driven development, and custom instructions and prompt engineering, with the ability to establish team-level practices for effective AI-assisted development. - Understanding of broker-dealer capabilities and operations. - Excellent communication skills and a proven ability to communicate and lead other engineers in a collaborative environment. - Collaborative mindset coupled with a bias for action to effectively engage with fellow developers, architects, and adjacent teams. Nice-to-Have Qualifications list includes: - Master’s degree in IT, CS, or related degree, or related practical experience. - Good knowledge of messaging technologies. - Experience in the Financial Services industry. - Experience in Test Driven Development, QA Automation, and a strong quality mindset and behaviors. - Proficient in developing diagrams, architectural and design documentations, functional and technical specifications, and automated test processes. - Willingness to learn all aspects of the tech stack and document findings. - Ability to research and document production and test environments along with architecture and design work. - Knowledge of Agile methodology and experience in an Agile working environment. - Experience with collaboration and project management tools. Thus we can map: About the role: introductory paragraphs. Responsibilities: the "What You’ll Do" bullet list. Requirements: maybe the Must-Have Qualifications (including education, years experience). Could also include the specific technical skills but they are part of must-have. Qualifications: Nice-to-Have Qualifications. Skills: maybe we could extract specific technical skills like Java, Spring, cloud, containers, microservices, CI/CD, cloud platforms, databases, LLMs, Generative AI coding assistants, agentic workflows, spec-driven development, prompt engineering, broker-dealer capabilities. But those are already in Must-Have. To avoid duplication, we could still include them under Skills but that would duplicate content. The instruction says preserve ALL substantive information; does not forbid duplication? It says do NOT invent or summarize away detail. Duplication is not inventing or summarizing away; it's repeating. Might be okay but better to avoid redundancy. However we need to follow the headings list; we can include Skills if we have content. We could put the specific technical skills under Skills, and keep Requirements more about education/experience thresholds (like degree, years). But the Must-Have list includes both thresholds and specific skills. We could split: Requirements: education and years experience (like Bachelor's degree, 7+ years experience, etc). Skills: the specific technologies and domains. Qualifications: nice-to-have. Let's extract: Education/experience thresholds: - Bachelor’s degree in Computer Science, Software Engineering, or a related technical field, or equivalent practical experience. - 7+ years of professional software engineering experience actively developing large-scale software using Java, Spring framework, cloud development, and Web Services supporting high-volume transactions in a highly available environment. (This includes specific tech but we could keep as experience.) - 2+ years of hands-on experience with AI/ML implementation and production deployment. - 6+ years of experience working with containers and microservices in the cloud. - 6+ years of experience in cloud deployment within a continuous integration and continuous delivery (CI/CD) model. - 2+ years of experience with major cloud platforms. - 2+ years’ experience working with various modern databases. - 2+ years prior experience in IT transformations and system modernization initiatives from legacy to distributed platforms. - Hands-on experience with Large Language Models. - Demonstrated exposure to, or hands-on experience with, Generative AI coding assistants used across day-to-day engineering workflows in the SDLC, applying engineering judgment and validation. - Working knowledge of agentic workflows, spec-driven development, and custom instructions and prompt engineering, with the ability to establish team-level practices for effective AI-assisted development. - Understanding of broker-dealer capabilities and operations. - Excellent communication skills and a proven ability to communicate and lead other engineers in a collaborative environment. - Collaborative mindset coupled with a bias for action to effectively engage with fellow developers, architects, and adjacent teams. That's still a mix. Maybe better to keep Requirements as the Must-Have Qualifications block, Qualifications as Nice-to-Have, and omit Skills because no distinct skill set beyond those. But the instruction says "Prefer a few substantive sections over many thin ones." So we could have About the role, Responsibilities, Requirements, Qualifications, Benefits. That's five sections. Benefits: from Aquent Talent paragraph: subsidized health, vision, dental plans, paid sick leave, retirement plans with a match, free online training through Aquent Gymnasium. Thus we will output:

About the role

... introductory paragraphs ...

Responsibilities

• ... each bullet ...

Requirements

• ... each must-have qualification ...

Qualifications

• ... each nice-to-have ...

Benefits

• ... each benefit ...

We must not include Pay or Schedule. We need to preserve all substantive info: ensure we don't miss any bullet. Let's extract the introductory text: "Aquent is partnering with a leading financial services organization that is undergoing a significant technical transformation, modernizing its core technology infrastructure and challenging the status quo in the finance industry. This is an exceptional opportunity to join a dynamic team at the intersection of cutting-edge AI technology and complex financial domains, where you will redefine the future of financial technology and make a tangible impact on critical systems that underpin operations, ensuring a secure, seamless experience for millions of people. Are you ready to be at the forefront of innovation, shaping the next generation of financial technology? In this pivotal role, you will lead AI-focused workflows across the System Development Life Cycle, driving innovation and efficiency in how solutions are built and delivered. This is your chance to drive innovation, enhance system reliability, and contribute directly to solutions that impact millions, all within a culture of continuous improvement." We can combine into a paragraph. Now Responsibilities: "What You’ll Do" list: - Lead the integration and application of Generative AI coding assistants throughout the System Development Life Cycle, from implementation and refactoring to unit testing, regression support, code reviews, scripting, automation, troubleshooting, and documentation. - Drive the adoption of AI assistance for common development tasks, including code suggestions, test generation, review support, and automation scripts, while maintaining clear ownership for correctness and quality. - Pioneer the use of Generative AI to reduce context switching and accelerate delivery across various workflows, extending beyond just writing new code. - Apply practical familiarity with leading AI coding tools within IDE/CLI-style workflows. - Develop and implement agentic workflows and spec-driven development methodologies, translating low-level design artifacts into structured specifications that guide AI-assisted implementation. - Establish team-level practices for effective AI-assisted development, including custom instructions and prompt engineering. - Contribute to the modernization of core technology infrastructure and play a key role in IT transformations from legacy to distributed platforms. - Collaborate with fellow developers, architects, and adjacent teams, fostering a culture of innovation and continuous improvement. We need to preserve each as

. Now Requirements: Must-Have Qualifications list (each bullet). Let's list them exactly as in text: - Bachelor’s degree in Computer Science, Software Engineering, or a related technical field, or equivalent practical experience. - 7+ years of professional software engineering experience actively developing large-scale software using Java, Spring framework, cloud development, and Web Services supporting high-volume transactions in a highly available environment. - 2+ years of hands-on experience with AI/ML implementation and production deployment. - 6+ years of experience working with containers and microservices in the cloud. - 6+ years of experience in cloud deployment within a continuous integration and continuous delivery (CI/CD) model. - 2+ years of experience with major cloud platforms. - 2+ years’ experience working with various modern databases. - 2+ years prior experience in IT transformations and system modernization initiatives from legacy to distributed platforms. - Hands-on experience with Large Language Models. - Demonstrated exposure to, or hands-on experience with, Generative AI coding assistants used across day-to-day engineering workflows in the SDLC, applying engineering judgment and validation. - Working knowledge of agentic workflows, spec-driven development, and custom instructions and prompt engineering, with the ability to establish team-level practices for effective AI-assisted development. - Understanding of broker-dealer capabilities and operations. - Excellent communication skills and a proven ability to communicate and lead other engineers in a