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 need to include only sections that have real specific content. The posting includes: introductory paragraph about company (maybe "About the role"? Actually it's about company). Then "What You'll Be Doing" is responsibilities. Then "What You Should Have" includes requirements/qualifications/skills. Then "Compensation & Benefits" includes pay and benefits. Also there are sections like "Physical Requirements", "EEO STATEMENT", etc which we must remove as boilerplate. Also "SPECIAL NOTATION", "ACCOMMODATIONS REQUEST", "RECRUITING FRAUD ALERT", etc. Remove those. We need to preserve all substantive information. So we need to extract: - About the role? The first paragraph: "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 about the company, could be "About the role" or "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 "About the role" heading for that intro. - Responsibilities: "What You'll Be Doing" list of bullet points (each sentence). Need to put each as

inside

. Should we keep as prose? It says use
• for any list of duties/requirements/benefits. So we need to convert each duty into list items. - Requirements/Qualifications/Skills: "What You Should Have" includes many items: degree, years experience, expertise with ADO, etc. Some are required, some preferred. We need to keep all substantive info. We could split into Requirements (required) and Skills (preferred) or Qualifications. The instruction says prefer a few substantive sections over many thin ones. Could combine Requirements and Qualifications into one section? But we have headings list: Requirements, Qualifications, Skills. We need to decide which to use based on content. The posting includes both required and preferred items. Could make a "Requirements" section for required items, and a "Skills" section for preferred/experience items. Or combine into "Qualifications". Let's see: The posting says "What You Should Have" then bullet list with required and preferred. We could split: Required items: degree, 4-6 years experience, proven expertise with ADO, experience managing environment promotion workflows, proficiency in scripting languages, working knowledge of Windows/Linux, experience with version control systems, familiarity with enterprise application integration patterns (preferred), experience with ERP, MES, SCADA (plus), experience with ERP, MES enterprise platforms preferred, OpenShift/Redhat experience preferred, experience with IaC tools preferred, experience with containerization preferred. That's a mix. We could have a "Requirements" section for required items (degree, years, ADO expertise, environment promotion workflow, scripting languages, Windows/Linux, version control). Then a "Skills" section for preferred items (familiarity with ERP/MES/SCADA, OpenShift/Redhat, IaC, containerization). Also maybe "Qualifications" could be used for degree and experience. But we need to avoid thin sections. Perhaps combine required and preferred into one "Qualifications" section, but then we lose distinction. However instruction says prefer a few substantive sections over many thin ones. So maybe we have three sections: About the role, Responsibilities, Qualifications (which includes both required and preferred), and Benefits & Pay (combined). That seems reasonable. But we also have Pay and Benefits separate headings possible. The posting includes compensation & benefits paragraph with pay range and benefits description. We could make a "Pay" section with the pay range, and a "Benefits" section with the benefits list. However the instruction says only include a section when posting has real specific content for it. It does have pay range and benefits description. So we could have both Pay and Benefits sections. But we could also combine them into "Compensation & Benefits". However the allowed headings list includes Benefits, Pay, Schedule. So we could use both Pay and Benefits. That would be two sections, each with content. That's fine. Schedule: no info about schedule, so omit. Thus final sections: About the role (

  About the role

  ), Responsibilities (

  Responsibilities

  ), Qualifications (

  Qualifications

  ), Pay (

  Pay

  ), Benefits (

  Benefits

  ). We need to ensure we don't repeat job title as heading. Not needed. We need to strip boilerplate: remove SPECIAL NOTATION, Physical Requirements, EEO STATEMENT, ACCOMMODATIONS REQUEST, RECRUITING FRAUD ALERT, etc. Also remove duplicated lines: there is duplicate "Experience with ERP, MES enterprise platforms preferred." appears twice? Actually appears: "Experience with ERP, MES enterprise platforms preferred." and later "Experience with ERP, MES enterprise platforms preferred." Might be duplicate; we should keep only one instance. 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." and later "Experience with ERP, MES enterprise platforms preferred." We'll keep both but avoid duplication. Now craft HTML. We need to wrap each section:

  Heading

  then either

  for prose or

  • for lists. For About the role: it's prose (multiple sentences). We'll put in

    . For Responsibilities: list each duty. We'll extract each sentence from "What You'll Be Doing". Let's list them: - 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'll put each as

  • . For Qualifications: we need to list required and preferred items. Could use
    • for each. We'll separate required vs preferred? Could just list all items as bullet points. But we might want to separate required and preferred for clarity. However instruction says prefer few sections; we already have Qualifications section. Inside we could have two sub-lists? Not required to have headings inside. We could just list all items. But we need to preserve all substantive info; we can include notes like "(required)" or "(preferred)". That's fine. Let's extract items 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. - 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. Note duplicate "Experience with ERP, MES enterprise platforms preferred." appears twice? Actually we have one line: "Experience with ERP, MES enterprise platforms preferred." and later "Experience with ERP, MES enterprise platforms preferred." Might be duplicate; we keep one. 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." That's similar to the preferred line but we keep both. Now Pay: The posting says: "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'll put that in

      under Pay heading. Benefits: The posting says: "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". Actually the text: "With best-in-class benefits, you can