Quality Engineer (AI Automation)

We need to output HTML fragment with headings

for sections: 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 not include Job ID etc. Must preserve all substantive info, no invention. Remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines. Must not create sections with filler like "commensurate with experience". Pay section only if posting actually states salary. It does: "The annual salary for this position is $65,000.00 depending on experience and other qualifications of the successful candidate." Also mentions discretionary annual incentive program. So Pay section can include that. Benefits: they list benefits. So include Benefits section. Schedule: not mentioned. So omit Schedule. About the role: we have "About Cognizant’s Quality Engineering & Assurance Team" and "Position Overview". Could combine as About the role. Provide content. Responsibilities: list of duties. Requirements: maybe "Required Skills & Qualifications". Could split into Requirements and Qualifications and Skills? The instruction says use headings for those categories if content exists. We have "Required Skills & Qualifications" which includes education, experience, skills. Could separate into Requirements (education/experience) and Skills (technical). But we must not invent sections if content is thin. Let's parse: - About Cognizant’s Quality Engineering & Assurance Team (description) - Position Overview (overview) - Key Responsibilities (list) - Required Skills & Qualifications (list includes education, experience, skills, etc.) - Location (maybe not a heading per list; but not in allowed headings; we could fold into a short p under About? But location is substantive; but not in allowed headings list. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples; we could also use other headings? Probably we should stick to those. Location not in list, but we could include as a short p under About the role or maybe under Responsibilities? Better to include as a p after About the role? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings when appropriate; other headings maybe not allowed? It says "use

for section headings (e.g. ...)" meaning those are examples of headings we can use; we could also use other headings if needed? Safer to stick to those. Location could be placed in a

under About the role or maybe under Responsibilities? Probably better to add a short paragraph after About the role: "Location: New hires will be hired to the Cognizant office in Dallas/Plano TX, Charlotte/Cary NC, Teaneck NJ, Miami FL where you will work alongside other experienced Cognizant associates delivering technology solutions. Applicants must be willing to relocate to this major geographic area." That's substantive. Start Date: also substantive; could be placed under About the role as well. We must not include disclaimer, work authorization, etc. Those are boilerplate? Work authorization maybe relevant but it's a restriction; but it's not in allowed headings; could be placed as a p under About? Might be considered boilerplate? It's a specific condition; but it's not about role. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Work authorization is not exactly those but could be considered legal? Might be considered a condition; but it's not about role. Safer to omit? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Work authorization is substantive. But we don't have a heading for it; we could include as a p under About the role. It's not boilerplate; it's a specific condition. So include. Also "Start Date" is substantive. Thus sections: - About the role: include team description, position overview, location, start date, work authorization. - Responsibilities: list from Key Responsibilities. - Requirements: maybe education/experience? Could combine with Qualifications? But we have both Required Skills & Qualifications. Could split: Requirements (education/experience) and Qualifications (skills). But we have overlapping. Let's decide: Use Requirements for education/experience, Skills for technical skills, Qualifications maybe for other? But we have only one block. To avoid thin sections, we could make one section "Requirements" containing all required skills & qualifications. Or we could have "Qualifications" and "Skills". The instruction says prefer a few substantive sections over many thin ones. So better to have one section for Requirements (including education, experience, skills). Then we can omit Qualifications and Skills headings if they'd be thin. But we need to follow instruction: use headings for those categories if content exists. If we put all in Requirements, we still have content for Requirements; we don't need Qualifications or Skills headings. That's okay. Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay. Check for duplicated lines: In Responsibilities, there is duplicate line: "Develop and maintain test automation scripts and frameworks using Java and Python." appears twice (once in bullet list and later). We must remove duplicated lines. Also "Have proficiency with test and defect management tools, particularly JIRA or any similar tools." appears in Required Skills & Qualifications but also maybe in Responsibilities? Not in responsibilities. We'll keep. Now craft HTML. Structure:

About the role

... combine team description, position overview, location, start date, work authorization.

Responsibilities

