DevOps Infrastructure Engineer
for section headings
- Use - for lists
- Use
for prose
- Don't repeat job title as heading
- Don't put Job ID/requisition numbers as headings
- Fold minor metadata into short
or drop
- Preserve ALL substantive information
- Remove boilerplate (EEO, scam warning, application instructions, agency notes)
- Only include sections with real content
- No filler/placeholder text
- No Pay/Schedule/Benefits sections unless actually stated
- Output ONLY HTML fragment
Let me parse the content:
The posting has:
- Intro about Fiserv (company description) - this is boilerplate/marketing, but "About Your Role" section has a paragraph describing the role. I'll include that as "About the role" section.
- "What You'll Do" - list of responsibilities
- "Experience You'll Need To Have" - list of requirements
- "Experience That Would Be Great To Have" - preferred qualifications
- "Important Information About This Role" - schedule (on-site Mon-Fri), work authorization, full-time direct-hire, background checks, government contractor info
- "Salary Range" - $82,000 - $141,600 for NJ/NY
- Then boilerplate: EEO, accommodation, agency note, scam warning, application instructions.
I should include:
- About the role (the paragraph under "About Your Role")
- Responsibilities (What You'll Do)
- Requirements (Experience You'll Need To Have)
- Qualifications (Experience That Would Be Great To Have) - maybe call it "Preferred qualifications"
- Schedule (from Important Information: on-site Mon-Fri)
- Work authorization (must have valid unrestricted US work auth, no sponsorship)
- Employment type (full-time, direct-hire)
- Background check info
- Pay (salary range)
But note: "Important Information About This Role" includes multiple points. I could make a "Role details" section or separate sections. The rules say use headings like Schedule, Pay, etc. So I'll create:
- Schedule (on-site Monday through Friday)
- Work authorization (must have valid unrestricted U.S. work authorization, no sponsorship)
- Employment type (full-time, direct-hire)
- Background checks (standard background checks, government contract requirements)
- Pay (salary range)
But the rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state schedule and pay. Benefits not explicitly stated (no mention of health, 401k, etc.). So I'll include Schedule and Pay.
Also, the "Important Information" includes "This role is on-site Monday through Friday." That's schedule. "You must currently possess valid and unrestricted U.S. work authorization..." That's work authorization. "This is a full-time, direct-hire position..." That's employment type. "All offers of employment are contingent on standard background checks..." That's background checks.
I'll create sections for each substantive piece.
Now, for the lists: The responsibilities are bullet points. The requirements are bullet points with sub-bullets (AWS services). I'll need to nest lists or flatten. The original uses nested bullets. I'll represent as nested
inside - or separate lists. Since the rule says use
- for any list, I can do nested lists.
Similarly, preferred qualifications are bullet points.
Now, the company intro paragraph at the very top ("Calling all innovators...") is marketing boilerplate. The rule says remove boilerplate. But "About Your Role" has a specific paragraph: "At Fiserv, we are dedicated to transforming financial services technology to benefit our clients. As a DevOps Infrastructure Engineer, you will be responsible for managing operations of large-scale high frequency, low latency applications on AWS. You will manage and operate large-scale, highly available, secure, and scalable AWS cloud infrastructure." That's substantive about the role. I'll include that as "About the role".
Now, let's write HTML.
Structure:
About the role
At Fiserv, we are dedicated to transforming financial services technology to benefit our clients. As a DevOps Infrastructure Engineer, you will be responsible for managing operations of large-scale high frequency, low latency applications on AWS. You will manage and operate large-scale, highly available, secure, and scalable AWS cloud infrastructure.
Responsibilities
- Responsible for managing operations of large-scale high frequency, low latency applications on AWS.
- Manage and operate large-scale, highly available, secure, and scalable AWS cloud infrastructure.
- Design, implement, and maintain CI/CD pipelines to automate application build, testing, deployment, and release processes.
- Provision and manage AWS infrastructure using Infrastructure as Code (Terraform, CloudFormation, or equivalent).
- Implement and maintain cloud monitoring, alerting, logging, and observability solutions using AWS CloudWatch, Dynatrace, Splunk, and related tools.
- Monitor application and infrastructure performance, availability, and reliability, ensuring compliance with SLAs.
- Drive AWS cost optimization initiatives by monitoring cloud spending, analyzing usage trends, rightsizing resources, and implementing cost-control measures.
- Implement AWS security best practices, including IAM, network security, encryption, secrets management, vulnerability remediation, and compliance controls.
- Collaborate with architects, developers, and security teams to design resilient and secure cloud-native solutions.
- Automate operational processes, incident response procedures, and infrastructure management using scripting and cloud-native services.
- Support disaster recovery, backup, high-availability, and business continuity initiatives.
- Develop operational runbooks, technical documentation, and knowledge base articles.
- Ensure security scanning, code quality checks, unit testing, and compliance validations are integrated into CI/CD workflows.
Requirements
- 4+ years of experience managing AWS cloud infrastructure in production environments.
- Strong hands-on experience with AWS services such as:
- EC2, ECS/EKS, Lambda
- VPC, Transit Gateway, Route 53, Load Balancers
- RDS, DynamoDB, S3
- CloudFormation, Terraform
- CloudWatch, CloudTrail, AWS Config
- IAM, Secrets Manager, KMS, WAF, Shield
- Experience building and maintaining CI/CD pipelines using Jenkins, GitHub Actions, GitLab CI, or similar platforms.
- Strong Infrastructure as Code experience using CloudFormation, Terraform.
- Experience with monitoring, observability, and incident management tools such as CloudWatch, Dynatrace, Splunk, or Datadog.
- Hands-on experience with scripting languages such as Python, Bash, or PowerShell.
- Understanding of cloud networking, security architecture, and AWS Well-Architected Framework.
- Experience with AWS cost management, budgeting, tagging strategies, Cost Explorer, and optimization techniques.
- Knowledge of container platforms such as Docker, ECS, or Kubernetes.
- Experience integrating security tools such as Sonatype, Fortify, Snyk, Prisma Cloud, or equivalent into CI/CD pipelines.
- Experience with AI-assisted SDLC / AI Coding tools experience
- Bachelor's degree in computer science, Information Technology, Information Systems, or a related field (or foreign equivalent degree) or equivalent work experience
Preferred qualifications
- Experience in the financial services industry
- AWS Certified Solutions Architect, AWS Certified DevOps Engineer, or AWS Security Specialty certifications.
- Experience with FinOps and cloud cost governance.
- Experience supporting high-frequency, low-latency production applications.
- Experience with Agile/Scrum delivery models.
- Experience using Jira, Confluence, Dynatrace, Splunk, and GitLab.
Schedule
This role is on-site Monday through Friday. Fiserv considers in-person collaboration to be an essential part of this role as in-person office experiences help with overall onboarding experience and leads to stronger productivity.
Work authorization
You must currently possess valid and unrestricted U.S. work authorization to be considered for this role. Individuals with temporary visas including, but not limited to, F-1 (OPT, CPT, STEM), H-1B, H-2, or TN, or any candidate requiring sponsorship, now or in the future, will not be considered for this role.
Employment type
This is a full-time, direct-hire position, and no contract options for unsolicited agency submissions will be considered.
Background checks
All offers of employment are contingent on standard background checks. Fiserv and certain of its affiliated companies are federal, state, and/or local government contractors. Should this position support a Federal Government contract, now or in the future, the successful candidate will be subject to a background check conducted by the U.S. Government to determine eligibility and suitability for federal contract employment for public trust or sensitive positions. Positions that support state and/or local contracts also may require additional background checks to determine eligibility and suitability.
Pay
Salary range: $82,000.00 - $141,600.00. These pay ranges apply to employees in New Jersey and New York. Pay ranges for employees in other states may differ. This position is not eligible for an annual incentive opportunity and is also not eligible to earn commissions.
That's all substantive content. I'll omit the EEO, accommodation, agency note, scam warning, application instructions.
Now, ensure no markdown code fences, just HTML fragment.
Let me double-check: The rule says "Do NOT repeat the job title as a heading (the page already shows it)". I didn't include job title heading. Good.
"do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short or drop it." There's no job ID in the posting.
"Preserve ALL substantive information; do NOT invent or summarize away detail." I've preserved all bullet points.
"Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Done.
"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." I created Schedule, Work authorization, Employment type, Background checks,
for prose - Don't repeat job title as heading - Don't put Job ID/requisition numbers as headings - Fold minor metadata into short
or drop - Preserve ALL substantive information - Remove boilerplate (EEO, scam warning, application instructions, agency notes) - Only include sections with real content - No filler/placeholder text - No Pay/Schedule/Benefits sections unless actually stated - Output ONLY HTML fragment Let me parse the content: The posting has: - Intro about Fiserv (company description) - this is boilerplate/marketing, but "About Your Role" section has a paragraph describing the role. I'll include that as "About the role" section. - "What You'll Do" - list of responsibilities - "Experience You'll Need To Have" - list of requirements - "Experience That Would Be Great To Have" - preferred qualifications - "Important Information About This Role" - schedule (on-site Mon-Fri), work authorization, full-time direct-hire, background checks, government contractor info - "Salary Range" - $82,000 - $141,600 for NJ/NY - Then boilerplate: EEO, accommodation, agency note, scam warning, application instructions. I should include: - About the role (the paragraph under "About Your Role") - Responsibilities (What You'll Do) - Requirements (Experience You'll Need To Have) - Qualifications (Experience That Would Be Great To Have) - maybe call it "Preferred qualifications" - Schedule (from Important Information: on-site Mon-Fri) - Work authorization (must have valid unrestricted US work auth, no sponsorship) - Employment type (full-time, direct-hire) - Background check info - Pay (salary range) But note: "Important Information About This Role" includes multiple points. I could make a "Role details" section or separate sections. The rules say use headings like Schedule, Pay, etc. So I'll create: - Schedule (on-site Monday through Friday) - Work authorization (must have valid unrestricted U.S. work authorization, no sponsorship) - Employment type (full-time, direct-hire) - Background checks (standard background checks, government contract requirements) - Pay (salary range) But the rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state schedule and pay. Benefits not explicitly stated (no mention of health, 401k, etc.). So I'll include Schedule and Pay. Also, the "Important Information" includes "This role is on-site Monday through Friday." That's schedule. "You must currently possess valid and unrestricted U.S. work authorization..." That's work authorization. "This is a full-time, direct-hire position..." That's employment type. "All offers of employment are contingent on standard background checks..." That's background checks. I'll create sections for each substantive piece. Now, for the lists: The responsibilities are bullet points. The requirements are bullet points with sub-bullets (AWS services). I'll need to nest lists or flatten. The original uses nested bullets. I'll represent as nested
- inside
- or separate lists. Since the rule says use
- for any list, I can do nested lists.
Similarly, preferred qualifications are bullet points.
Now, the company intro paragraph at the very top ("Calling all innovators...") is marketing boilerplate. The rule says remove boilerplate. But "About Your Role" has a specific paragraph: "At Fiserv, we are dedicated to transforming financial services technology to benefit our clients. As a DevOps Infrastructure Engineer, you will be responsible for managing operations of large-scale high frequency, low latency applications on AWS. You will manage and operate large-scale, highly available, secure, and scalable AWS cloud infrastructure." That's substantive about the role. I'll include that as "About the role".
Now, let's write HTML.
Structure:
About the role
At Fiserv, we are dedicated to transforming financial services technology to benefit our clients. As a DevOps Infrastructure Engineer, you will be responsible for managing operations of large-scale high frequency, low latency applications on AWS. You will manage and operate large-scale, highly available, secure, and scalable AWS cloud infrastructure.
Responsibilities
- Responsible for managing operations of large-scale high frequency, low latency applications on AWS.
- Manage and operate large-scale, highly available, secure, and scalable AWS cloud infrastructure.
- Design, implement, and maintain CI/CD pipelines to automate application build, testing, deployment, and release processes.
- Provision and manage AWS infrastructure using Infrastructure as Code (Terraform, CloudFormation, or equivalent).
- Implement and maintain cloud monitoring, alerting, logging, and observability solutions using AWS CloudWatch, Dynatrace, Splunk, and related tools.
- Monitor application and infrastructure performance, availability, and reliability, ensuring compliance with SLAs.
- Drive AWS cost optimization initiatives by monitoring cloud spending, analyzing usage trends, rightsizing resources, and implementing cost-control measures.
- Implement AWS security best practices, including IAM, network security, encryption, secrets management, vulnerability remediation, and compliance controls.
- Collaborate with architects, developers, and security teams to design resilient and secure cloud-native solutions.
- Automate operational processes, incident response procedures, and infrastructure management using scripting and cloud-native services.
- Support disaster recovery, backup, high-availability, and business continuity initiatives.
- Develop operational runbooks, technical documentation, and knowledge base articles.
- Ensure security scanning, code quality checks, unit testing, and compliance validations are integrated into CI/CD workflows.
Requirements
- 4+ years of experience managing AWS cloud infrastructure in production environments.
- Strong hands-on experience with AWS services such as:
- EC2, ECS/EKS, Lambda
- VPC, Transit Gateway, Route 53, Load Balancers
- RDS, DynamoDB, S3
- CloudFormation, Terraform
- CloudWatch, CloudTrail, AWS Config
- IAM, Secrets Manager, KMS, WAF, Shield
- Experience building and maintaining CI/CD pipelines using Jenkins, GitHub Actions, GitLab CI, or similar platforms.
- Strong Infrastructure as Code experience using CloudFormation, Terraform.
- Experience with monitoring, observability, and incident management tools such as CloudWatch, Dynatrace, Splunk, or Datadog.
- Hands-on experience with scripting languages such as Python, Bash, or PowerShell.
- Understanding of cloud networking, security architecture, and AWS Well-Architected Framework.
- Experience with AWS cost management, budgeting, tagging strategies, Cost Explorer, and optimization techniques.
- Knowledge of container platforms such as Docker, ECS, or Kubernetes.
- Experience integrating security tools such as Sonatype, Fortify, Snyk, Prisma Cloud, or equivalent into CI/CD pipelines.
- Experience with AI-assisted SDLC / AI Coding tools experience
- Bachelor's degree in computer science, Information Technology, Information Systems, or a related field (or foreign equivalent degree) or equivalent work experience
Preferred qualifications
- Experience in the financial services industry
- AWS Certified Solutions Architect, AWS Certified DevOps Engineer, or AWS Security Specialty certifications.
- Experience with FinOps and cloud cost governance.
- Experience supporting high-frequency, low-latency production applications.
- Experience with Agile/Scrum delivery models.
- Experience using Jira, Confluence, Dynatrace, Splunk, and GitLab.
Schedule
This role is on-site Monday through Friday. Fiserv considers in-person collaboration to be an essential part of this role as in-person office experiences help with overall onboarding experience and leads to stronger productivity.
Work authorization
You must currently possess valid and unrestricted U.S. work authorization to be considered for this role. Individuals with temporary visas including, but not limited to, F-1 (OPT, CPT, STEM), H-1B, H-2, or TN, or any candidate requiring sponsorship, now or in the future, will not be considered for this role.
Employment type
This is a full-time, direct-hire position, and no contract options for unsolicited agency submissions will be considered.
Background checks
All offers of employment are contingent on standard background checks. Fiserv and certain of its affiliated companies are federal, state, and/or local government contractors. Should this position support a Federal Government contract, now or in the future, the successful candidate will be subject to a background check conducted by the U.S. Government to determine eligibility and suitability for federal contract employment for public trust or sensitive positions. Positions that support state and/or local contracts also may require additional background checks to determine eligibility and suitability.
Pay
Salary range: $82,000.00 - $141,600.00. These pay ranges apply to employees in New Jersey and New York. Pay ranges for employees in other states may differ. This position is not eligible for an annual incentive opportunity and is also not eligible to earn commissions.
That's all substantive content. I'll omit the EEO, accommodation, agency note, scam warning, application instructions. Now, ensure no markdown code fences, just HTML fragment. Let me double-check: The rule says "Do NOT repeat the job title as a heading (the page already shows it)". I didn't include job title heading. Good. "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a shortor drop it." There's no job ID in the posting. "Preserve ALL substantive information; do NOT invent or summarize away detail." I've preserved all bullet points. "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Done. "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." I created Schedule, Work authorization, Employment type, Background checks,
- for any list, I can do nested lists.
Similarly, preferred qualifications are bullet points.
Now, the company intro paragraph at the very top ("Calling all innovators...") is marketing boilerplate. The rule says remove boilerplate. But "About Your Role" has a specific paragraph: "At Fiserv, we are dedicated to transforming financial services technology to benefit our clients. As a DevOps Infrastructure Engineer, you will be responsible for managing operations of large-scale high frequency, low latency applications on AWS. You will manage and operate large-scale, highly available, secure, and scalable AWS cloud infrastructure." That's substantive about the role. I'll include that as "About the role".
Now, let's write HTML.
Structure: