VP, Cybersecurity Operations and Engineering

We need to output HTML fragment with sections: About the role? Actually we have "Who We Are" and "Position Overview". The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. We need to include sections only when posting has real, specific content. We have content for Who We Are (company description) maybe treat as "About the role"? Actually "Who We Are" is about company, not role. Could be "About the company"? Not in list. But we can maybe treat as "About the role"? Not exactly. The instructions list example headings but not mandatory to use only those; they say use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those headings if appropriate. We have "Position Overview" which could be "About the role". We have "Key Responsibilities". We have "Qualifications". We have "Preferred Qualifications" maybe part of Qualifications or separate? Could be under Qualifications. We have "What Success Looks Like" maybe not needed. We have Pay info: Hiring Rate Minimum $225,000 annually, Maximum $300,000 annually. So we can include Pay section. Benefits: mention robust benefits such as health care, retirement, vacation etc. So we can include Benefits. Schedule: not mentioned. So omit Schedule. Skills: not explicit list; but we could infer from qualifications but better not to invent. So maybe omit Skills. We need to preserve all substantive information, not invent. So we need to include content from Who We Are, Position Overview, Key Responsibilities (with bullet list), Qualifications (bullet list), Preferred Qualifications maybe as part of Qualifications or separate? Could be separate heading "Preferred Qualifications". But the instruction says use headings like Qualifications, Skills, etc. Could add "Preferred Qualifications" as

but not in list; but it's okay as a heading? Might be considered extra but okay. However they said use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They didn't forbid other headings, but they gave examples. Safer to stick to those. We could incorporate Preferred Qualifications into Qualifications section as a subsection maybe using

or

. But we need to preserve all info; we can include them as part of Qualifications
with note "Preferred". That's okay. We need to remove boilerplate: EEO, legal, privacy policy, terms of use, etc. Also remove duplicated lines. Also remove application instructions (none). Also remove cookie/navigation etc. We need to output only HTML fragment, no /, no markdown fences. Let's craft:

About the role

Position Overview: The VP, Cybersecurity Operations & Engineering is responsible for leading and maturing the enterprise cybersecurity Operations and Engineering programs with oversight on Cybersecurity program execution, and risk management, while leading cybersecurity operations and engineering capabilities. This leader partners across Cybersecurity, technology, legal, compliance, privacy, and business units to align and articulate strategy, operationalize policy, strengthen controls, improve resilience, and provide measurable security outcomes across a complex global environment. The ideal candidate brings a strong blend of executive leadership, program & project management discipline, technical depth, and business partnership. They are equally effective shaping long-range roadmaps, communicating across all levels of an enterprise, driving control maturity, and ensuring day-to-day operational readiness across detection, response, vulnerability management, security engineering, risk management, and threat-informed defense.

But we also have Who We Are description. Could include as a separate

About the company

but not in list. Maybe we can incorporate into About the role? Might be weird. Better to add a section "About the company" but not in examples; risk of being considered extra. However the instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say you cannot use other headings, but they gave examples. Safer to include only those headings that have content. We have content for About the role (Position Overview). We have Who We Are maybe could be considered "About the role"? Not exactly. But we could treat it as "About the company" but not listed. However we could drop it? The instruction says preserve ALL substantive information. So we must keep Who We Are info. So we need a heading for it. Could use

About TKO Group Holdings

. That's still an h3 heading, not in examples but still an h3. The instruction didn't forbid other headings; they just gave examples. So it's okay. Thus:

About TKO Group Holdings

TKO Group Holdings, Inc. (NYSE: TKO) is a premium sports and entertainment company. TKO owns iconic properties including UFC, the world’s premier mixed martial arts organization; WWE, the global leader in sports entertainment; and PBR, the world’s premier bull riding organization. Together, these properties reach 1 billion households across 210 countries and territories and organize more than 500 live events year-round, attracting more than three million fans. TKO also services and partners with major sports rights holders through IMG, an industry-leading global sports marketing agency; and On Location, a global leader in premium experiential hospitality.

Then

About the role

with Position Overview paragraph. Then

Responsibilities

