Associate Director, Cybersecurity Engineering

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

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

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings — fold minor metadata into short

  or drop it. Preserve all substantive info; do not invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting. Key sections: - Role Summary (maybe "About the role") – we can use

  About the role

  and then paragraph(s) summarizing. - Key Responsibilities – we can have

  Responsibilities

  with subheadings? The posting has categories: Strategy & Governance, Engineering Lead, People Leadership & Collaboration, Product & Delivery Management. Could treat each as subheadings? But we only allowed

  for section headings; we could use

  ? Not allowed? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should stick to

  for main sections. Could embed subheadings as or

  with bold. Simpler: list responsibilities as bullet points. - Education Requirement – could be part of Requirements or Qualifications. We'll have a

  Requirements

  maybe includes Education and Required Skills & Experience. - Required Skills & Experience – list. - Preferred Experience & Skills – list. - Required Skills (list of many) – maybe part of Skills section. - Preferred Skills – list. - Benefits – there is a paragraph about 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." - Pay – salary range: "$142,400.00 - $224,100.00". Also mention annual bonus and long-term incentive. - Schedule – maybe not explicit; there is "Hybrid Shift" under Employee Status? Actually there is "Hybrid Shift" under Employee Status? The posting includes: "Employee Status Regular Relocation: VISA Sponsorship Travel Requirements: Flexible Work Arrangements Hybrid Shift Valid Driving License: Hazardous Material(s)". That seems like schedule info: Hybrid Shift. So we can include Schedule section with that. - Also there is "Job Posting End Date: 10/8/2026" etc. That's metadata; we can fold into short

  maybe. - Also "Requisition ID:R419125" – minor metadata, fold into short

  or drop. - Also "US And Puerto Rico Residents Only" – maybe location requirement; could be part of Requirements? Could be included as a note. - Also "Current Employees apply HERE Current Contingent Workers apply HERE" – application instructions, remove. - Also EEO boilerplate etc – remove. - Also "Search Firm Representatives Please Read Carefully ..." – remove. - Also "San Francisco Residents Only: ..." etc – maybe keep as location-specific note? Might be considered boilerplate but it's specific legal info; but instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is legal but maybe considered EEO? It's about fair chance ordinance. Might be considered legal boilerplate; safer to remove. - Also "We are proud to be a company that embraces the value..." – that's EEO/diversity boilerplate; remove. - Also "The fastest way to breakthrough innovation..." – remove. - Also "Learn more about your rights, including under California, Colorado and other US State Acts" – remove. - Also "As an Equal Employment Opportunity Employer..." – remove. - Also "As a federal contractor..." – remove. - Also "For more information about personal rights under the U.S. Equal Opportunity Employment laws, visit: EEOC Know Your Rights EEOC GINA Supplement" – remove. Thus we keep substantive content: Role Summary, Responsibilities (with subcategories), Education Requirement, Required Skills & Experience, Preferred Experience & Skills, Required Skills list, Preferred Skills list, Benefits, Pay, Schedule (Hybrid Shift), maybe location restriction (US and Puerto Rico Residents Only) as a note. We must not repeat job title as heading. So no

  Privileged Access Management (PAM) Team Lead (R4 - Associate Director)

  . We need to output only HTML fragment. Let's structure:

  About the role

  ... role summary ...

  Responsibilities

  • Strategy & Governance: Own and execute the enterprise PAM roadmap aligned with our company's cybersecurity strategy, Zero Trust objectives, and identity security initiatives. Define and maintain PAM standards and governance practices in partnership with security, risk, and architecture teams. Develop and present PAM posture, risk metrics, and remediation plans to leadership, governance, and audit stakeholders. Partner across teams to prioritize PAM adoption, expand privileged access controls and remediate risk.
  • Engineering Lead: Lead the design and delivery of enterprise PAM and secrets management capabilities. Modernize privileged access through risk-based, least-privilege, and just-in-time access models. Translate PAM strategy into scalable designs, standards, and patterns across all environments. Lead evaluations of new PAM technologies based on need, risk, architectural fit, and cost. Oversee remediation of PAM vulnerabilities, control gaps, audit findings, and technical debt.
  • People Leadership & Collaboration: Lead daily PAM engineering activities, drive execution, remove delivery barriers, and develop team capabilities. Promote Agile ways of working and continuous improvement. Mentor and influence the team’s personal and professional development.
  • Product & Delivery Management: Partner with the IAM Product Owner to manage the backlog aligned with OKRs and team capacity. Be accountable for the health, stability, and continuous improvement of PAM services. Partner with stakeholders to ensure capabilities meet business and security needs while reducing risk.

  Requirements

  Education: Bachelor’s degree (or equivalent experience), preferably in Computer Science, Information Systems, or a related field.

  Experience: 10+ years of experience in cybersecurity or Identity and Access Management (IAM), including at least 7 years focused on Privileged Access Management (PAM). Experience leading and developing security engineering teams within a large, global organization.

  Skills

  Required Skills & Experience:

  • Strong understanding of enterprise PAM and secrets management platforms (e.g., Delinea, CyberArk, BeyondTrust, and/or HashiCorp Vault).
  • Hands-on knowledge of PAM solutions supporting Windows, UNIX/Linux, and databases.
  • Experience delivering solutions using Agile methodologies and collaborating with Product Owners using tools such as Jira.
  • Excellent communication skills, with the ability to effectively translate complex technical concepts, risks, and recommendations for technical and non-technical stakeholders.

  Preferred Experience & Skills:

  • Hands-on experience with identity platforms such as Active Directory, Microsoft Entra ID, cloud identity services, and/or HashiCorp Vault.
  • Hands-on knowledge of PAM solutions operating in multi-cloud environments (AWS, Azure, and GCP) and Kubernetes platforms.
  • Familiarity with ServiceNow for incident and change management processes.
  • Experience automating administrative and operational tasks using PowerShell or similar technologies.
  • Strong understanding of cybersecurity fundamentals, secure SDLC practices, Zero Trust principles, and cloud-native security controls.
  • Knowledge of industry standards and frameworks such as NIST, ITIL, and modern identity security practices.
  • Experience working in healthcare, life sciences, or other highly regulated industries.
  • Industry-recognized certifications such as CISSP, Security+, or comparable credentials.

  Required Skills (list):

  • Application Security
  • Cloud Security
  • Cybersecurity Operations
  • Data Protection
  • Delivery of Security Applications
  • Design Applications
  • DevOps Coaching
  • Influence
  • Information Security
  • SLA Management
  • System Designs
  • Technical Advice
  • Zero Trust Identity

  Preferred Skills:

  • (list from posting? Actually the posting had "Preferred Skills" then list: Current Employees apply HERE etc. That seems not a list. The "Preferred Skills" section earlier had list of items? Actually after "Preferred Experience & Skills" there is a block: "Required Skills Application Security, Cloud Security, Cybersecurity Operations, Data Protection, Delivery of Security Applications, Design Applications, DevOps Coaching, Influence, Information Security, SLA Management, System Designs, Technical Advice, Zero Trust Identity". Then "Preferred Skills Current Employees apply HERE Current Contingent Workers apply HERE". That seems misformatted. The "Preferred Skills" line is followed by "Current Employees apply HERE Current Contingent Workers apply HERE". That's not a list of skills; it's application instructions. So we should not include that as skills. So we can omit Preferred Skills section unless there is actual list. There is no list after that. So we skip. Thus we have Skills section covering required skills list. Now Benefits:

    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.

    Pay:

    Pay

    The salary range for this role is $142,400.00 - $224,100.00. This is the lowest to highest salary we in good faith believe we would pay for this role at the time of this posting. An employee’s position within the salary range will be based on several factors including, but not limited to relevant education, qualifications, certifications, experience, skills, geographic location, government requirements, and business or organizational needs. The successful candidate will be eligible for annual bonus and long-term incentive, if applicable.

    Schedule:

    Schedule

    Hybrid Shift (flexible work arrangements).

    We might also include location restriction