• Design, develop, and maintain test automation frameworks using Java and Python.
• Write clean, efficient, and scalable automation scripts for new features to ensure robust test coverage across all deliverables.
• Perform API testing: Understand API concepts, develop and execute functional tests, interpret Swagger YAML files, and validate endpoints using Postman or Rest Assured automation frameworks.
• Conduct database testing: Write and execute SQL queries to retrieve, update, and delete data, ensuring database integrity and reliability.
• Own quality for assigned features and components: Collaborate with product managers and developers on requirements analysis, create detailed test cases, execute comprehensive test suites (functional, integration, regression), and provide final quality sign-off.
• Track and report testing progress: Use tools such as JIRA, ADO, or ALM for defect logging and reporting, ensuring transparency of feature quality to the team and stakeholders. Also understanding of CI/CD concepts.
• Implement and execute test plans for AI/ML applications: Support QA activities and certify the quality of AI-powered systems, including hands-on testing of chatbots for intent recognition, conversational flow, response accuracy, and edge case handling.
• Leverage modern AI tools to enhance workflow: Utilize AI code assistants like GitHub Copilot to accelerate test script development and explore generative AI for tasks such as test data creation and bug report summarization.
• Ensure AI reliability and fairness: Execute test cases to identify issues related to bias, fairness, and model robustness, contributing to the overall trustworthiness of AI systems.

Note: removed duplicate "Develop and maintain test automation scripts and frameworks using Java and Python." and also removed "Have proficiency with test and defect management tools, particularly JIRA or any similar tools." from responsibilities (it wasn't there). Actually that line is in Required Skills & Qualifications; we will include in Requirements. Now Requirements section: combine education/experience/skills. We need to list: - Bachelor’s or Master’s degree in Computer Science, Engineering, or a related technical field, or equivalent practical experience. - 0 – 1 years of professional experience in a Quality Assurance or Quality Engineering role. - Some hands-on experience developing and maintaining test automation scripts and frameworks using Java and Python. - Basic understanding of the Software Testing Life Cycle (STLC) and practical experience working in an Agile/Scrum environment. - A keen interest in or prior experience testing AI-powered applications, such as chatbots or other AI/ML-based systems. - Hands-on experience with the Hybrid Automation frameworks. - Familiarity with CI/CD concepts and tools (e.g., Jenkins, GitLab, GitHub Actions). - Exposure to performance testing tools (e.g., JMeter, Gatling). - Basic knowledge of cloud platforms (AWS, Azure, or GCP) and containerization (Docker) - A passion for learning and staying up to date with the latest trends in AI and software testing. - Have proficiency with test and defect management tools, particularly JIRA or any similar tools. We should ensure no duplication. Also note "Some hands-on experience developing and maintaining test automation scripts and frameworks using Java and Python." is similar to earlier but okay. Now Benefits section: list as

• ... each benefit. Benefits list: - Medical/Dental/Vision/Life Insurance - Paid holidays plus Paid Time Off - 401(k) plan and contributions - Long-term/Short-term Disability - Paid Parental Leave - Employee Stock Purchase Plan We should keep as is. Pay section: include salary and discretionary annual incentive program. We can put:

  The annual salary for this position is $65,000.00 depending on experience and other qualifications of the successful candidate. This position is also eligible for Cognizant’s discretionary annual incentive program, based on performance and subject to the terms of Cognizant’s applicable plans.

  Now ensure no boilerplate: removed disclaimer, work authorization? We included work authorization in About the role? Actually we said we would include work authorization. Let's incorporate that: "Due to the nature of this position, Cognizant cannot provide sponsorship for U.S. work authorization (including participation in a CPT/OPT program) for this role." Include as a p. Also include Start Date: "New hires will start in September 2026. While we will attempt to honor candidate start date preferences, business need and position availability will determine final start date assignment. Exact start date will be communicated with enough time for you to plan effectively." Location: as earlier. Now About the role paragraph: combine team description, position overview, location, start date, work authorization. We need to avoid too long but keep all info. Let's craft:

  About Cognizant’s Quality Engineering & Assurance team: Our Quality Engineering & Assurance team is the innovative engine at our company. We are a dedicated group of builders and problem-solvers responsible for the most critical, customer-facing platforms. Within this team, the Quality practice is not a downstream function but a fully integrated partner in development. Our mission is to embed quality into every stage of the lifecycle, and as a Quality Engineer, you will be on the front lines of this effort.

  Position Overview: Are you a driven Quality Engineer passionate about building the future of testing? We are seeking a creative and hands-on QE to be a key contributor to our quality practice. This is an exciting opportunity to move beyond traditional QA and dive into the world of AI-driven testing, helping us build and maintain robust quality standards for our mission-critical intelligent applications that are redefining customer interaction.

  Location: New hires will be hired to the Cognizant office in Dallas/Plano TX, Charlotte/Cary NC, Teaneck NJ, Miami FL where you will work alongside other experienced Cognizant associates delivering technology solutions. Applicants must be willing to relocate to this major geographic area.

  Start Date: New hires will start in September 2026. While we will attempt to honor candidate start date preferences, business need and position availability will determine final start date assignment. Exact start date will be communicated with enough