DevOps & Security Engineer
Greenheck Group · Minnesota, United States · 3 wk ago
Information Technology$117k–$145k/yrFull-time
We need to output HTML fragment only, with headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list. Use
for prose. Do not repeat job title as heading. Do not include Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Keep substantive info.
We need to parse the posting.
First paragraph: "Ready to join a global leader..." This is about the company, could be "About the role"? Actually "About the role" is typical heading for description of role/company. We'll put that as
About the role
and then a with that prose.
Then "What You'll Be Doing" is responsibilities. So
Responsibilities
with a - for each bullet.
Then "What You Should Have" is requirements/qualifications. Could split into Requirements and Qualifications? The instruction says we can have sections for Requirements, Qualifications, Skills. We need to decide based on content. The "What You Should Have" includes degree, years experience, expertise with ADO, etc. That's qualifications/requirements. Could treat as Requirements. Also there is a list of preferred experiences etc. Could be Skills. But we need to avoid thin sections. Perhaps combine into one Requirements section with both required and preferred? But we need to follow instruction: include a section ONLY when posting has real, specific content for it. We have content for Requirements (required). Also we have content for Skills (technical skills). Could separate: Requirements (education, years experience) and Skills (specific tools/languages). Also Benefits and Pay sections exist: "Compensation & Benefits" includes pay range and benefits description. So we need Pay and Benefits sections. Schedule? Not mentioned. So we should not include Schedule heading.
Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay.
We need to ensure we don't include filler like "commensurate with experience". Not present.
Now extract content.
About the role: The first paragraph up to "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."
That's the About the role.
Responsibilities: bullet list under "What You'll Be Doing". Let's list each sentence as a bullet.
- 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 all.
Now Requirements: The "What You Should Have" starts with degree and years experience etc. Let's extract required items:
- 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.
These are required. Also there is "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." That's preferred, could go to Skills.
Also "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." Preferred.
"Experience with ERP, MES enterprise platforms preferred." 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."
Thus we can split: Requirements = required items. Skills = preferred/experience items (including tools, platforms). Could also include "Proficiency in scripting languages" already in requirements; but that's fine.
Now Benefits: The "Compensation & Benefits" paragraph includes: "Greenheck Group takes pride in providing competitive pay along with a comprehensive benefits package as part of our total rewards program. 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. With best-in-class benefits, you can be the best you, and together, we can be the best in the industry. Visit our Perks & Benefits page for more information on these offerings: Health & Family SupportFinancial SecurityLearning & DevelopmentRewards & RecognitionWellbeing & Mental HealthWork-LifeBalanceFun Perks"
We need Benefits section: list of benefits items. The text after colon: "Health & Family SupportFinancial SecurityLearning & DevelopmentRewards & RecognitionWellbeing & Mental HealthWork-Life BalanceFun Perks". It seems missing spaces. We can split into list items: Health & Family Support, Financial Security, Learning & Development, Rewards & Recognition, Wellbeing & Mental Health, Work-Life Balance, Fun Perks.
Pay section: The pay range: "$117,249-$144,837". Also note that it may vary based on factors. We'll put that in Pay section as a
.
We should not include "Visit our Perks & Benefits page for more information on these offerings:" as it's application instruction? It's a reference; but we can keep as part of Benefits prose? Probably we can keep as a
before list.
Now ensure we don't include boilerplate: EEO statement, accommodations, recruiting fraud alert, special notation, physical requirements, etc. Remove those.
Now produce HTML:
About the role
...
Responsibilities
- ...
...
Requirements
- ...
...
Skills
- ...
...
Benefits
Greenheck Group takes pride in providing competitive pay along with a comprehensive benefits package as part of our total rewards program. With best-in-class benefits, you can be the best you, and together, we can be the best in the industry. Visit our Perks & Benefits page for more information on these offerings:
- Health & Family Support
- Financial Security
- Learning & Development
- Rewards & Recognition
- Wellbeing & Mental Health
- Work-Life Balance
- Fun Perks
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.
We should not include Schedule.
Check for any duplicated lines: ensure we didn't include any boilerplate like "SPECIAL NOTATION". Not included.
Now ensure we didn't miss any substantive info: The "What You Should Have" also includes "Experience with ERP, MES enterprise platforms preferred." Already captured in Skills. Also "OpenShift / Redhat experience preferred." etc.
Also "Experience with infrastructure-as-code tools (Terraform, Ansible, or Azure Resource Manager templates) for environment provisioning preferred." captured.
Also "Experience with containerization (Docker, Kubernetes) for supporting application services adjacent to the ERP / MES platform preferred." captured.
Also "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." captured.
Also "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." captured.
Now ensure we didn't include any "required" vs "preferred" duplication. In Requirements we included required items only. In Skills we included preferred items.
Check that we didn't miss any required items: "Working knowledge of Windows and Linux Server environments." included. "Experience with version control systems and branching strategies that support multiple concurrent development streams required." included.
Now check that we didn't include any "required" phrase inside Skills inadvertently. We'll avoid.
Now produce final HTML.
Be careful to escape any HTML special characters like & in "Health & Family Support". Should we keep as is? In HTML, & is okay if part of text but better to escape as &. However the instruction didn't mention escaping; but to be safe we can keep as is; but it's technically invalid if not escaped. Usually we should
for prose. Do not repeat job title as heading. Do not include Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Keep substantive info. We need to parse the posting. First paragraph: "Ready to join a global leader..." This is about the company, could be "About the role"? Actually "About the role" is typical heading for description of role/company. We'll put that as
About the role
and then awith that prose. Then "What You'll Be Doing" is responsibilities. So
Responsibilities
with a- for each bullet.
Then "What You Should Have" is requirements/qualifications. Could split into Requirements and Qualifications? The instruction says we can have sections for Requirements, Qualifications, Skills. We need to decide based on content. The "What You Should Have" includes degree, years experience, expertise with ADO, etc. That's qualifications/requirements. Could treat as Requirements. Also there is a list of preferred experiences etc. Could be Skills. But we need to avoid thin sections. Perhaps combine into one Requirements section with both required and preferred? But we need to follow instruction: include a section ONLY when posting has real, specific content for it. We have content for Requirements (required). Also we have content for Skills (technical skills). Could separate: Requirements (education, years experience) and Skills (specific tools/languages). Also Benefits and Pay sections exist: "Compensation & Benefits" includes pay range and benefits description. So we need Pay and Benefits sections. Schedule? Not mentioned. So we should not include Schedule heading.
Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay.
We need to ensure we don't include filler like "commensurate with experience". Not present.
Now extract content.
About the role: The first paragraph up to "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."
That's the About the role.
Responsibilities: bullet list under "What You'll Be Doing". Let's list each sentence as a bullet.
- 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 all.
Now Requirements: The "What You Should Have" starts with degree and years experience etc. Let's extract required items:
- 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.
These are required. Also there is "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." That's preferred, could go to Skills.
Also "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." Preferred.
"Experience with ERP, MES enterprise platforms preferred." 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."
Thus we can split: Requirements = required items. Skills = preferred/experience items (including tools, platforms). Could also include "Proficiency in scripting languages" already in requirements; but that's fine.
Now Benefits: The "Compensation & Benefits" paragraph includes: "Greenheck Group takes pride in providing competitive pay along with a comprehensive benefits package as part of our total rewards program. 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. With best-in-class benefits, you can be the best you, and together, we can be the best in the industry. Visit our Perks & Benefits page for more information on these offerings: Health & Family SupportFinancial SecurityLearning & DevelopmentRewards & RecognitionWellbeing & Mental HealthWork-LifeBalanceFun Perks"
We need Benefits section: list of benefits items. The text after colon: "Health & Family SupportFinancial SecurityLearning & DevelopmentRewards & RecognitionWellbeing & Mental HealthWork-Life BalanceFun Perks". It seems missing spaces. We can split into list items: Health & Family Support, Financial Security, Learning & Development, Rewards & Recognition, Wellbeing & Mental Health, Work-Life Balance, Fun Perks.
Pay section: The pay range: "$117,249-$144,837". Also note that it may vary based on factors. We'll put that in Pay section as a
. We should not include "Visit our Perks & Benefits page for more information on these offerings:" as it's application instruction? It's a reference; but we can keep as part of Benefits prose? Probably we can keep as a
before list. Now ensure we don't include boilerplate: EEO statement, accommodations, recruiting fraud alert, special notation, physical requirements, etc. Remove those. Now produce HTML:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Skills
- ... ...
Benefits
Greenheck Group takes pride in providing competitive pay along with a comprehensive benefits package as part of our total rewards program. With best-in-class benefits, you can be the best you, and together, we can be the best in the industry. Visit our Perks & Benefits page for more information on these offerings:
- Health & Family Support
- Financial Security
- Learning & Development
- Rewards & Recognition
- Wellbeing & Mental Health
- Work-Life Balance
- Fun Perks
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.
We should not include Schedule. Check for any duplicated lines: ensure we didn't include any boilerplate like "SPECIAL NOTATION". Not included. Now ensure we didn't miss any substantive info: The "What You Should Have" also includes "Experience with ERP, MES enterprise platforms preferred." Already captured in Skills. Also "OpenShift / Redhat experience preferred." etc. Also "Experience with infrastructure-as-code tools (Terraform, Ansible, or Azure Resource Manager templates) for environment provisioning preferred." captured. Also "Experience with containerization (Docker, Kubernetes) for supporting application services adjacent to the ERP / MES platform preferred." captured. Also "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." captured. Also "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." captured. Now ensure we didn't include any "required" vs "preferred" duplication. In Requirements we included required items only. In Skills we included preferred items. Check that we didn't miss any required items: "Working knowledge of Windows and Linux Server environments." included. "Experience with version control systems and branching strategies that support multiple concurrent development streams required." included. Now check that we didn't include any "required" phrase inside Skills inadvertently. We'll avoid. Now produce final HTML. Be careful to escape any HTML special characters like & in "Health & Family Support". Should we keep as is? In HTML, & is okay if part of text but better to escape as &. However the instruction didn't mention escaping; but to be safe we can keep as is; but it's technically invalid if not escaped. Usually we should