Senior Specialist, Cybersecurity Engineering

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: - Role Summary (maybe About the role) - What You'll Do (Responsibilities) - Required Qualifications (Qualifications) - Preferred Qualifications (maybe also Qualifications or Skills) - Required Skills (list) - Preferred Skills (list) - Salary range (Pay) - Benefits (Benefits) - Possibly other metadata like relocation, visa, etc. But we should not include minor metadata like Job ID, requisition numbers, application instructions, EEO boilerplate, etc. Also we should not include sections like "Schedule" if not present. There's no explicit schedule info. There's "Hybrid Shift" maybe? Actually there is "Hybrid Shift" under Employee Status? It says "Hybrid Shift". That could be schedule. But it's ambiguous. The posting includes "Hybrid Shift" maybe indicating hybrid work schedule. Could include Schedule section if we have content: "Hybrid Shift". However the instruction: "Prefer a few substantive sections over many thin ones." Might combine schedule into Benefits? Better to include Schedule only if there is real specific content. There's "Hybrid Shift" which is a schedule detail. Could include Schedule heading with that. Also "Relocation: VISA Sponsorship" maybe not needed. We must not repeat job title as heading. So no heading for the title. We need to use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. Remove boilerplate. Thus we need to extract: - About the role: The Role Summary paragraph: "Join our IT Risk Management & Security team and play a key role in protecting a global enterprise’s most critical systems, accounts, and secrets. As a Privileged Access & Secrets Management Engineer, you will design, deploy, and operate HashiCorp Vault and privileged access capabilities that reduce cyber risk and enable secure, automated secrets delivery. This role offers the opportunity to help shape enterprise privileged access and secrets management capabilities while working across identity, automation, cloud, infrastructure, and application teams." That's prose. - Responsibilities: "What You'll Do" bullet list items (they are sentences separated by periods). We need to convert to

  • . The list: Design, implement, and support HashiCorp Vault in on-premises environments. Develop reusable patterns, standards, and onboarding guidance for HashiCorp Vault and secrets management across application, infrastructure, and automation teams. Support HashiCorp Vault integrations with CI/CD platforms, deployment pipelines, automation workflows, and application delivery processes. Enable secure injection, retrieval, rotation, and lifecycle management of secrets used by build, release, and runtime environments. Integrate PAM with enterprise applications, infrastructure and cloud platforms, and APIs. Troubleshoot complex technical issues and support production operations. Develop automation, standards, and operational processes that improve security, efficiency, and improve audit readiness. We'll put each as
  • . - Qualifications: Required Qualifications (maybe heading "Required Qualifications" or just "Qualifications"). The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, etc. So we can have

    Qualifications

    and include both required and preferred? But they said prefer few substantive sections over many thin ones. Could combine required and preferred into Qualifications section with sublists? But we need to preserve all info. Could have Required Qualifications and Preferred Qualifications as separate subheadings? But only allowed headings are those listed; we could use

    Qualifications

    and then inside have

    for required qualifications prose and

    for preferred? However required qualifications are a list of items (bulleted). Preferred qualifications also a list. We could do two
    under same heading with preceding

    indicating required vs preferred. That's acceptable. But the instruction: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have Qualifications heading and inside we can have two lists with headings? Not allowed to add extra headings beyond those? It didn't forbid inner headings, but better to keep simple: maybe separate sections: Required Qualifications and Preferred Qualifications both under Qualifications? Could also have Skills section for required skills and preferred skills. Let's parse: Required Qualifications list: - Bachelor’s degree (or equivalent experience), preferably in Computer Science, Information Systems, or a related field. - 5+ years of experience designing, deploying, and supporting HashiCorp Vault in on-premises environments, including integrations with CI/CD tools, automation frameworks, APIs, and application deployment workflows. - Strong understanding of secrets lifecycle management including dynamic secrets, secrets engines, and auth methods for service accounts, workloads, applications, and non-human identities. - Practical knowledge of privileged account management techniques: vaulting, password rotation, secrets management, least-privilege access, and service account security. - Experience integrating security platforms with Windows, Linux/Unix, databases, cloud services, applications, and APIs. - Ability to manage multiple priorities, adapt to change, and work effectively within large, global, matrixed organizations. - Strong analytical, troubleshooting, problem-solving, and communication skills, with the ability to collaborate effectively across global teams and explain technical concepts to varied technical and non-technical audiences. Preferred Qualifications list: - Experience with CI/CD platforms such as GitHub Actions, GitLab CI, Jenkins, Azure DevOps, or similar tools. - Experience with infrastructure-as-code and automation tools such as Terraform, Ansible, PowerShell, Python, or similar technologies. - Hands-on experience with identity platforms such as Active Directory and Microsoft Entra ID, cloud identity management, etc. - Familiarity with ServiceNow for change and incident management and experience automating tasks with PowerShell or similar technologies. - Familiarity with NIST, ITIL, or related security frameworks. - Relevant certifications such as CISSP, Security+, or similar credentials. - Experience in healthcare, life sciences, or other highly regulated industries. - Knowledge of Zero Trust principles, cloud security, and modern identity security practices. Required Skills list (looks like a long list of keywords). It says "Required Skills Access Management Software, Access Management Software, Azure Active Directory (AD), Certificate Services, Cloud Security, Cybersecurity, Cybersecurity Analytics, Cybersecurity Operations, Delivery of Security Applications, Design Applications, HashiCorp Vault, Identity Access Management (IAM), Incident Response, Information Assurance, Information Security, IT Security Architecture, Linux, Network Segmentation, Operational Technology (OT) Security, Red Hat Ansible, Security Analysis, Security Analytics, Security Controls, Security Evaluations, Security Fundamentals {+ 9 more}". That's a list; we can turn into

    • each item. The duplicate "Access Management Software" appears twice; we can keep once? But we should preserve all substantive information; duplicate maybe not substantive; but we could keep as is. Might be okay to deduplicate but not required. We'll keep unique. Preferred Skills list: "Current Employees apply HERE Current Contingent Workers apply HERE US And Puerto Rico Residents Only Our company is committed to inclusion, ensuring that candidates can engage in a hiring process that exhibits their true capabilities. Please click here if you need an accommodation during the application or hiring process." That's not skills; it's application instructions. Actually the "Preferred Skills" heading appears earlier: after Preferred Qualifications there is "Required Skills ..." then "Preferred Skills Current Employees apply HERE Current Contingent Workers apply HERE US And Puerto Rico Residents Only ..." That seems garbled. The text after "Preferred Skills" includes application instructions and EEO etc. We need to strip boilerplate. So we should ignore that. Thus we have: - Pay: salary range "$117,000.00 - $184,200.00" plus description about salary determination, bonus, long-term incentive. That's substantive. We'll put under Pay heading. - Benefits: "We offer a comprehensive package of benefits. Available benefits include medical, dental, vision healthcare and other insurance benefits (for employee and family), retirement benefits, including 401(k), paid holidays, vacation, and compassionate and sick days. More information about benefits is available at https://jobs.merck.com/us/en/compensation-and-benefits." That's substantive. - Schedule: maybe "Hybrid Shift" under Employee Status. Also "Relocation: VISA Sponsorship Travel Requirements: Flexible Work Arrangements Hybrid Shift". Could interpret schedule as Hybrid Shift (hybrid work). We'll include Schedule heading with "Hybrid Shift". Also maybe "Flexible Work Arrangements". We'll combine. We must not include minor metadata like Job ID, requisition numbers, application instructions, EEO boilerplate, etc. Thus final HTML:

      About the role

      Join our IT Risk Management & Security team and play a key role in protecting a global enterprise’s most critical systems, accounts, and secrets. As a Privileged Access & Secrets Management Engineer, you will design, deploy, and operate HashiCorp Vault and privileged access capabilities that reduce cyber risk and enable secure, automated secrets delivery. This role offers the opportunity to help shape enterprise privileged access and secrets management capabilities while working across identity, automation, cloud, infrastructure, and application teams.

      Responsibilities

      • Design, implement, and support HashiCorp Vault in on-premises environments.
      • Develop reusable patterns, standards, and onboarding guidance for HashiCorp Vault and secrets management across application, infrastructure, and automation teams.
      • Support HashiCorp Vault integrations with CI/CD platforms, deployment pipelines, automation workflows, and application delivery processes.
      • Enable secure injection, retrieval, rotation, and lifecycle management of secrets used by build, release, and runtime environments.
      • Integrate PAM with enterprise applications, infrastructure and cloud platforms, and APIs.
      • Troubleshoot complex technical issues and support production operations.
      • Develop automation, standards, and operational processes that improve security, efficiency, and improve audit readiness.

      Qualifications

      Required Qualifications:

      • Bachelor’s degree (or equivalent experience), preferably in Computer Science, Information Systems, or a related field.
      • 5+ years of experience designing, deploying, and supporting HashiCorp Vault in on-premises environments, including integrations with CI/CD tools, automation frameworks, APIs, and application deployment workflows.
      • Strong understanding of secrets lifecycle management including dynamic secrets, secrets engines, and auth methods for service accounts, workloads, applications, and non-human identities.
      • Practical knowledge of privileged account management techniques: vaulting, password rotation, secrets management, least-privilege access, and service account security.
      • Experience integrating security platforms with Windows, Linux/Unix, databases, cloud services, applications, and APIs.
      • Ability to manage multiple priorities, adapt to change, and work effectively within large, global, matrixed organizations.
      • Strong analytical, troubleshooting, problem-solving, and communication skills, with the ability to collaborate effectively across global teams and explain technical concepts to varied technical and non-technical audiences.

      Preferred Qualifications:

      • Experience with CI/CD platforms such as GitHub Actions, GitLab CI, Jenkins, Azure DevOps, or similar tools.
      • Experience with infrastructure-as-code and automation tools such as Terraform, Ansible, PowerShell, Python, or similar technologies.
      • Hands-on experience with identity platforms such as Active Directory and Microsoft Entra ID, cloud identity management, etc.