DevOps Lead
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 a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; 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.
We need to parse the posting.
Content:
- Who We Are: description of TKO Group Holdings, Inc. (NYSE: TKO) etc. This is "About the company". Could be "About the role"? Actually "Who We Are" is about the company. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use "About the company" maybe but they gave examples; we can still use "About the role" but we have "Who We Are". Might be better to use "About the company" as heading? 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 suggests those as typical. We can use "About the company" as heading; but they said "e.g." meaning examples. So we can use any appropriate heading. However they also said "Do NOT repeat the job title as a heading (the page already shows it)". So we can have "About the company". We'll include that.
Then "The Role and What You’ll Do": that's responsibilities. So we can have Responsibilities
with bullet list of duties.
Then "You Have These": that's requirements/qualifications. Could split into Requirements (must-have) and Qualifications (nice-to-have). They have "You Have These" (mandatory) and "We’d Love If You Also Have These" (preferred). So we can have Requirements
for mandatory, and Preferred Qualifications
for nice-to-have. Or we could combine but better separate.
Then "Travel": occasional travel required. That could be a note under Responsibilities or a separate section like "Travel". Not in list of examples but we can include if substantive. It's a specific content. Could be a
under Responsibilities or separate
Travel
. Since they said prefer few substantive sections over many thin ones, maybe include travel as a bullet under Responsibilities.
Then "Per local requirements and in the interest of transparency, the hourly rate shown below reflects the prevalent current hiring range for this position." Then they give hiring rate min and max. That's Pay info. So we should include a Pay section with the salary range. They said never create Pay/Schedule/Benefits sections unless posting actually states them. Here they state hiring rate min and max annually. So we can include Pay section.
Benefits: they mention "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." That's benefits description. So we can include Benefits section.
Schedule: not mentioned. So we should not create Schedule section.
EEO etc: remove boilerplate.
Thus sections: About the company, Responsibilities, Requirements, Preferred Qualifications, Pay, Benefits, Travel (maybe under Responsibilities). We'll decide to include Travel as a bullet under Responsibilities.
Now we need to format using for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can condense into bullet points while preserving meaning. Must not lose detail. We need to be careful to include all specifics.
Let's extract details.
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.
That's all.
The Role and What You’ll Do (Responsibilities):
List:
- 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.
Note: Some repetition: earlier bullet about owning deployment etc. We'll keep but avoid duplication? The instruction says remove duplicated lines. So we need to deduplicate similar statements. Let's consolidate.
We can create a bullet list of responsibilities, each distinct.
Let's list unique responsibilities:
1. Own deployment, release management, and security operations for Salesforce and business-systems platforms (reliable, secure, fast to evolve).
2. Establish and continuously optimize frameworks for deployment, pipeline, and environment management.
3. Own security operations: observability, monitoring, incident response, reliability and scaling.
4. Own engineering discipline, automation, operational guardrails to make delivery safe, repeatable, high-quality.
5. Serve as connective tissue between software developers, security, IT operations: streamline workflows, introduce tooling and AI capabilities to accelerate deployments and strengthen security.
6. Own framework and ongoing optimization of deployment, pipeline (CI/CD), environment management, release management across Salesforce and connected business-systems landscape.
7. Own security vendor relationships: ensure adherence to SLAs, monitor services, alerting.
8. Facilitate communication and streamline workflows between software developers, security, IT operations teams, breaking down silos across delivery pipeline.
9. Own tooling and AI capabilities that accelerate deployment, testing, operational tasks; continuously evaluate and introduce automation improving speed and quality.
10. Establish branching, release, environment-promotion strategies for predictable, low-risk deployments.
11. Embed security and compliance controls directly into pipeline (shift-left), partnering with platform and data architecture functions to enforce standards.
12. Define, track, improve DevSecOps and quality KPIs: deployment frequency, lead time, change-failure rate, mean time to recovery, test coverage, defect escape rate.
13. Lead security incident response and post-incident reviews: ensure rigorous root-cause analysis and durable remediation.
14. Govern environments and sandboxes: data seeding, refresh strategy, access controls.
15. Partner with Director, Salesforce Platform Architecture & Delivery and Data & Marketing Technology Architect to align release governance, architecture standards, quality expectations.
We can combine some similar points: #2 and #6 overlap (frameworks for deployment, pipeline, environment management). We'll keep one.
Now Requirements (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).
Preferred Qualifications (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
for prose. Do NOT repeat job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; 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. We need to parse the posting. Content: - Who We Are: description of TKO Group Holdings, Inc. (NYSE: TKO) etc. This is "About the company". Could be "About the role"? Actually "Who We Are" is about the company. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use "About the company" maybe but they gave examples; we can still use "About the role" but we have "Who We Are". Might be better to use "About the company" as heading? 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 suggests those as typical. We can use "About the company" as heading; but they said "e.g." meaning examples. So we can use any appropriate heading. However they also said "Do NOT repeat the job title as a heading (the page already shows it)". So we can have "About the company". We'll include that.
Then "The Role and What You’ll Do": that's responsibilities. So we can have Responsibilities
with bullet list of duties.
Then "You Have These": that's requirements/qualifications. Could split into Requirements (must-have) and Qualifications (nice-to-have). They have "You Have These" (mandatory) and "We’d Love If You Also Have These" (preferred). So we can have Requirements
for mandatory, and Preferred Qualifications
for nice-to-have. Or we could combine but better separate.
Then "Travel": occasional travel required. That could be a note under Responsibilities or a separate section like "Travel". Not in list of examples but we can include if substantive. It's a specific content. Could be a
Responsibilities
with bullet list of duties. Then "You Have These": that's requirements/qualifications. Could split into Requirements (must-have) and Qualifications (nice-to-have). They have "You Have These" (mandatory) and "We’d Love If You Also Have These" (preferred). So we can haveRequirements
for mandatory, andPreferred Qualifications
for nice-to-have. Or we could combine but better separate. Then "Travel": occasional travel required. That could be a note under Responsibilities or a separate section like "Travel". Not in list of examples but we can include if substantive. It's a specific content. Could be aunder Responsibilities or separate
Travel
. Since they said prefer few substantive sections over many thin ones, maybe include travel as a bullet under Responsibilities. Then "Per local requirements and in the interest of transparency, the hourly rate shown below reflects the prevalent current hiring range for this position." Then they give hiring rate min and max. That's Pay info. So we should include a Pay section with the salary range. They said never create Pay/Schedule/Benefits sections unless posting actually states them. Here they state hiring rate min and max annually. So we can include Pay section. Benefits: they mention "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." That's benefits description. So we can include Benefits section. Schedule: not mentioned. So we should not create Schedule section. EEO etc: remove boilerplate. Thus sections: About the company, Responsibilities, Requirements, Preferred Qualifications, Pay, Benefits, Travel (maybe under Responsibilities). We'll decide to include Travel as a bullet under Responsibilities. Now we need to format using for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can condense into bullet points while preserving meaning. Must not lose detail. We need to be careful to include all specifics.
Let's extract details.
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.
That's all.
The Role and What You’ll Do (Responsibilities):
List:
- 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.
Note: Some repetition: earlier bullet about owning deployment etc. We'll keep but avoid duplication? The instruction says remove duplicated lines. So we need to deduplicate similar statements. Let's consolidate.
We can create a bullet list of responsibilities, each distinct.
Let's list unique responsibilities:
1. Own deployment, release management, and security operations for Salesforce and business-systems platforms (reliable, secure, fast to evolve).
2. Establish and continuously optimize frameworks for deployment, pipeline, and environment management.
3. Own security operations: observability, monitoring, incident response, reliability and scaling.
4. Own engineering discipline, automation, operational guardrails to make delivery safe, repeatable, high-quality.
5. Serve as connective tissue between software developers, security, IT operations: streamline workflows, introduce tooling and AI capabilities to accelerate deployments and strengthen security.
6. Own framework and ongoing optimization of deployment, pipeline (CI/CD), environment management, release management across Salesforce and connected business-systems landscape.
7. Own security vendor relationships: ensure adherence to SLAs, monitor services, alerting.
8. Facilitate communication and streamline workflows between software developers, security, IT operations teams, breaking down silos across delivery pipeline.
9. Own tooling and AI capabilities that accelerate deployment, testing, operational tasks; continuously evaluate and introduce automation improving speed and quality.
10. Establish branching, release, environment-promotion strategies for predictable, low-risk deployments.
11. Embed security and compliance controls directly into pipeline (shift-left), partnering with platform and data architecture functions to enforce standards.
12. Define, track, improve DevSecOps and quality KPIs: deployment frequency, lead time, change-failure rate, mean time to recovery, test coverage, defect escape rate.
13. Lead security incident response and post-incident reviews: ensure rigorous root-cause analysis and durable remediation.
14. Govern environments and sandboxes: data seeding, refresh strategy, access controls.
15. Partner with Director, Salesforce Platform Architecture & Delivery and Data & Marketing Technology Architect to align release governance, architecture standards, quality expectations.
We can combine some similar points: #2 and #6 overlap (frameworks for deployment, pipeline, environment management). We'll keep one.
Now Requirements (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).
Preferred Qualifications (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
for prose. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can condense into bullet points while preserving meaning. Must not lose detail. We need to be careful to include all specifics. Let's extract details. 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. That's all. The Role and What You’ll Do (Responsibilities): List: - 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. Note: Some repetition: earlier bullet about owning deployment etc. We'll keep but avoid duplication? The instruction says remove duplicated lines. So we need to deduplicate similar statements. Let's consolidate. We can create a bullet list of responsibilities, each distinct. Let's list unique responsibilities: 1. Own deployment, release management, and security operations for Salesforce and business-systems platforms (reliable, secure, fast to evolve). 2. Establish and continuously optimize frameworks for deployment, pipeline, and environment management. 3. Own security operations: observability, monitoring, incident response, reliability and scaling. 4. Own engineering discipline, automation, operational guardrails to make delivery safe, repeatable, high-quality. 5. Serve as connective tissue between software developers, security, IT operations: streamline workflows, introduce tooling and AI capabilities to accelerate deployments and strengthen security. 6. Own framework and ongoing optimization of deployment, pipeline (CI/CD), environment management, release management across Salesforce and connected business-systems landscape. 7. Own security vendor relationships: ensure adherence to SLAs, monitor services, alerting. 8. Facilitate communication and streamline workflows between software developers, security, IT operations teams, breaking down silos across delivery pipeline. 9. Own tooling and AI capabilities that accelerate deployment, testing, operational tasks; continuously evaluate and introduce automation improving speed and quality. 10. Establish branching, release, environment-promotion strategies for predictable, low-risk deployments. 11. Embed security and compliance controls directly into pipeline (shift-left), partnering with platform and data architecture functions to enforce standards. 12. Define, track, improve DevSecOps and quality KPIs: deployment frequency, lead time, change-failure rate, mean time to recovery, test coverage, defect escape rate. 13. Lead security incident response and post-incident reviews: ensure rigorous root-cause analysis and durable remediation. 14. Govern environments and sandboxes: data seeding, refresh strategy, access controls. 15. Partner with Director, Salesforce Platform Architecture & Delivery and Data & Marketing Technology Architect to align release governance, architecture standards, quality expectations. We can combine some similar points: #2 and #6 overlap (frameworks for deployment, pipeline, environment management). We'll keep one. Now Requirements (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). Preferred Qualifications (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