DevOps Lead

We need to output HTML fragment with sections: About the role? Actually the posting includes "Who We Are", "The Role and What You’ll Do", "You Have These", "We’d Love If You Also Have These", "Travel", "Per local requirements..." includes pay info. Also "Hiring Rate Minimum $112,500 annually" and "Maximum $150,000 annually". So we need sections: About the role? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to include sections only when posting has real specific content. So we can have sections: About the role (maybe from "Who We Are"? Actually "Who We Are" is company overview, not role. But we can treat "About the role" as description of role. The posting includes "The Role and What You’ll Do". That's role description. So we can put that under

About the role

with paragraphs. Responsibilities: The bullet list of duties under "The DevOps Lead Will Own ..." etc. Those are responsibilities. Requirements: The "You Have These" list (mandatory). Qualifications: maybe same as requirements? But we can separate: Requirements (mandatory) and Qualifications (preferred) or Skills. The instruction says we can use sections like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only those with content. We have "We’d Love If You Also Have These" which are preferred qualifications. Could be under Qualifications or Skills. We have Travel info: occasional travel required. That could be under Schedule? Not exactly schedule. Could be under a separate section maybe "Travel". But instruction only lists example headings; we can add other headings if needed? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use

for section headings (e.g. ...)" implying those are examples; we could still use other headings but better to stick to those. Travel could be under Schedule? Not really. Could be under "Schedule" if we interpret schedule as work schedule/travel. But maybe better to include a "Travel" section? The instruction didn't forbid other headings, but to be safe we could include a "Travel" heading as

Travel

. However they said "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are typical but not exclusive. I'd include Travel as its own heading. Pay: we have hiring rate min and max. So we can have

Pay

with paragraph. Benefits: The posting mentions "robust benefits, such as health care, retirement, vacation and other paid time off, and additional offerings." Also mentions short- and long-term incentives. So we can include Benefits section. Schedule: Not explicitly given besides occasional travel. Could be omitted if no specific schedule. But we could include Schedule with maybe "Standard full-time schedule; occasional travel required." However the instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. Schedule not stated besides travel; but we could treat travel as schedule? Might be safer to omit Schedule section. We must not include boilerplate like EEO, privacy, terms, etc. Remove duplicated lines. We must preserve all substantive information. Let's extract content: Who We Are: 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. The Role and What You’ll Do: TKO is seeking a DevOps Lead to own the deployment, release management, and security operations that keep our Salesforce and business-systems platforms reliable, secure, and fast to evolve. Reporting to the VP, Business Systems, this role establishes and continuously optimizes the frameworks for deployment, pipeline, and environment management; and owns security operations spanning observability, monitoring, incident response, and reliability and scaling. The DevOps Lead owns the engineering discipline, automation, and operational guardrails that make delivery safe, repeatable, and high-quality. The role serves as the connective tissue between software developers, security, and IT operations - streamlining workflows and introducing tooling and AI capabilities that accelerates deployments and strengthens security operations. The DevOps Lead Will Own: - the framework and ongoing optimization of deployment, pipeline (CI/CD), environment management, and release management across the Salesforce and connected business-systems landscape. - Own security operations — including observability, monitoring, incident response, and reliability and scaling — ensuring platforms are secure, resilient, and performant. - Own security vendor relationships, ensuring adherence to SLAs, monitoring services, and alerting - Facilitate communication and streamline workflows between software developers, security, and IT operations teams, breaking down silos across the delivery pipeline. - Own the tooling and AI capabilities that accelerate deployment, testing, and operational tasks, continuously evaluating and introducing automation that improves speed and quality. - Establish branching, release, and environment-promotion strategies that enable predictable, low-risk deployments. - Embed security and compliance controls directly into the pipeline (shift-left), partnering with the platform and data architecture functions to enforce standards. - Define, track, and improve DevSecOps and quality KPIs — such as deployment frequency, lead time, change-failure rate, mean time to recovery, test coverage, and defect escape rate. - Lead security incident response and post-incident reviews, ensuring rigorous root-cause analysis and durable remediation. - Govern environments and sandboxes, including data seeding, refresh strategy, and access controls. - Partner with the Director, Salesforce Platform Architecture & Delivery and the Data & Marketing Technology Architect to align release governance, architecture standards, and quality expectations. You Have These: - 6+ years in DevOps/DevSecOps, release engineering, and site reliability, including experience leading practices, standards, and teams. - Bachelor’s degree in Computer Science, Information Systems, or a related field, or equivalent experience. - Hands-on expertise building and optimizing CI/CD pipelines, deployment automation, and environment/release management. - Experience owning security operations: observability, monitoring and alerting, incident response, and reliability and scaling practices. - Proficiency with DevOps and release-management tooling (e.g., Salesforce DevOps Center, Copado, Gearset, Git-based workflows, or similar). - Experience with observability and monitoring platforms (e.g., Datadog, Splunk, New Relic, or similar). - Demonstrated ability to facilitate collaboration across software development, security, and IT operations teams. - Experience applying AI and automation to accelerate deployment, testing, and operational tasks. - Strong understanding of security and compliance practices, including access control, secrets management, and data governance. - Excellent problem-solving, critical thinking, and communication skills (written and verbal, for technical and non-technical audiences). We’d Love If You Also Have These: - Background in QA strategy and test automation, including building automated test frameworks and embedding quality gates in the delivery lifecycle. - Experience within the Salesforce ecosystem (Sales Cloud, Service Cloud, Data Cloud) and Salesforce-specific deployment and testing tooling. - Relevant certifications (e.g., Salesforce DevOps/Platform certifications, AWS or Azure DevOps, Certified Kubernetes, or security certifications such as Security+ or CISSP). - Experience with infrastructure-as-code and cloud platform operations (AWS, Azure, or GCP). - Experience operating in regulated, high-availability, or high-traffic environments. - Experience in live events, sports, hospitality, or media businesses. Travel: - Occasional travel is required for onsite support, projects, leadership offsites, workshops, and training/conferences/events. Pay: - Hiring Rate Minimum $112,500 annually (minimum will not fall below the applicable State/local minimum salary thresholds) - Hiring Rate Maximum $150,000 annually Benefits: - The company strives to provide locally competitive rewards packages, which include base rate along with, as applicable, short- and long-term incentives, growth and developmental opportunities, and robust benefits, such as health care, retirement, vacation and other paid time off, and additional offerings. We should not include EEO etc. Now produce HTML fragment with

headings and

or

• . We need to decide which sections: About the role (maybe combine Who We Are and role description? Actually About the role could be the description of role; Who We Are is company overview. Could be separate section "About the company". But instruction only gave examples; we could add About the company as heading. But maybe better to have "About the role" covering the role description, and maybe include a brief company overview in a paragraph before that? The instruction says do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. It didn't forbid a company overview paragraph. We could include a

  before first heading? The output should be only HTML fragment; we can start with a

  for company overview then headings. But the instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we must start with a heading. So we can have a

  for company overview then

  About the role

  etc. Let's structure:

  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.

  About the role

  TKO is seeking a DevOps Lead to own the deployment, release management, and security operations that keep our Salesforce and business-systems platforms reliable, secure, and fast to evolve. Reporting to the VP, Business Systems, this role establishes and continuously optimizes the frameworks for deployment, pipeline, and environment management; and owns security operations spanning observability, monitoring, incident response, and reliability and scaling. The DevOps Lead owns the engineering discipline, automation, and operational guardrails that make delivery safe, repeatable, and high-quality. The role serves as the connective tissue between software developers, security, and IT operations - streamlining workflows and introducing tooling and AI capabilities that accelerates deployments and strengthens security operations.

  Responsibilities

  • the framework and ongoing optimization of deployment, pipeline (CI/CD), environment management, and release management across the Salesforce and connected business-systems landscape.
  • Own security operations — including observability, monitoring, incident response, and reliability and scaling — ensuring platforms are secure, resilient, and performant.
  • Own security vendor relationships, ensuring adherence to SLAs, monitoring services, and alerting
  • Facilitate communication and streamline workflows between software developers, security, and