DevOps & Security Engineer

We need to output HTML fragment with sections: About the role? Actually the posting includes an intro paragraph about company, then "What You'll Be Doing" (responsibilities), then "What You Should Have" (requirements/qualifications), then "Compensation & Benefits". Also there are sections like "Physical Requirements", "EEO STATEMENT", etc which we must remove as boilerplate. Also "SPECIAL NOTATION" etc. Remove all boilerplate. We need to use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should decide which sections to include based on content. We have: - Intro paragraph about company: could be "About the role" or maybe "About the company"? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" for the introductory description. - Responsibilities: "What You'll Be Doing" list of duties. - Requirements/Qualifications/Skills: "What You Should Have" includes education, experience, required skills, preferred skills. We can split into Requirements (required) and Qualifications/Skills (preferred). But we can combine into one section "Requirements" maybe. However we have to avoid thin sections. We could have "Requirements" for required items, and "Preferred Qualifications" maybe but not in list. The instruction says we can use headings like Requirements, Qualifications, Skills. We could have "Requirements" for required, and "Skills" for preferred? Or "Qualifications" for required and "Skills" for preferred. Let's decide: Use "Requirements" for required (education, years experience, expertise with ADO, etc). Use "Skills" for preferred (familiarity with ERP, MES, SCADA, OpenShift, IaC, containerization). Also maybe "Qualifications" could be used for education? But we can keep simple: "Requirements" for required, "Preferred Skills" maybe not allowed heading? The allowed headings list includes Skills, Qualifications, Requirements. So we can have "Requirements" for required, and "Skills" for preferred. Or we could have "Qualifications" for required and "Skills" for preferred. Let's do:

Requirements

for required items (education, experience, ADO, scripting, etc).

Skills

for preferred items (ERP/MES/SCADA, OpenShift, IaC, containerization). That seems fine. - Compensation & Benefits: we have pay range and benefits description. So we can have

Pay

for pay range, and

Benefits

for benefits description. Or combine into one "Compensation & Benefits" but not in allowed list. We'll split. - Schedule: not mentioned, so omit. We must not repeat job title as heading. No Job ID. We must preserve all substantive information. So we need to include all responsibilities bullet points, all requirements bullet points, all preferred skills bullet points, pay range, benefits description (including list of perk categories). Also include the introductory paragraph about company (the first paragraph). Also maybe include the sentence "Ready to join a global leader..." etc. That's substantive. We must remove boilerplate: SPECIAL NOTATION, Physical Requirements, EEO STATEMENT, ACCOMMODATIONS REQUEST, RECRUITING FRAUD ALERT, and the final motivational sentence? Actually the final sentence: "If you're looking for a place to grow while working with happy, enthusiastic, values-based people, you'll enjoy your career with us!" That's maybe not boilerplate but could be considered fluff; but it's part of posting. It's not explicitly listed as boilerplate to remove, but it's kind of a closing marketing line. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. That final sentence is not legal; it's more of a tagline. I'd keep it as part of About the role maybe. We need to output only HTML fragment, no /, no markdown fences. We'll structure:

About the role

Intro paragraph(s).

Responsibilities

• ...
...

Requirements

• ...
...

Skills

• ...
...

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 Support, Financial Security, Learning & Development, Rewards & Recognition, Wellbeing & Mental Health, Work-Life Balance, Fun Perks.

We need to ensure we preserve all substantive info from responsibilities list. Let's extract responsibilities from "What You'll Be Doing". It's a long paragraph with many sentences separated by periods. We need to turn each duty into a

. Let's parse: - 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 16 items. Now requirements list from "What You Should Have". 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. - 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. (This is preferred, not required) - 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. (Preferred) - Experience with infrastructure-as-code tools (Terraform, Ansible, or Azure Resource Manager templates) for environment provisioning preferred. (Preferred) - Experience with containerization (Docker, Kubernetes) for supporting application services adjacent to the ERP / MES platform preferred. (Preferred) Thus required items: first 7 bullet points (degree, 4-6 years, ADO expertise, environment promotion workflow, scripting proficiency, Windows/Linux knowledge, version control/branching). Also maybe "Experience with version control systems and branching strategies that support multiple concurrent development streams required." That's included. We'll put those in Requirements

. Preferred skills: we can list all the preferred items as Skills. Let's list them: - 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 "Experience with ERP, MES enterprise platforms preferred." which is similar to earlier. We'll keep them as separate
• . Now benefits: we need to include the sentence about competitive pay and comprehensive benefits package, plus the list of perk categories. The original: "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". Actually the original had no spaces between categories: "Health & Family SupportFinancial SecurityLearning & DevelopmentRewards & RecognitionWellbeing & Mental HealthWork-Life BalanceFun Perks". We need to preserve the info but we can format with commas for readability? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Changing punctuation might be okay as long as we don't lose info. Adding commas is not inventing content, just formatting. Safer to keep as original string but we