DevOps & Security Engineer

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. We must include sections only if posting has real specific content. We need to parse the posting. The posting includes: - Intro paragraph about company (About the role? Actually "About the role" maybe not; but we have description of company and culture. Could be "About the role" or maybe "About the company". The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those headings if content matches. We have: - "What You'll Be Doing" -> Responsibilities. - "What You Should Have" -> Requirements/Qualifications/Skills. Might split into Requirements (education, experience) and Skills (technical). But we can combine. - "Compensation & Benefits" -> Benefits and Pay. - There's also "Physical Requirements" but that's likely boilerplate? It's not in list of allowed headings; we should remove boilerplate like Physical Requirements, EEO, Accommodations, Recruiting Fraud Alert, etc. So we drop those. - Also "SPECIAL NOTATION" etc. Remove. Thus we need sections: - About the role? Could use the introductory paragraph about company and culture as "About the role". Might be appropriate. - Responsibilities: the bullet list under "What You'll Be Doing". We need to convert each sentence into

items inside

. Should we keep each sentence as separate list item? Probably yes. - Requirements: education and experience requirements under "What You Should Have". Could be split into Requirements (education, years) and Skills (technical). But we can combine into Requirements and maybe Skills. But instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have multiple of those. We need to decide which sections have content. We have content for: - About the role: company description. - Responsibilities: list of duties. - Requirements: education and experience (4-year degree, 4-6 years DevOps, etc.) - Skills: technical proficiencies (Azure DevOps, scripting, etc.) plus preferred experience. - Benefits: description of benefits package. - Pay: starting base pay range. - Schedule: not mentioned; we should not create Schedule section. Thus we will output sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay. We must not include empty sections. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from those sections. We must not repeat job title. We must not include boilerplate like EEO etc. We need to format as HTML fragment: use

for each heading, then content:

for prose,

• for lists. We need to decide how to split content. About the role: The introductory 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." That's prose; we can put in

  . Responsibilities: The bullet list under "What You'll Be Doing". Each sentence seems a duty. Let's extract each sentence: - 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; we will list each as

• . Requirements: Education and experience required. From "What You Should Have": - 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. We could also include "Proven expertise with Azure DevOps (ADO), including YAML pipeline authoring, release pipelines, environment management, and test plan integration required." That's more skill but could be under Skills. However it's listed under "What You Should Have" as required. We could treat as Requirements (maybe split). But we have separate Skills section for technical proficiencies. Let's decide: Requirements: education and years of experience. Skills: specific tools and technologies. Thus Requirements
  with two items. Skills: list of required and preferred technical proficiencies. From "What You Should Have" after the first two bullets: - 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 could also include some from Responsibilities that are skills but we already captured them as duties; but we can keep them under Skills as well if they appear there. However to avoid duplication, we might keep Skills as the list above. We need to preserve all substantive information; we must not omit any of those. So we will include each as
  • . Benefits: The paragraph under "Compensation & Benefits". It says: "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 to separate Pay and Benefits. The instruction: include Pay and Benefits sections only if posting actually states them. The posting includes pay range and benefits description. So we should split: Pay section: the starting base pay range sentence. Benefits section: the rest about comprehensive benefits package and list of offerings. Thus: 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:

    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 SupportFinancial SecurityLearning & DevelopmentRewards & RecognitionWellbeing & Mental HealthWork-LifeBalanceFun Perks

    But note the benefits paragraph includes mention of competitive pay; we already extracted pay sentence; we might want to avoid duplication. However the benefits paragraph includes "competitive pay along with a comprehensive benefits package". If we remove that sentence, we might lose mention of competitive pay. But we already have Pay section with the range; we could keep benefits paragraph without the pay mention. However the instruction says preserve ALL substantive information; we should not omit any detail. If we remove the phrase "competitive pay" from benefits, we are omitting that detail (though it's covered in Pay section). But we could keep it in benefits as well; duplication is okay? The instruction didn't forbid duplication, but said preserve all substantive information; duplication is not losing info. However we should avoid unnecessary duplication? Not explicitly forbidden. Safer to keep the benefits paragraph as is, and also have Pay section with the range. That duplicates the mention of competitive pay but retains all info. Thus 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 SupportFinancial SecurityLearning & DevelopmentRewards & RecognitionWellbeing & Mental HealthWork-LifeBalanceFun Perks

    Now About the role: we have the intro paragraph. Now we need to output HTML fragment only, no or . We'll output sequence of sections. Let's craft:

    About the role