with
• items from Key Responsibilities. We need to break down Key Responsibilities into bullet points. The text includes several paragraphs each starting with a bold heading. We'll extract each as a bullet. Key Responsibilities sections: - Cybersecurity Program Leadership and Governance: Lead the enterprise cybersecurity operations & engineering programs, including documenting strategy, risk governance, organization roadmap development, budgeting, KPI reporting, and preparing executive communications. Contribute to cybersecurity policies, standards, procedures, and control frameworks aligned to business objectives and risk appetite. Develop and maintain governance forums, steering committee materials, risk updates, and decision-supporting business cases for senior leadership. Partner with legal, compliance, privacy, internal audit, and technology stakeholders to strengthen the company’s overall security, regulatory, and governance posture. Drive consistent security practices across corporate, cloud, application, and business environments, ensuring alignment with enterprise architecture and operating models. Translate threat, control, and assessment findings into practical, risk-informed recommendations and prioritized remediation plans. - Operations Oversight and Resilience: Provide executive oversight for security operations, including SOC and/or MSSP performance, alert monitoring, incident triage, escalation management, and operational readiness. Own and mature incident response planning, operational runbooks, tabletop exercises, and cross-functional response coordination with technology, legal, HR, and compliance teams. Oversee threat intelligence, threat detection, threat hunting, and vulnerability management capabilities to improve visibility, response speed, and control effectiveness. Ensure the organization is prepared to protect, detect, respond to, and recover from cybersecurity events affecting critical systems, intellectual property, data, and brand reputation. Develop and monitor operational metrics and service-level indicators for security operations, incident management, remediation progress, and program effectiveness. - Security Engineering and Control Maturity: Oversee the design, implementation, enhancement, and lifecycle management of cybersecurity technologies and control capabilities across on-premises, cloud, endpoint, identity, and network domains. Partner closely with infrastructure, platform, and software engineering teams to embed security into enterprise architecture, system design, and operational workflows. Support secure development lifecycle practices, software assurance, secure coding, and application security initiatives across internal and customer-facing environments. Guide the selection and optimization of security tools and services, including SIEM, EDR, IDS/IPS, firewalls, vulnerability management, logging, monitoring, and related protection technologies. Promote automation, orchestration, and process simplification to improve scalability, consistency, and efficiency across cybersecurity operations and engineering. - Risk, Compliance, and Business Partnership: Lead cyber risk assessments across infrastructure, applications, vendors, business processes, and emerging technology initiatives. Support compliance and control maturity efforts related to frameworks and obligations such as NIST, ISO 27001, PCI-DSS, SOC, SOX, GDPR, privacy, and other applicable requirements. Provide security leadership for vendor and third-party reviews, architectural reviews, major initiatives, and transformation programs. Build trusted relationships with business and technology leaders to ensure security enables growth, resilience, and informed risk-taking. Champion security awareness, education, and culture-building efforts that improve employee behavior and strengthen organizational readiness. - Team Leadership: Lead, coach, and develop high-performing cybersecurity managers and individual contributors across program, operations, and engineering functions. Foster a culture of accountability, collaboration, continuous improvement, and service-oriented partnership. Mentor technical teams on incident response, operational excellence, architectural decision-making, and effective communication with executive and non-technical audiences. We'll put each as
• . Then

  Qualifications

  with
  • items from Qualifications list. Qualifications bullet points: - Bachelor’s degree in Computer Science, Information Systems, Cybersecurity, or a related field, or equivalent professional experience. - 12+ years of progressive cybersecurity experience, including leadership of enterprise security programs in complex, high-growth, or globally distributed organizations. - 7+ years of leadership experience managing managers, cross-functional teams, and/or external service providers across multiple cybersecurity domains. - Demonstrated success building or maturing cybersecurity governance, program management, security operations, and security engineering capabilities. - Strong working knowledge of cybersecurity frameworks, regulatory requirements, and assurance practices, including NIST CSF, ISO 27001, PCI-DSS, SOC, SOX, data privacy, and related standards. - Experience leading or overseeing incident response, threat intelligence, vulnerability management, detection engineering, and security monitoring programs. - Strong technical understanding of cloud security, identity and access management, endpoint protection, network security, logging and monitoring, system hardening, and enterprise security architecture. - Experience working closely with software development and infrastructure teams to integrate security into lifecycle management, architecture, and operational processes. - Proven ability to define metrics, communicate risk clearly, and present meaningful security insights to operational, technical, and executive stakeholders. - Strong business judgment and the ability to balance risk reduction, operational efficiency, and strategic enablement. - Excellent written and verbal communication skills, with the ability to influence across all levels of the organization. Preferred Qualifications could be added as a note within Qualifications or separate

    Preferred Qualifications

    . Since we have a section for Qualifications, we could add Preferred Qualifications as a subsection maybe using

    but better to keep as

    with a note. Let's add a

    Preferred Qualifications

    with bullet list. Preferred Qualifications bullet points: - Master’s degree in a relevant discipline. - CISSP or comparable industry certification. - Experience in media, entertainment, sports, or other fast-paced global operating environments. - Experience overseeing a hybrid model that includes internal teams and managed security partners. - Experience building metric-driven security programs and using automation to streamline cyber workflows. Then

    Pay

    with

    containing the hiring rate: Minimum $225,000 annually, Maximum $300,000 annually. Also note that minimum will not fall below applicable State/local minimum salary thresholds. Then

    Benefits

    with

    describing robust benefits: health care, retirement, vacation and other paid time off, short- and long-term incentives, growth and developmental opportunities. We should not include Schedule. We must not include boilerplate like EEO, privacy policy, terms of use, etc. Now output HTML fragment. Check for any repeated content: We have Position Overview paragraph included in About the role; we also have Who We