Lead Performance Test Engineer
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.
We need to decide which sections to include. The posting includes:
- About The Role (intro paragraph)
- Responsibilities: bullet list of duties (Design and execute performance... etc.)
- Work model: description about remote, flexibility.
- What You Need To Have To Be Considered: list of required qualifications/experience.
- These will help you stand out: list of preferred qualifications.
- Salary And Other Compensation: salary range and incentive.
- Benefits: list of benefits.
Also there is a line about "We’re excited to meet people..." which is more generic encouragement; could be part of About the role or maybe a concluding paragraph. It's substantive but not a list; we can include as paragraph under About the role or separate? Probably part of About the role.
We need to avoid filler sections like "Schedule" if not present. There's no schedule specifics. So we omit Schedule.
We need to use
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat the job title as heading. So we just output sections.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all bullet points exactly as given? We can keep them as list items preserving content. Should we keep the exact phrasing? Probably yes.
We need to remove boilerplate like "cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." There's no explicit such content besides maybe the line about "Cognizant will only consider applicants..." which is substantive (eligibility). Keep it.
We need to ensure we don't include filler like "commensurate with experience" etc. Not present.
Now structure:
About the role
As a Lead Performance Test Engineer, you will make an impact by leading and executing performance engineering initiatives for complex enterprise and cloud-native applications. This is a hands-on technical role requiring deep expertise in performance testing, automation, cloud platforms, observability, and application resiliency. You will collaborate with development, architecture, platform engineering, DevOps, and Site Reliability Engineering teams to establish performance standards, implement automated quality gates, identify system bottlenecks, and improve application scalability and operational readiness.
In this role, you will design and execute performance, load, stress, endurance, scalability, and capacity-testing strategies for enterprise applications, APIs, and cloud-based services. Build and maintain automated performance-testing frameworks using NeoLoad and custom performance engineering solutions. Integrate performance testing into CI/CD pipelines using GitLab CI/CD or comparable automation platforms, including performance thresholds and quality gates. Analyze applications, database, infrastructure, network, and cloud performance to identify bottlenecks and provide actionable optimization recommendations. Use AWS services and observability platforms such as CloudWatch, Dynatrace, Splunk, Grafana, and Prometheus to troubleshoot complex performance issues. Plan and execute Chaos Engineering and resiliency-testing exercises to evaluate fault tolerance, recovery capabilities, and operational readiness. Develop automation utilities using Python, Java, SQL, APIs, and scripting languages to improve testing efficiency and reduce manual effort. Partner with technical and business stakeholders to define performance KPIs, engineering standards, capacity requirements, and performance-improvement plans.
Work model: We strive to provide flexibility wherever possible. Based on this role’s business requirements, this is a Remote position open to qualified applicants in the United States for the duration of the assignment. Regardless of your working arrangement, we are here to support a healthy work-life balance through our various wellbeing programs. The working arrangements for this role are accurate as of the date of posting. This may change based on the project you are engaged in, as well as business and client requirements. Rest assured, we will always be clear about role expectations.
We’re excited to meet people who share our mission and can make an impact in a variety of ways. Don’t hesitate to apply, even if you only meet the minimum requirements listed. Think about your transferable experiences and unique skills that make you stand out as someone who can bring new and exciting things to this role.
Then responsibilities? Actually the above includes responsibilities already. But we might separate responsibilities as a list. However the instructions: Use - for any list of duties/requirements/benefits. The responsibilities are a list of duties; we could put them in a
. The prose we already used for responsibilities could be turned into list items. But we need to preserve all substantive information; we can either keep as prose or list. The rule says use - for any list of duties/requirements/benefits. It doesn't forbid using prose for duties, but better to use list for clarity. However we already used prose for responsibilities; we could change to list. Let's restructure: Have a section
Responsibilities
with - each duty.
Similarly, Requirements:
Requirements
with list of required qualifications.
Qualifications? Could be same as Requirements; but we have also "These will help you stand out" which could be Preferred Qualifications
or Skills
. The instruction list includes Skills as possible heading. We'll use Preferred Qualifications
maybe but they said use headings like Skills, Benefits, Pay, Schedule. We can use Skills for preferred qualifications. Or we can use Qualifications for required and Skills for preferred. Let's decide:
- About the role: intro paragraph.
- Responsibilities: list.
- Requirements: list (mandatory).
- Skills: list (preferred).
- Benefits: list.
- Pay: maybe we need a Pay section for salary. The instruction includes Pay as possible heading. We'll include Pay
with salary range and incentive.
We should not include Schedule as not present.
Now we need to ensure we don't duplicate content. Let's extract responsibilities from the text:
From "In This Role, You Will" bullet list:
- Design and execute performance, load, stress, endurance, scalability, and capacity-testing strategies for enterprise applications, APIs, and cloud-based services.
- Build and maintain automated performance-testing frameworks using NeoLoad and custom performance engineering solutions.
- Integrate performance testing into CI/CD pipelines using GitLab CI/CD or comparable automation platforms, including performance thresholds and quality gates.
- Analyze applications, database, infrastructure, network, and cloud performance to identify bottlenecks and provide actionable optimization recommendations.
- Use AWS services and observability platforms such as CloudWatch, Dynatrace, Splunk, Grafana, and Prometheus to troubleshoot complex performance issues.
- Plan and execute Chaos Engineering and resiliency-testing exercises to evaluate fault tolerance, recovery capabilities, and operational readiness.
- Develop automation utilities using Python, Java, SQL, APIs, and scripting languages to improve testing efficiency and reduce manual effort.
- Partner with technical and business stakeholders to define performance KPIs, engineering standards, capacity requirements, and performance-improvement plans.
Also earlier paragraph about leading and executing performance engineering initiatives etc. Could be part of responsibilities as well. But we can include that as a separate bullet maybe: "Lead and execute performance engineering initiatives for complex enterprise and cloud-native applications." However the instruction says preserve ALL substantive information. So we need to include that too. Let's add as a bullet.
Also "Collaborate with development, architecture, platform engineering, DevOps, and Site Reliability Engineering teams to establish performance standards, implement automated quality gates, identify system bottlenecks, and improve application scalability and operational readiness." That's also a duty.
Thus responsibilities list will include those.
Now Requirements list from "What You Need To Have To Be Considered":
- At least 10 years of hands-on experience in performance testing, performance engineering, or non-functional testing for enterprise applications.
- Hands-on expertise with NeoLoad or a comparable enterprise performance testing tool, including test design, workload modeling, execution, analysis, and reporting.
- Experience integrating automated performance tests into CI/CD pipelines using GitLab CI/CD or similar automation platforms.
- Hands-on experience with AWS cloud services and cloud-native architectures, including services such as EC2, ECS, EKS, Lambda, RDS, S3, and CloudWatch.
- Programming and scripting experience using Python, Java, SQL, and shell scripting, including experience testing REST APIs, microservices, and distributed systems.
- Experience diagnosing performance issues across application, database, infrastructure, network, and cloud layers using observability tools such as Dynatrace, AppDynamics, Splunk, Grafana, Prometheus, or Elastic Stack.
- Experience working with containerized environments and orchestration platforms such as Kubernetes, Docker, OpenShift, ECS, or EKS.
- Strong communication, collaboration, and stakeholder-management skills, with the flexibility to support planned production testing during off-hours or weekends when required.
Now Preferred qualifications list from "These will help you stand out":
- Experience designing and implementing Chaos Engineering, resiliency-testing, or disaster-recovery validation programs.
- Knowledge of Site Reliability Engineering principles, operational excellence practices, service-level objectives, and performance-based quality gates.
- Experience with capacity planning, scalability analysis, production-readiness assessments, and cloud-cost optimization.
- Experience developing reusable performance engineering frameworks, accelerators, or custom automation utilities.
- Exposure to AI-driven performance analysis, anomaly detection, root-cause analysis, predictive capacity planning, or intelligent test automation.
Now Benefits list from "Benefits":
- 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
Also note: "Cognizant will only consider applicants for this position who are legally authorized to work in the United States without company sponsorship. *Please note, this role is not able to offer visa transfer or sponsorship now or in the future*". This is eligibility requirement; could be part of Requirements or a separate note. We'll include as a paragraph under Requirements maybe.
Now Pay section: Salary range and incentive.
- The annual salary for this position is between $83,250 to $132,000 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.
We'll put in or
? It's not a list but we can use . The rule says use
- for any list of duties/requirements/
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. We need to decide which sections to include. The posting includes: - About The Role (intro paragraph) - Responsibilities: bullet list of duties (Design and execute performance... etc.) - Work model: description about remote, flexibility. - What You Need To Have To Be Considered: list of required qualifications/experience. - These will help you stand out: list of preferred qualifications. - Salary And Other Compensation: salary range and incentive. - Benefits: list of benefits. Also there is a line about "We’re excited to meet people..." which is more generic encouragement; could be part of About the role or maybe a concluding paragraph. It's substantive but not a list; we can include as paragraph under About the role or separate? Probably part of About the role. We need to avoid filler sections like "Schedule" if not present. There's no schedule specifics. So we omit Schedule. We need to use
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat the job title as heading. So we just output sections.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all bullet points exactly as given? We can keep them as list items preserving content. Should we keep the exact phrasing? Probably yes.
We need to remove boilerplate like "cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." There's no explicit such content besides maybe the line about "Cognizant will only consider applicants..." which is substantive (eligibility). Keep it.
We need to ensure we don't include filler like "commensurate with experience" etc. Not present.
Now structure:
About the role
As a Lead Performance Test Engineer, you will make an impact by leading and executing performance engineering initiatives for complex enterprise and cloud-native applications. This is a hands-on technical role requiring deep expertise in performance testing, automation, cloud platforms, observability, and application resiliency. You will collaborate with development, architecture, platform engineering, DevOps, and Site Reliability Engineering teams to establish performance standards, implement automated quality gates, identify system bottlenecks, and improve application scalability and operational readiness.
In this role, you will design and execute performance, load, stress, endurance, scalability, and capacity-testing strategies for enterprise applications, APIs, and cloud-based services. Build and maintain automated performance-testing frameworks using NeoLoad and custom performance engineering solutions. Integrate performance testing into CI/CD pipelines using GitLab CI/CD or comparable automation platforms, including performance thresholds and quality gates. Analyze applications, database, infrastructure, network, and cloud performance to identify bottlenecks and provide actionable optimization recommendations. Use AWS services and observability platforms such as CloudWatch, Dynatrace, Splunk, Grafana, and Prometheus to troubleshoot complex performance issues. Plan and execute Chaos Engineering and resiliency-testing exercises to evaluate fault tolerance, recovery capabilities, and operational readiness. Develop automation utilities using Python, Java, SQL, APIs, and scripting languages to improve testing efficiency and reduce manual effort. Partner with technical and business stakeholders to define performance KPIs, engineering standards, capacity requirements, and performance-improvement plans.
Work model: We strive to provide flexibility wherever possible. Based on this role’s business requirements, this is a Remote position open to qualified applicants in the United States for the duration of the assignment. Regardless of your working arrangement, we are here to support a healthy work-life balance through our various wellbeing programs. The working arrangements for this role are accurate as of the date of posting. This may change based on the project you are engaged in, as well as business and client requirements. Rest assured, we will always be clear about role expectations.
We’re excited to meet people who share our mission and can make an impact in a variety of ways. Don’t hesitate to apply, even if you only meet the minimum requirements listed. Think about your transferable experiences and unique skills that make you stand out as someone who can bring new and exciting things to this role.
Then responsibilities? Actually the above includes responsibilities already. But we might separate responsibilities as a list. However the instructions: Use - for any list of duties/requirements/benefits. The responsibilities are a list of duties; we could put them in a
. The prose we already used for responsibilities could be turned into list items. But we need to preserve all substantive information; we can either keep as prose or list. The rule says use - for any list of duties/requirements/benefits. It doesn't forbid using prose for duties, but better to use list for clarity. However we already used prose for responsibilities; we could change to list. Let's restructure: Have a section
Responsibilities
with - each duty.
Similarly, Requirements:
Requirements
with list of required qualifications.
Qualifications? Could be same as Requirements; but we have also "These will help you stand out" which could be Preferred Qualifications
or Skills
. The instruction list includes Skills as possible heading. We'll use Preferred Qualifications
maybe but they said use headings like Skills, Benefits, Pay, Schedule. We can use Skills for preferred qualifications. Or we can use Qualifications for required and Skills for preferred. Let's decide:
- About the role: intro paragraph.
- Responsibilities: list.
- Requirements: list (mandatory).
- Skills: list (preferred).
- Benefits: list.
- Pay: maybe we need a Pay section for salary. The instruction includes Pay as possible heading. We'll include Pay
with salary range and incentive.
We should not include Schedule as not present.
Now we need to ensure we don't duplicate content. Let's extract responsibilities from the text:
From "In This Role, You Will" bullet list:
- Design and execute performance, load, stress, endurance, scalability, and capacity-testing strategies for enterprise applications, APIs, and cloud-based services.
- Build and maintain automated performance-testing frameworks using NeoLoad and custom performance engineering solutions.
- Integrate performance testing into CI/CD pipelines using GitLab CI/CD or comparable automation platforms, including performance thresholds and quality gates.
- Analyze applications, database, infrastructure, network, and cloud performance to identify bottlenecks and provide actionable optimization recommendations.
- Use AWS services and observability platforms such as CloudWatch, Dynatrace, Splunk, Grafana, and Prometheus to troubleshoot complex performance issues.
- Plan and execute Chaos Engineering and resiliency-testing exercises to evaluate fault tolerance, recovery capabilities, and operational readiness.
- Develop automation utilities using Python, Java, SQL, APIs, and scripting languages to improve testing efficiency and reduce manual effort.
- Partner with technical and business stakeholders to define performance KPIs, engineering standards, capacity requirements, and performance-improvement plans.
Also earlier paragraph about leading and executing performance engineering initiatives etc. Could be part of responsibilities as well. But we can include that as a separate bullet maybe: "Lead and execute performance engineering initiatives for complex enterprise and cloud-native applications." However the instruction says preserve ALL substantive information. So we need to include that too. Let's add as a bullet.
Also "Collaborate with development, architecture, platform engineering, DevOps, and Site Reliability Engineering teams to establish performance standards, implement automated quality gates, identify system bottlenecks, and improve application scalability and operational readiness." That's also a duty.
Thus responsibilities list will include those.
Now Requirements list from "What You Need To Have To Be Considered":
- At least 10 years of hands-on experience in performance testing, performance engineering, or non-functional testing for enterprise applications.
- Hands-on expertise with NeoLoad or a comparable enterprise performance testing tool, including test design, workload modeling, execution, analysis, and reporting.
- Experience integrating automated performance tests into CI/CD pipelines using GitLab CI/CD or similar automation platforms.
- Hands-on experience with AWS cloud services and cloud-native architectures, including services such as EC2, ECS, EKS, Lambda, RDS, S3, and CloudWatch.
- Programming and scripting experience using Python, Java, SQL, and shell scripting, including experience testing REST APIs, microservices, and distributed systems.
- Experience diagnosing performance issues across application, database, infrastructure, network, and cloud layers using observability tools such as Dynatrace, AppDynamics, Splunk, Grafana, Prometheus, or Elastic Stack.
- Experience working with containerized environments and orchestration platforms such as Kubernetes, Docker, OpenShift, ECS, or EKS.
- Strong communication, collaboration, and stakeholder-management skills, with the flexibility to support planned production testing during off-hours or weekends when required.
Now Preferred qualifications list from "These will help you stand out":
- Experience designing and implementing Chaos Engineering, resiliency-testing, or disaster-recovery validation programs.
- Knowledge of Site Reliability Engineering principles, operational excellence practices, service-level objectives, and performance-based quality gates.
- Experience with capacity planning, scalability analysis, production-readiness assessments, and cloud-cost optimization.
- Experience developing reusable performance engineering frameworks, accelerators, or custom automation utilities.
- Exposure to AI-driven performance analysis, anomaly detection, root-cause analysis, predictive capacity planning, or intelligent test automation.
Now Benefits list from "Benefits":
- 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
Also note: "Cognizant will only consider applicants for this position who are legally authorized to work in the United States without company sponsorship. *Please note, this role is not able to offer visa transfer or sponsorship now or in the future*". This is eligibility requirement; could be part of Requirements or a separate note. We'll include as a paragraph under Requirements maybe.
Now Pay section: Salary range and incentive.
- The annual salary for this position is between $83,250 to $132,000 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.
We'll put in or
? It's not a list but we can use . The rule says use
- for any list of duties/requirements/
for prose. We must not repeat the job title as heading. So we just output sections. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all bullet points exactly as given? We can keep them as list items preserving content. Should we keep the exact phrasing? Probably yes. We need to remove boilerplate like "cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." There's no explicit such content besides maybe the line about "Cognizant will only consider applicants..." which is substantive (eligibility). Keep it. We need to ensure we don't include filler like "commensurate with experience" etc. Not present. Now structure:
About the role
As a Lead Performance Test Engineer, you will make an impact by leading and executing performance engineering initiatives for complex enterprise and cloud-native applications. This is a hands-on technical role requiring deep expertise in performance testing, automation, cloud platforms, observability, and application resiliency. You will collaborate with development, architecture, platform engineering, DevOps, and Site Reliability Engineering teams to establish performance standards, implement automated quality gates, identify system bottlenecks, and improve application scalability and operational readiness.
In this role, you will design and execute performance, load, stress, endurance, scalability, and capacity-testing strategies for enterprise applications, APIs, and cloud-based services. Build and maintain automated performance-testing frameworks using NeoLoad and custom performance engineering solutions. Integrate performance testing into CI/CD pipelines using GitLab CI/CD or comparable automation platforms, including performance thresholds and quality gates. Analyze applications, database, infrastructure, network, and cloud performance to identify bottlenecks and provide actionable optimization recommendations. Use AWS services and observability platforms such as CloudWatch, Dynatrace, Splunk, Grafana, and Prometheus to troubleshoot complex performance issues. Plan and execute Chaos Engineering and resiliency-testing exercises to evaluate fault tolerance, recovery capabilities, and operational readiness. Develop automation utilities using Python, Java, SQL, APIs, and scripting languages to improve testing efficiency and reduce manual effort. Partner with technical and business stakeholders to define performance KPIs, engineering standards, capacity requirements, and performance-improvement plans.
Work model: We strive to provide flexibility wherever possible. Based on this role’s business requirements, this is a Remote position open to qualified applicants in the United States for the duration of the assignment. Regardless of your working arrangement, we are here to support a healthy work-life balance through our various wellbeing programs. The working arrangements for this role are accurate as of the date of posting. This may change based on the project you are engaged in, as well as business and client requirements. Rest assured, we will always be clear about role expectations.
We’re excited to meet people who share our mission and can make an impact in a variety of ways. Don’t hesitate to apply, even if you only meet the minimum requirements listed. Think about your transferable experiences and unique skills that make you stand out as someone who can bring new and exciting things to this role.
Then responsibilities? Actually the above includes responsibilities already. But we might separate responsibilities as a list. However the instructions: Use- for any list of duties/requirements/benefits. The responsibilities are a list of duties; we could put them in a
- . The prose we already used for responsibilities could be turned into list items. But we need to preserve all substantive information; we can either keep as prose or list. The rule says use
- for any list of duties/requirements/benefits. It doesn't forbid using prose for duties, but better to use list for clarity. However we already used prose for responsibilities; we could change to list. Let's restructure: Have a section
Responsibilities
with- each duty.
Similarly, Requirements:
Requirements
with list of required qualifications. Qualifications? Could be same as Requirements; but we have also "These will help you stand out" which could bePreferred Qualifications
orSkills
. The instruction list includes Skills as possible heading. We'll usePreferred Qualifications
maybe but they said use headings like Skills, Benefits, Pay, Schedule. We can use Skills for preferred qualifications. Or we can use Qualifications for required and Skills for preferred. Let's decide: - About the role: intro paragraph. - Responsibilities: list. - Requirements: list (mandatory). - Skills: list (preferred). - Benefits: list. - Pay: maybe we need a Pay section for salary. The instruction includes Pay as possible heading. We'll includePay
with salary range and incentive. We should not include Schedule as not present. Now we need to ensure we don't duplicate content. Let's extract responsibilities from the text: From "In This Role, You Will" bullet list: - Design and execute performance, load, stress, endurance, scalability, and capacity-testing strategies for enterprise applications, APIs, and cloud-based services. - Build and maintain automated performance-testing frameworks using NeoLoad and custom performance engineering solutions. - Integrate performance testing into CI/CD pipelines using GitLab CI/CD or comparable automation platforms, including performance thresholds and quality gates. - Analyze applications, database, infrastructure, network, and cloud performance to identify bottlenecks and provide actionable optimization recommendations. - Use AWS services and observability platforms such as CloudWatch, Dynatrace, Splunk, Grafana, and Prometheus to troubleshoot complex performance issues. - Plan and execute Chaos Engineering and resiliency-testing exercises to evaluate fault tolerance, recovery capabilities, and operational readiness. - Develop automation utilities using Python, Java, SQL, APIs, and scripting languages to improve testing efficiency and reduce manual effort. - Partner with technical and business stakeholders to define performance KPIs, engineering standards, capacity requirements, and performance-improvement plans. Also earlier paragraph about leading and executing performance engineering initiatives etc. Could be part of responsibilities as well. But we can include that as a separate bullet maybe: "Lead and execute performance engineering initiatives for complex enterprise and cloud-native applications." However the instruction says preserve ALL substantive information. So we need to include that too. Let's add as a bullet. Also "Collaborate with development, architecture, platform engineering, DevOps, and Site Reliability Engineering teams to establish performance standards, implement automated quality gates, identify system bottlenecks, and improve application scalability and operational readiness." That's also a duty. Thus responsibilities list will include those. Now Requirements list from "What You Need To Have To Be Considered": - At least 10 years of hands-on experience in performance testing, performance engineering, or non-functional testing for enterprise applications. - Hands-on expertise with NeoLoad or a comparable enterprise performance testing tool, including test design, workload modeling, execution, analysis, and reporting. - Experience integrating automated performance tests into CI/CD pipelines using GitLab CI/CD or similar automation platforms. - Hands-on experience with AWS cloud services and cloud-native architectures, including services such as EC2, ECS, EKS, Lambda, RDS, S3, and CloudWatch. - Programming and scripting experience using Python, Java, SQL, and shell scripting, including experience testing REST APIs, microservices, and distributed systems. - Experience diagnosing performance issues across application, database, infrastructure, network, and cloud layers using observability tools such as Dynatrace, AppDynamics, Splunk, Grafana, Prometheus, or Elastic Stack. - Experience working with containerized environments and orchestration platforms such as Kubernetes, Docker, OpenShift, ECS, or EKS. - Strong communication, collaboration, and stakeholder-management skills, with the flexibility to support planned production testing during off-hours or weekends when required. Now Preferred qualifications list from "These will help you stand out": - Experience designing and implementing Chaos Engineering, resiliency-testing, or disaster-recovery validation programs. - Knowledge of Site Reliability Engineering principles, operational excellence practices, service-level objectives, and performance-based quality gates. - Experience with capacity planning, scalability analysis, production-readiness assessments, and cloud-cost optimization. - Experience developing reusable performance engineering frameworks, accelerators, or custom automation utilities. - Exposure to AI-driven performance analysis, anomaly detection, root-cause analysis, predictive capacity planning, or intelligent test automation. Now Benefits list from "Benefits": - 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 Also note: "Cognizant will only consider applicants for this position who are legally authorized to work in the United States without company sponsorship. *Please note, this role is not able to offer visa transfer or sponsorship now or in the future*". This is eligibility requirement; could be part of Requirements or a separate note. We'll include as a paragraph under Requirements maybe. Now Pay section: Salary range and incentive. - The annual salary for this position is between $83,250 to $132,000 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. We'll put inor
- ? It's not a list but we can use
- for any list of duties/requirements/
. The rule says use
- each duty.
Similarly, Requirements:
- for any list of duties/requirements/benefits. It doesn't forbid using prose for duties, but better to use list for clarity. However we already used prose for responsibilities; we could change to list. Let's restructure: Have a section