AI DevOps Engineer| Hybrid: Chicago, IL or NYC, NY
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate like EEO, legal, etc. Also remove duplicated lines, navigation, cookie, etc. Also remove application instructions (like apply through website). Also remove AI-assisted screening etc? Those are maybe considered boilerplate? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove lines about background check, AI-assisted screening, etc? Those might be considered legal/boilerplate. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Background check is legal? Might be considered legal. Safer to remove it. Also remove "This job is also eligible for bonus pay." That's part of compensation, maybe keep in Pay section. But "We offer a comprehensive package of benefits including paid time off, medical/dental/vision insurance and 401(k) to eligible employees." That's benefits.
We need to include sections only when posting has real specific content. So we will have sections: About the role (maybe from Role Overview paragraph), Responsibilities, Requirements, Qualifications (Preferred Qualifications), Benefits, Pay. Possibly also "Core Competencies" but that's similar to skills; but we can incorporate into Requirements or Qualifications. However instruction: prefer a few substantive sections over many thin ones. Could combine Core Competencies into Requirements or Skills. But we have separate Requirements and Preferred Qualifications. Could keep them.
We must not create Pay/Schedule/Benefits sections unless posting actually states them. Benefits yes, Pay yes. Schedule not given, omit.
We need to ensure we don't include placeholder text like "commensurate with experience". Not present.
Now extract content.
Role Overview paragraph: "We are seeking an experienced Senior DevOps Engineer to design, implement, automate, and support enterprise infrastructure and application delivery platforms across both on-premises and hyperscaler cloud environments. This role will be responsible for driving DevOps practices, CI/CD automation, Infrastructure as Code (IaC), platform reliability, and operational excellence in hybrid infrastructure landscapes. The ideal candidate will possess deep expertise in cloud and data center technologies, automation, container platforms, and production support. This individual will partner closely with Infrastructure, Application Development, Security, Architecture, and Operations teams to deliver scalable, secure, and highly available technology solutions."
That's prose.
Responsibilities: multiple bullet-like paragraphs under headings: DevOps, Platform Engineering & Automation; On-Premise Infrastructure Operations; AI & Frontier Technology Platform Support; Hybrid Cloud & Hyperscaler Support; Monitoring, Reliability & Production Support. Each contains sentences. We'll need to turn each duty into list items? The instruction: Use
- for any list of duties/requirements/benefits. So we should extract each duty as list items. Could group under each subheading? But we only have one Responsibilities section heading
Responsibilities
then a with items. We'll need to preserve all substantive information; we can break each sentence into list items.
Let's list responsibilities:
- Design, build, and maintain enterprise DevOps platforms supporting software development and infrastructure teams.
- Develop and manage CI/CD pipelines utilizing Jenkins, Azure DevOps, or similar tools.
- Implement Infrastructure as Code (IaC) using Ansible, or equivalent technologies.
- Automate application deployment, infrastructure provisioning, configuration management, patching, and operational workflows.
- Drive continuous improvement initiatives focused on deployment speed, reliability, security, and operational efficiency.
- Support enterprise data center infrastructure including virtualized environments, compute, storage, networking, and backup solutions.
- Manage Linux-based environments supporting business-critical applications.
- Integrate on-premises systems with cloud platforms to support hybrid operational models.
- Participate in infrastructure lifecycle management, upgrades, patching, disaster recovery testing, and capacity planning.
- Deploy, automate, and support AI/ML infrastructure platforms and services in cloud and on-premises environments.
- Support AI engineering teams with scalable environments for model training, inference, experimentation, and deployment.
- Manage infrastructure supporting generative AI, large language models (LLMs), AI copilots, vector databases, and AI orchestration frameworks.
- Establish operational monitoring, security controls, compliance, and reliability standards for AI solutions.
- Design, deploy, and support workloads across Microsoft Azure and Google Cloud Platform (GCP).
- Manage and optimize hybrid cloud environments integrating on-premises infrastructure with cloud services.
- Support cloud governance, security standards, identity management, cost optimization, and operational best practices.
- Partner with cloud vendors and internal teams to troubleshoot and resolve complex platform issues.
- Develop cloud migration, modernization, and platform engineering strategies.
- Design and support containerized application platforms using Kubernetes, OpenShift, AKS, EKS, or GKE.
- Manage cluster administration, networking, security, scalability, and operational health.
- Implement and maintain enterprise monitoring, logging, and observability solutions.
- Support production systems with a focus on availability, performance, and resiliency.
- Participate in incident management, root cause analysis, problem management, and on-call support rotations.
- Develop operational runbooks and support procedures for critical platforms.
- Apply Site Reliability Engineering (SRE) principles to improve system availability and reduce operational risk.
- Ensure compliance with organizational security policies, audit requirements, and regulatory standards.
- Support disaster recovery, business continuity, and resiliency initiatives.
That seems comprehensive.
Now Requirements: list:
- Bachelor's degree in Computer Science, Information Technology, Engineering, or a related field.
- 7+ years of experience in DevOps, Infrastructure Engineering, Cloud Engineering, or Platform Operations.
- Strong experience supporting both on-premises infrastructure and cloud-based environments.
- Extensive hands-on experience with Jenkins administration, pipeline development, automation, and integration.
- Experience with CI/CD platforms such as Jenkins and Azure DevOps
- Experience implementing Infrastructure as Code Ansible.
- Strong Linux administration experience.
- Hands-on experience with Kubernetes, Docker, and container orchestration platforms.
- Experience supporting Azure or GCP environments.
- Strong scripting and automation skills using PowerShell, Python, Bash, or similar languages.
- Experience with enterprise monitoring tools such as Grafana, Prometheus, or Azure Monitor.
- Strong troubleshooting, problem-solving, and communication skills.
Note there is a duplicated line: "Experience with CI/CD platforms such as Jenkins and Azure DevOpsExperience implementing Infrastructure as Code Ansible." Actually the text had no space. We'll split.
Now Preferred Qualifications (maybe Qualifications section). We'll treat as Qualifications.
- Multi-cloud experience across Azure and GCP.
- Azure DevOps Engineer Expert, Azure Solutions Architect or related certifications.
- Experience managing large-scale hybrid cloud transformations.
- Knowledge of platform engineering and self-service infrastructure models.
- Experience supporting retail, distribution, supply chain, or large-scale customer-facing platforms.
Core Competencies list: but could be merged into Requirements or Qualifications. To avoid many thin sections, maybe we can incorporate Core Competencies into Requirements or Qualifications as a list. But we already have Requirements and Qualifications. Could add another section "Key Skills" but instruction prefers few sections. Could omit Core Competencies as it's redundant with Requirements. However we must preserve ALL substantive information; we cannot drop it. So we need to include it somewhere. Could add a section "Key Competencies" as Key Competencies
with list. That's another section but still okay. However instruction: prefer a few substantive sections over many thin ones. Adding another section may be okay if it's substantive. We'll include it.
Now Benefits: "We offer a comprehensive package of benefits including paid time off, medical/dental/vision insurance and 401(k) to eligible employees." Also mention bonus pay earlier: "This job is also eligible for bonus pay." We'll combine.
Thus Benefits section list:
- Paid time off
- Medical/dental/vision insurance
- 401(k) (for eligible employees)
- Bonus pay eligibility
Now Pay: "The salary range for this role is $150,000 USD to $190,000 USD. This job is also eligible for bonus pay." Actually bonus pay already in benefits; but we can mention in Pay: salary range and bonus eligibility.
Thus Pay section: maybe The salary range for this role is $150,000 USD to $190,000 USD, with eligibility for bonus pay.
Now we need to exclude boilerplate: lines about location? Location is given: "Location: This position can be located in the following area(s): Chicago, IL (Hybrid) or NYC, NY (Hybrid)". That's substantive; we should include location. Where to put? Could be a short paragraph after About the role or its own section? Not listed as a standard heading but we could include as a under About the role or separate "Location". The instruction only mentions specific headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It didn't list Location. But we need to preserve ALL substantive information. We could include location in a
within About the role section or as a separate
before sections. Since we cannot add arbitrary headings not listed, better to embed location in About the role paragraph or as a
after the overview. The About the role section currently contains the role overview paragraph; we can add location info as another paragraph within that section (still under same
About the role
). That's allowed.
Now we need to remove duplicated lines, navigation, cookie, legal, EEO, etc. Also remove lines about background check, AI-assisted screening, etc. Also remove "An offer of employment may be conditional upon successful completion of a background check..." etc. Also remove "Your current employer will not be contacted without your permission." Also remove "You can apply for this role through the Circana careers website or Intranet site for internal candidates." Also remove "This role is subject to AI-assisted screening." Also remove "Circana uses artificial intelligence (AI) to assess resumes..." Also remove "This position is expected to remain open for approximately 30 days..." etc.
Now we need to output only HTML fragment, no /, no markdown fences.
Let's craft.
Structure:
About the role
We are seeking an experienced Senior DevOps Engineer to design, implement, automate, and support enterprise infrastructure and application delivery platforms across both on-premises and hyperscaler cloud environments. This role will be responsible for driving DevOps practices, CI/CD automation, Infrastructure as Code (IaC), platform reliability, and operational excellence in hybrid infrastructure landscapes. The ideal candidate will possess deep expertise in cloud and data center technologies, automation, container platforms, and production support. This individual will partner closely with Infrastructure, Application Development, Security, Architecture, and Operations teams to deliver scalable, secure, and highly available technology solutions.
Location: This position can be located in Chicago, IL (Hybrid) or NYC, NY (Hybrid).
Responsibilities
- Design, build, and maintain enterprise DevOps platforms supporting software development and infrastructure teams.
- Develop and manage CI/CD pipelines utilizing Jenkins, Azure DevOps, or similar tools.
- Implement Infrastructure as Code (IaC) using Ansible, or equivalent technologies.
for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate like EEO, legal, etc. Also remove duplicated lines, navigation, cookie, etc. Also remove application instructions (like apply through website). Also remove AI-assisted screening etc? Those are maybe considered boilerplate? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove lines about background check, AI-assisted screening, etc? Those might be considered legal/boilerplate. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Background check is legal? Might be considered legal. Safer to remove it. Also remove "This job is also eligible for bonus pay." That's part of compensation, maybe keep in Pay section. But "We offer a comprehensive package of benefits including paid time off, medical/dental/vision insurance and 401(k) to eligible employees." That's benefits. We need to include sections only when posting has real specific content. So we will have sections: About the role (maybe from Role Overview paragraph), Responsibilities, Requirements, Qualifications (Preferred Qualifications), Benefits, Pay. Possibly also "Core Competencies" but that's similar to skills; but we can incorporate into Requirements or Qualifications. However instruction: prefer a few substantive sections over many thin ones. Could combine Core Competencies into Requirements or Skills. But we have separate Requirements and Preferred Qualifications. Could keep them. We must not create Pay/Schedule/Benefits sections unless posting actually states them. Benefits yes, Pay yes. Schedule not given, omit. We need to ensure we don't include placeholder text like "commensurate with experience". Not present. Now extract content. Role Overview paragraph: "We are seeking an experienced Senior DevOps Engineer to design, implement, automate, and support enterprise infrastructure and application delivery platforms across both on-premises and hyperscaler cloud environments. This role will be responsible for driving DevOps practices, CI/CD automation, Infrastructure as Code (IaC), platform reliability, and operational excellence in hybrid infrastructure landscapes. The ideal candidate will possess deep expertise in cloud and data center technologies, automation, container platforms, and production support. This individual will partner closely with Infrastructure, Application Development, Security, Architecture, and Operations teams to deliver scalable, secure, and highly available technology solutions." That's prose. Responsibilities: multiple bullet-like paragraphs under headings: DevOps, Platform Engineering & Automation; On-Premise Infrastructure Operations; AI & Frontier Technology Platform Support; Hybrid Cloud & Hyperscaler Support; Monitoring, Reliability & Production Support. Each contains sentences. We'll need to turn each duty into list items? The instruction: Use
- for any list of duties/requirements/benefits. So we should extract each duty as list items. Could group under each subheading? But we only have one Responsibilities section heading
Responsibilities
then a- with items. We'll need to preserve all substantive information; we can break each sentence into list items.
Let's list responsibilities:
- Design, build, and maintain enterprise DevOps platforms supporting software development and infrastructure teams.
- Develop and manage CI/CD pipelines utilizing Jenkins, Azure DevOps, or similar tools.
- Implement Infrastructure as Code (IaC) using Ansible, or equivalent technologies.
- Automate application deployment, infrastructure provisioning, configuration management, patching, and operational workflows.
- Drive continuous improvement initiatives focused on deployment speed, reliability, security, and operational efficiency.
- Support enterprise data center infrastructure including virtualized environments, compute, storage, networking, and backup solutions.
- Manage Linux-based environments supporting business-critical applications.
- Integrate on-premises systems with cloud platforms to support hybrid operational models.
- Participate in infrastructure lifecycle management, upgrades, patching, disaster recovery testing, and capacity planning.
- Deploy, automate, and support AI/ML infrastructure platforms and services in cloud and on-premises environments.
- Support AI engineering teams with scalable environments for model training, inference, experimentation, and deployment.
- Manage infrastructure supporting generative AI, large language models (LLMs), AI copilots, vector databases, and AI orchestration frameworks.
- Establish operational monitoring, security controls, compliance, and reliability standards for AI solutions.
- Design, deploy, and support workloads across Microsoft Azure and Google Cloud Platform (GCP).
- Manage and optimize hybrid cloud environments integrating on-premises infrastructure with cloud services.
- Support cloud governance, security standards, identity management, cost optimization, and operational best practices.
- Partner with cloud vendors and internal teams to troubleshoot and resolve complex platform issues.
- Develop cloud migration, modernization, and platform engineering strategies.
- Design and support containerized application platforms using Kubernetes, OpenShift, AKS, EKS, or GKE.
- Manage cluster administration, networking, security, scalability, and operational health.
- Implement and maintain enterprise monitoring, logging, and observability solutions.
- Support production systems with a focus on availability, performance, and resiliency.
- Participate in incident management, root cause analysis, problem management, and on-call support rotations.
- Develop operational runbooks and support procedures for critical platforms.
- Apply Site Reliability Engineering (SRE) principles to improve system availability and reduce operational risk.
- Ensure compliance with organizational security policies, audit requirements, and regulatory standards.
- Support disaster recovery, business continuity, and resiliency initiatives.
That seems comprehensive.
Now Requirements: list:
- Bachelor's degree in Computer Science, Information Technology, Engineering, or a related field.
- 7+ years of experience in DevOps, Infrastructure Engineering, Cloud Engineering, or Platform Operations.
- Strong experience supporting both on-premises infrastructure and cloud-based environments.
- Extensive hands-on experience with Jenkins administration, pipeline development, automation, and integration.
- Experience with CI/CD platforms such as Jenkins and Azure DevOps
- Experience implementing Infrastructure as Code Ansible.
- Strong Linux administration experience.
- Hands-on experience with Kubernetes, Docker, and container orchestration platforms.
- Experience supporting Azure or GCP environments.
- Strong scripting and automation skills using PowerShell, Python, Bash, or similar languages.
- Experience with enterprise monitoring tools such as Grafana, Prometheus, or Azure Monitor.
- Strong troubleshooting, problem-solving, and communication skills.
Note there is a duplicated line: "Experience with CI/CD platforms such as Jenkins and Azure DevOpsExperience implementing Infrastructure as Code Ansible." Actually the text had no space. We'll split.
Now Preferred Qualifications (maybe Qualifications section). We'll treat as Qualifications.
- Multi-cloud experience across Azure and GCP.
- Azure DevOps Engineer Expert, Azure Solutions Architect or related certifications.
- Experience managing large-scale hybrid cloud transformations.
- Knowledge of platform engineering and self-service infrastructure models.
- Experience supporting retail, distribution, supply chain, or large-scale customer-facing platforms.
Core Competencies list: but could be merged into Requirements or Qualifications. To avoid many thin sections, maybe we can incorporate Core Competencies into Requirements or Qualifications as a list. But we already have Requirements and Qualifications. Could add another section "Key Skills" but instruction prefers few sections. Could omit Core Competencies as it's redundant with Requirements. However we must preserve ALL substantive information; we cannot drop it. So we need to include it somewhere. Could add a section "Key Competencies" as
- Design, build, and maintain enterprise DevOps platforms supporting software development and infrastructure teams.
- Develop and manage CI/CD pipelines utilizing Jenkins, Azure DevOps, or similar tools.
- Implement Infrastructure as Code (IaC) using Ansible, or equivalent technologies.
Key Competencies
with list. That's another section but still okay. However instruction: prefer a few substantive sections over many thin ones. Adding another section may be okay if it's substantive. We'll include it. Now Benefits: "We offer a comprehensive package of benefits including paid time off, medical/dental/vision insurance and 401(k) to eligible employees." Also mention bonus pay earlier: "This job is also eligible for bonus pay." We'll combine. Thus Benefits section list: - Paid time off - Medical/dental/vision insurance - 401(k) (for eligible employees) - Bonus pay eligibility Now Pay: "The salary range for this role is $150,000 USD to $190,000 USD. This job is also eligible for bonus pay." Actually bonus pay already in benefits; but we can mention in Pay: salary range and bonus eligibility. Thus Pay section: maybeThe salary range for this role is $150,000 USD to $190,000 USD, with eligibility for bonus pay.
Now we need to exclude boilerplate: lines about location? Location is given: "Location: This position can be located in the following area(s): Chicago, IL (Hybrid) or NYC, NY (Hybrid)". That's substantive; we should include location. Where to put? Could be a short paragraph after About the role or its own section? Not listed as a standard heading but we could include as aunder About the role or separate "Location". The instruction only mentions specific headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It didn't list Location. But we need to preserve ALL substantive information. We could include location in a
within About the role section or as a separate
before sections. Since we cannot add arbitrary headings not listed, better to embed location in About the role paragraph or as a
after the overview. The About the role section currently contains the role overview paragraph; we can add location info as another paragraph within that section (still under same
About the role
). That's allowed. Now we need to remove duplicated lines, navigation, cookie, legal, EEO, etc. Also remove lines about background check, AI-assisted screening, etc. Also remove "An offer of employment may be conditional upon successful completion of a background check..." etc. Also remove "Your current employer will not be contacted without your permission." Also remove "You can apply for this role through the Circana careers website or Intranet site for internal candidates." Also remove "This role is subject to AI-assisted screening." Also remove "Circana uses artificial intelligence (AI) to assess resumes..." Also remove "This position is expected to remain open for approximately 30 days..." etc. Now we need to output only HTML fragment, no /, no markdown fences. Let's craft. Structure:About the role
We are seeking an experienced Senior DevOps Engineer to design, implement, automate, and support enterprise infrastructure and application delivery platforms across both on-premises and hyperscaler cloud environments. This role will be responsible for driving DevOps practices, CI/CD automation, Infrastructure as Code (IaC), platform reliability, and operational excellence in hybrid infrastructure landscapes. The ideal candidate will possess deep expertise in cloud and data center technologies, automation, container platforms, and production support. This individual will partner closely with Infrastructure, Application Development, Security, Architecture, and Operations teams to deliver scalable, secure, and highly available technology solutions.
Location: This position can be located in Chicago, IL (Hybrid) or NYC, NY (Hybrid).
Responsibilities