Senior Manager, Cybersecurity, AI SOC & Crisis Management - Remote

We need to output HTML fragment with sections: About the role? The posting includes description: "Preference will be given to candidates residing in the Eastern or Central time zones. As a Senior Manager, AI Security Operations & Crisis Management, you will lead the enterprise Cyber Incident Response Team (CIRT) and coordinate incidents through recovery and closure. You will advance AI-enabled operations and crisis readiness with Investigations, Threat Hunting & Forensics and enterprise partners." That's about the role. Then "What you will do:" with subheadings Technical Responsibilities and Leadership & People Management Responsibilities and Knowledge and Capabilities. Then "What You Need:" with Required Qualifications and Preferred Qualifications. Also Pay ranges and Health benefits, Financial benefits, etc. Need to include sections only if real content. Use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. Do not repeat job title as heading. Do not put Job ID/requisition numbers as headings. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Posted Date: 09/14/2026 This role will be posted for a minimum of 3 days." That's metadata; maybe keep as short paragraph? It says fold minor metadata into a short

  or drop it. Could include a short p for posted date? It's minor metadata; we could drop it. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we could include a

  for posted date maybe. But also "View the U.S. work location and transparency guide to find the pay range for your location." That's a link instruction; maybe drop as boilerplate. Also "Depending on customer requirements employees and new hires in sales and field roles that require access to customer accounts as a function of the job may be required to obtain various vaccinations as an essential function of their role." That's maybe not relevant; could drop as boilerplate? It's not EEO but maybe extraneous. Likely drop. We need to preserve all substantive information: preference for Eastern/Central time zones, role description, responsibilities, qualifications, pay ranges, benefits. We need sections: maybe About the role (pref + role description), Responsibilities (technical, leadership, knowledge), Requirements (required qualifications), Preferred Qualifications, Benefits (health, financial), Pay (pay ranges). Also maybe Schedule? Not mentioned. So no Schedule section. We must not create sections with filler like "commensurate with experience". Not present. We need to use

  for each section heading. Use

  • for any list. For prose use

    . For lists of responsibilities we can use

    . For qualifications also list. Let's structure:

    About the role

    Preference will be given to candidates residing in the Eastern or Central time zones. As a Senior Manager, AI Security Operations & Crisis Management, you will lead the enterprise Cyber Incident Response Team (CIRT) and coordinate incidents through recovery and closure. You will advance AI-enabled operations and crisis readiness with Investigations, Threat Hunting & Forensics and enterprise partners.

    Responsibilities

    Then sub-sections? Could keep as one Responsibilities section with 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 to be safe we can just use

    for main sections and inside use

    or

    with maybe bold text? But we could also embed subheadings as within

    . Simpler: keep one Responsibilities section with

    containing items grouped maybe with
    • containing subheadings as . That's acceptable. List items: - Technical Responsibilities: - Lead global CIRT operations, including follow-the-sun coverage, escalation, containment, recovery, closure, and continuity during outages. - Oversee managed detection and response providers, including readiness, governance, performance, escalation quality, budgets, licensing, and commitments. - Advance responsible AI-assisted triage, investigation, decision support, documentation, and response with oversight, approvals, auditability, and reversibility. - Own the Cyber Defense digital twin roadmap and operationalize capabilities by defining use cases, requirements, success measures, acceptance, adoption, and legacy retirement. - Direct incident response; govern non-destructive containment and automated actions; and engage Investigations, Threat Hunting & Forensics when required. - Monitor response time, escalation and case quality, automation effectiveness, queue health, service levels, and corrective actions. - Own the detection content lifecycle with Detection Engineering, including rule development, tuning, coverage mapping, and deprecation. - Partner with Cyber Threat Intelligence, Threat Exposure Management, Vulnerability Management, Security Engineering, and Enterprise Technology to improve response. - Leadership & People Management Responsibilities: - Own cyber crisis management and CIRT activation, including severity criteria, escalation thresholds, leadership notifications, governance, and operational coordination. - Lead executive briefings, stakeholder updates, reporting, communication cadence, and documentation of significant decisions. - Coordinate response with crisis, communications, legal, privacy, human resources, procurement, continuity, and technology operations teams. - Lead executive tabletop, functional, and technical exercises; maintain the roadmap and close corrective actions. - Lead post-incident reviews and incorporate technical findings and root-cause lessons into playbooks and readiness activities. - Build CIRT leadership depth through coaching, exercises, structured development, and clear performance expectations. - Knowledge and Capabilities: - Apply incident response, recovery, crisis communications, business continuity, and crisis coordination practices during high-pressure events. - Translate issues into business terms and coordinate concurrent workstreams using risk-based decisions. - Integrate FDA, HIPAA, SEC cyber disclosure, sanctions compliance, and other reporting considerations into response processes. - Address threats involving contractors and contingent workers through identity verification and access revocation coordination. - Participate in after-hours or on-call incident response and crisis management activities as required. Then

      Requirements

      (or Qualifications?). The instruction list includes Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Required Qualifications and Preferred Qualifications. Could combine into Requirements section with sublists? Or separate sections: Requirements (required) and Qualifications (preferred). But they said prefer few substantive sections over many thin ones. Could have one "Qualifications" section with required and preferred sublists. But they also list Requirements as possible heading. Let's make a section "Requirements" for required qualifications, and another "Preferred Qualifications" for preferred. That's two sections; still okay. We'll do:

      Requirements

      • Bachelor's degree in Cybersecurity, Computer Science, Information Technology, Engineering, Business, or a related field.
      • Minimum 10 years of experience in cybersecurity operations, incident response, crisis management, technology operations, or enterprise service delivery.
      • Minimum 5 years of leadership experience managing technical teams, global operations, strategic initiatives, or managed services.
      • Experience leading significant cybersecurity incidents with technical, business, legal, communications, and executive stakeholders.
      • Experience managing a Security Operations Center, CIRT, Managed Detection and Response service, or comparable operational capability.
      • Experience implementing or governing AI-enabled workflows, automation, orchestration, or technology-enabled operational transformation.

      Preferred Qualifications

      • Master's degree in Cybersecurity, Business Administration, Technology Management, or a related discipline.
      • Professional certification such as CISSP, CISM, GCIH, ITIL, PMP, or equivalent.
      Then Benefits: health benefits and financial benefits. Could combine into Benefits section with two sublists.

      Benefits

      • Health benefits include: Medical and prescription drug insurance, dental insurance, vision insurance, critical illness insurance, accident insurance, hospital indemnity insurance, personalized healthcare support, wellbeing program and tobacco cessation program.
      • Financial benefits include: Health Savings Account (HSA), Flexible Spending Accounts (FSAs), 401(k) plan, Employee Stock Purchase Plan (ESPP), basic life and AD&D insurance, and short-term disability insurance.
      Pay: we have multiple pay ranges based on location codes. We should include them as a list.

      Pay

      • USN: $155,900 - $259,700 USD Annual
      • US5: $163,700 - $272,700 USD Annual
      • US10: $171,500 - $285,700 USD Annual
      • US15: $179,300 - $298,700 USD Annual
      • US20: $187,100 - $311,600 USD Annual
      • US30: $202,700 - $337,600 USD Annual
      We could also include note: "View the U.S. work location and transparency guide to find the pay range for your location." That's maybe boilerplate; we could drop. We should not include schedule section. Now ensure no duplicated lines. Also remove "Posted Date: 09/14/2026 This role will be posted for a minimum of 3 days." Could drop. Check for any other boilerplate: "Stryker offers innovative products and services in MedSurg, Neurotechnology, Orthopaedics and Spine that help improve patient and healthcare outcomes. Alongside its customers around the world, Stryker impacts more than 150 million patients annually." That's company description; maybe keep as part of About the role? It's not directly about role but could be considered boilerplate? It's about company; maybe we can keep as part of About the role? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not those; it's company description. Could keep as part of About the role? Might be considered substantive? It's not about the role but about company. Might be okay to keep. However, they said "Preserve ALL substantive information; do NOT invent or summarize away detail." This is substantive about the company. I'd include it in About the role paragraph after the role description. Thus About the role paragraph: "Preference will be given to candidates residing in the Eastern or Central time zones. As a Senior Manager, AI Security Operations & Crisis Management, you will lead the enterprise Cyber Incident Response Team (CIRT) and coordinate incidents through recovery and closure. You will advance AI-enabled operations and crisis readiness with Investigations, Threat Hunting & Forensics and enterprise partners. Stryker offers innovative products and services in MedSurg, Neurotechnology, Orthopaedics and Spine that help improve patient and healthcare outcomes. Alongside its customers around the world, Stryker impacts more than 150 million patients annually." Now check for any other lines: "Depending on customer requirements employees and new hires in sales and field roles that require access to customer accounts as a function of the job may be required to obtain various vaccinations as an essential function of their role." That's not relevant to this role (maybe generic). Could drop as boilerplate? It's not EEO but could be considered not substantive for this role. Safer to drop. Now