DevOps & Security Engineer
for section headings, - for lists,
for prose. No markdown fences. No html/body tags. Include sections only when posting has real specific content. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we need to extract the substantive parts: intro paragraph about company, "What You'll Be Doing" list of responsibilities, "What You Should Have" list of requirements, "Compensation & Benefits" with pay range and benefits description. Also maybe "Physical Requirements"? That's not a heading we have defined; we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map sections accordingly. "What You'll Be Doing" => Responsibilities. "What You Should Have" => Requirements (or Qualifications/Skills). Could split into Requirements and Skills? But we prefer few substantive sections. Could combine requirements and skills into one Requirements section. Benefits and Pay: we have compensation & benefits section includes pay range and benefits description. Could split into Pay and Benefits but we can combine? The instruction: prefer a few substantive sections over many thin ones. So we could have sections: Responsibilities, Requirements, Benefits (including pay). Or separate Pay and Benefits if both present. The posting includes pay range and benefits description. Could make two sections: Pay and Benefits. But that's thin? Might be okay. However we need to avoid filler like "commensurate with experience". The pay range is specific. Benefits description is generic but mentions categories. That's substantive enough.
We must not repeat job title as heading. No Job ID.
We need to strip boilerplate: The intro paragraph about company is okay. Then "What You'll Be Doing" list. Then "What You Should Have" list. Then "Compensation & Benefits" paragraph. Possibly also "Physical Requirements" but that's not a standard heading; we could omit as not requested. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. Physical Requirements is specific but not in allowed headings; we could ignore or maybe map to something else? Not needed.
We also need to remove duplicated lines, EEO statement, accommodations request, recruiting fraud alert, special notation, etc.
Thus final HTML:
Intro paragraph(s) about company.
Responsibilities
- ... each responsibility as list item.
Requirements
- ... each requirement.
Pay
The starting base pay range for this position is $117,249-$144,837 and may vary based on factors such as job-related knowledge, skills, experience, and performance.
Benefits
- Health & Family Support
- Financial Security
- Learning & Development
- Rewards & Recognition
- Wellbeing & Mental Health
- Work-Life Balance
- Fun Perks
We need to ensure we preserve all substantive information from responsibilities and requirements. Let's extract them.
Responsibilities list from posting:
- Design, build, and maintain CI/CD pipelines in Azure DevOps (ADO) to automate packaging, validation, and deployment of enterprise platform configurations and customizations while ensuring security is integrated throughout the development lifecycle.
- Own and operate the environment promotion workflow (Dev → Test → Production), enforcing quality gates and release controls at each stage to protect operations stability.
- Develop and maintain automated test and validation frameworks for source code packages prior to deployment, including integration checks against SAP, DataHub (Ignition/SQL), Kafka, and Bartender interfaces.
- Collaborate with application developers and systems analysts to establish branching strategies, pull request workflows, and versioning conventions that support parallel build cycles across multiple workstreams.
- Manage infrastructure-as-code and configuration management for enterprise platforms environments, ensuring environment parity and reproducibility across Dev, Test, and Production tiers.
- Partner with the Architecture team to define and uphold deployment standards, cutover runbooks, and rollback procedures for project go-lives and platform upgrades.
- Support post-deployment monitoring and incident response for the enterprise platforms, diagnosing pipeline failures, deployment anomalies, and environment drift across plant instances.
- Maintain deployment documentation, release notes, and ADO pipeline definitions in alignment with the team's established Way of Working standards.
- Contribute to the ongoing build-out of the team's DevOps maturity, identifying opportunities to reduce manual effort, increase deployment reliability, and shorten lead times from development to production.
- Collaborate with cross-functional teams (development, operations, and security) to design and deploy secure cloud infrastructure and applications on Microsoft Azure.
- Leverage Wiz to continuously monitor, identify, and remediate vulnerabilities across cloud environments, containers, and applications.
- Integrate security tools and practices into CI/CD pipelines, including automated security scans, vulnerability management, and compliance checks to reduce risks.
- Ensure that infrastructure, applications, and data comply with industry standards and security best practices (e.g., GDPR, SOC 2).
- Implement and maintain cloud security controls, including secure access management and the protection of sensitive data.
- Perform regular security audits, conduct threat assessments, and lead incident response efforts to identify and mitigate security risks proactively.
That's many items.
Requirements list:
- 4-Year / Bachelor’s Degree in Computer Science, Information Technology, Computer Engineering, or equivalent years of directly relevant work experience required.
- 4–6 years of hands-on DevOps or release engineering experience required, with demonstrated ownership of CI/CD pipelines in a production environment.
- Proven expertise with Azure DevOps (ADO), including YAML pipeline authoring, release pipelines, environment management, and test plan integration required.
- Experience managing environment promotion workflows (Dev → Test → Production) with approval gates, quality checks, and rollback capabilities required.
- Proficiency in scripting languages (C#, PowerShell or Python) for deployment automation, environment configuration, and pre/post-deployment validation required.
- Working knowledge of Windows and Linux Server environments.
- Experience with version control systems and branching strategies that support multiple concurrent development streams required.
- Familiarity with enterprise application integration patterns; experience working with or automating deployments that interact with ERP systems (e.g., SAP), messaging platforms (e.g., Kafka), or industrial data systems (e.g., Ignition/SQL) preferred.
- Experience with ERP, MES, SCADA, or other manufacturing or operations technology platforms is a plus; candidates with general DevOps experience and a demonstrated ability to ramp on domain-specific platforms will be considered.
- Experience with ERP, MES enterprise platforms preferred.
- OpenShift / Redhat experience preferred.
- Experience with infrastructure-as-code tools (Terraform, Ansible, or Azure Resource Manager templates) for environment provisioning preferred.
- Experience with containerization (Docker, Kubernetes) for supporting application services adjacent to the ERP / MES platform preferred.
We need to keep required vs preferred distinction? The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we should keep the wording as is, maybe separate required and preferred? But we can keep as list items with the original phrasing.
We should not include duplicated lines. There's some duplication: "Experience with ERP, MES enterprise platforms preferred." appears twice? Actually there is "Experience with ERP, MES, SCADA, or other manufacturing or operations technology platforms is a plus; candidates with general DevOps experience and a demonstrated ability to ramp on domain-specific platforms will be considered." and then "Experience with ERP, MES enterprise platforms preferred." That's similar but not identical; we keep both.
Now Benefits list: The posting lists categories: Health & Family Support, Financial Security, Learning & Development, Rewards & Recognition, Wellbeing & Mental Health, Work-Life Balance, Fun Perks. We'll put each as - .
Now intro paragraph: The first paragraph(s) before "What You'll Be Doing". Let's capture:
"Ready to join a global leader in air movement and ventilation? At Greenheck Group, joining our team means more than just starting a job, it’s joining an award-winning culture prioritizing your growth and development. Our unwavering commitment in supporting our team members both personally and professionally has earned us national recognition time and time again. As an innovative, environmentally responsible manufacturer of commercial HVAC systems, Greenheck Group designs and manufactures industry-leading air movement and ventilation solutions through our family of trusted brands. Our products are found in commercial, institutional, and industrial facilities worldwide, from schools and hospitals to factories and stadiums. Since 1947, we’ve proudly invested in our people and our communities, fostering innovation, leadership, and opportunity at every level. We are more than products, we are a team of inspired people doing extraordinary things."
We can combine into one or multiple
tags. Use
for prose. Could be one paragraph.
Now ensure we don't include any boilerplate like "SPECIAL NOTATION", "Physical Requirements", "EEO STATEMENT", etc.
Now output HTML fragment.
Let's craft:
Ready to join a global leader in air movement and ventilation? At Greenheck Group, joining our team means more than just starting a job, it’s joining an award-winning culture prioritizing your growth and development. Our unwavering commitment in supporting our team members both personally and professionally has earned us national recognition time and time again. As an innovative, environmentally responsible manufacturer of commercial HVAC systems, Greenheck Group designs and manufactures industry-leading air movement and ventilation solutions through our family of trusted brands. Our products are found in commercial, institutional, and industrial facilities worldwide, from schools and hospitals to factories and stadiums. Since 1947, we’ve proudly invested in our people and our communities, fostering innovation, leadership, and opportunity at every level. We are more than products, we are a team of inspired people doing extraordinary things.
Responsibilities
- Design, build, and maintain CI/CD pipelines in Azure DevOps (ADO) to automate packaging, validation, and deployment of enterprise platform configurations and customizations while ensuring security is integrated throughout the development lifecycle.
- Own and operate the environment promotion workflow (Dev → Test → Production), enforcing quality gates and release controls at each stage to protect operations stability.
- Develop and maintain automated test and validation frameworks for source code packages prior to deployment, including integration checks against SAP, DataHub (Ignition/SQL), Kafka, and Bartender interfaces.
- Collaborate with application developers and systems analysts to establish branching strategies, pull request workflows, and versioning conventions that support parallel build cycles across multiple workstreams.
- Manage infrastructure-as-code and configuration management for enterprise platforms environments, ensuring environment parity and reproducibility across Dev, Test, and Production tiers.
- Partner with the Architecture team to define and uphold deployment standards, cutover runbooks, and rollback procedures for project go-lives and platform upgrades.
- Support post-deployment monitoring and incident response for the enterprise platforms, diagnosing pipeline failures, deployment anomalies, and environment drift across plant instances.
- Maintain deployment documentation, release notes, and ADO pipeline definitions in alignment with the team's established Way of Working standards.
- Contribute to the ongoing build-out of the team's DevOps maturity, identifying opportunities to reduce manual effort, increase deployment reliability, and shorten lead times from development to production.
- Collaborate with cross-functional teams (development, operations, and security) to design and deploy secure cloud infrastructure and applications on Microsoft Azure.
- Leverage Wiz to continuously monitor, identify, and remediate vulnerabilities across cloud environments, containers, and applications.
- Integrate security tools and practices into CI/CD pipelines, including automated security scans, vulnerability management, and compliance checks to reduce risks.
- Ensure that infrastructure, applications, and data comply with industry standards and security best practices (e.g., GDPR,
for prose. No markdown fences. No html/body tags. Include sections only when posting has real specific content. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we need to extract the substantive parts: intro paragraph about company, "What You'll Be Doing" list of responsibilities, "What You Should Have" list of requirements, "Compensation & Benefits" with pay range and benefits description. Also maybe "Physical Requirements"? That's not a heading we have defined; we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map sections accordingly. "What You'll Be Doing" => Responsibilities. "What You Should Have" => Requirements (or Qualifications/Skills). Could split into Requirements and Skills? But we prefer few substantive sections. Could combine requirements and skills into one Requirements section. Benefits and Pay: we have compensation & benefits section includes pay range and benefits description. Could split into Pay and Benefits but we can combine? The instruction: prefer a few substantive sections over many thin ones. So we could have sections: Responsibilities, Requirements, Benefits (including pay). Or separate Pay and Benefits if both present. The posting includes pay range and benefits description. Could make two sections: Pay and Benefits. But that's thin? Might be okay. However we need to avoid filler like "commensurate with experience". The pay range is specific. Benefits description is generic but mentions categories. That's substantive enough. We must not repeat job title as heading. No Job ID. We need to strip boilerplate: The intro paragraph about company is okay. Then "What You'll Be Doing" list. Then "What You Should Have" list. Then "Compensation & Benefits" paragraph. Possibly also "Physical Requirements" but that's not a standard heading; we could omit as not requested. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. Physical Requirements is specific but not in allowed headings; we could ignore or maybe map to something else? Not needed. We also need to remove duplicated lines, EEO statement, accommodations request, recruiting fraud alert, special notation, etc. Thus final HTML:
Intro paragraph(s) about company.
Responsibilities
- ... each responsibility as list item.
Requirements
- ... each requirement.
Pay
The starting base pay range for this position is $117,249-$144,837 and may vary based on factors such as job-related knowledge, skills, experience, and performance.
Benefits
- Health & Family Support
- Financial Security
- Learning & Development
- Rewards & Recognition
- Wellbeing & Mental Health
- Work-Life Balance
- Fun Perks
tags. Use
for prose. Could be one paragraph. Now ensure we don't include any boilerplate like "SPECIAL NOTATION", "Physical Requirements", "EEO STATEMENT", etc. Now output HTML fragment. Let's craft:
Ready to join a global leader in air movement and ventilation? At Greenheck Group, joining our team means more than just starting a job, it’s joining an award-winning culture prioritizing your growth and development. Our unwavering commitment in supporting our team members both personally and professionally has earned us national recognition time and time again. As an innovative, environmentally responsible manufacturer of commercial HVAC systems, Greenheck Group designs and manufactures industry-leading air movement and ventilation solutions through our family of trusted brands. Our products are found in commercial, institutional, and industrial facilities worldwide, from schools and hospitals to factories and stadiums. Since 1947, we’ve proudly invested in our people and our communities, fostering innovation, leadership, and opportunity at every level. We are more than products, we are a team of inspired people doing extraordinary things.
Responsibilities
- Design, build, and maintain CI/CD pipelines in Azure DevOps (ADO) to automate packaging, validation, and deployment of enterprise platform configurations and customizations while ensuring security is integrated throughout the development lifecycle.
- Own and operate the environment promotion workflow (Dev → Test → Production), enforcing quality gates and release controls at each stage to protect operations stability.
- Develop and maintain automated test and validation frameworks for source code packages prior to deployment, including integration checks against SAP, DataHub (Ignition/SQL), Kafka, and Bartender interfaces.
- Collaborate with application developers and systems analysts to establish branching strategies, pull request workflows, and versioning conventions that support parallel build cycles across multiple workstreams.
- Manage infrastructure-as-code and configuration management for enterprise platforms environments, ensuring environment parity and reproducibility across Dev, Test, and Production tiers.
- Partner with the Architecture team to define and uphold deployment standards, cutover runbooks, and rollback procedures for project go-lives and platform upgrades.
- Support post-deployment monitoring and incident response for the enterprise platforms, diagnosing pipeline failures, deployment anomalies, and environment drift across plant instances.
- Maintain deployment documentation, release notes, and ADO pipeline definitions in alignment with the team's established Way of Working standards.
- Contribute to the ongoing build-out of the team's DevOps maturity, identifying opportunities to reduce manual effort, increase deployment reliability, and shorten lead times from development to production.
- Collaborate with cross-functional teams (development, operations, and security) to design and deploy secure cloud infrastructure and applications on Microsoft Azure.
- Leverage Wiz to continuously monitor, identify, and remediate vulnerabilities across cloud environments, containers, and applications.
- Integrate security tools and practices into CI/CD pipelines, including automated security scans, vulnerability management, and compliance checks to reduce risks.
- Ensure that infrastructure, applications, and data comply with industry standards and security best practices (e.g., GDPR,