Jobs · Management · California

Manager, Technology Operations - Olympic & Paralympic Games

TKO · Los Angeles, CA · 1 mo ago
Management$94k/yrFull-time
We need to output HTML fragment with sections: About the role? Actually we have "Who We Are" description, then "Role Summary", then "Responsibilities", then "Qualifications". Also there is pay info: Hiring Rate Minimum $93,750 annually, maximum $125,000 annually. So we need a Pay section. Benefits? Not explicitly listed; there is mention of benefits in generic statement: "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 generic but still mentions benefits. The instruction: include a section ONLY when posting has real, specific content for it — never emit 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 posting actually states them. The benefits statement is generic but still states benefits exist. Is that considered specific enough? It mentions health care, retirement, vacation and other paid time off, and additional offerings. That's somewhat specific. I'd include Benefits section with those items. Schedule? Not mentioned. So no Schedule section. We need headings: About the role? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The posting has "Who We Are" (company overview) and "Role Summary". Should we treat "Who We Are" as About the role? Possibly "About the role" is not present; but we could use "About the company" but not in list. The instruction says use those examples but not limited? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely we should use those headings where applicable. We have Responsibilities, Qualifications, Benefits, Pay. Also maybe "About the role" could be the Role Summary. We'll use

About the role

for the Role Summary paragraph. Also maybe "Who We Are" could be omitted? It's substantive info about company; maybe we could include as a

before sections. The instruction: 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. So we can include a brief paragraph about the company as intro. Thus output:

Who We Are ... (the paragraph)

About the role

Role Summary ...

Responsibilities

  • ...
  • ...

Qualifications

  • ...
  • ...

Benefits

  • Health care
  • Retirement
  • Vacation and other paid time off
  • Short- and long-term incentives
  • Growth and developmental opportunities
  • Additional offerings

Pay

Hiring Rate Minimum $93,750 annually (minimum will not fall below the applicable State/local minimum salary thresholds)

Hiring Rate Maximum $125,000 annually

We must ensure no boilerplate like EEO etc. Remove those paragraphs. Check that we preserved all substantive information: Who We Are paragraph, Role Summary paragraph, responsibilities list, qualifications list, benefits statement, pay info. We need to ensure we didn't miss any details: In Responsibilities there are many bullet-like sentences; we need to convert each sentence into
  • . Let's extract them: - Manage day-to-day technology engagement with external program stakeholders and partner organizations, including governance forums, status reporting, requirements alignment, decision management, dependency tracking, issue escalation, and follow-through. - Lead planning and governance for assigned technology programs and operational initiatives. - Translate objectives into integrated plans, milestones, dependencies, risks, issues, decisions, and actions. - Coordinate cross-functional teams across Technology, Product, Engineering, Data, Cybersecurity, Architecture, Support, and business functions. - Establish operating cadences, communication paths, escalation procedures, and clear ownership across workstreams. - Prepare executive-ready status reports, readouts, agendas, decision logs and governance materials. - Track delivery progress, surface tradeoffs, and escalate risks, blockers, and unresolved decisions. - Support UAT, release readiness, go-live planning, production launches, hyper care, and Games-time operational readiness. - Coordinate security and compliance dependencies, including penetration testing, remediation tracking, and partner communications. - Lead lessons learned and improve repeatable delivery, PMO, and governance practices. Qualifications bullet points: - 4+ years of experience in technology program management, PMO, technical project management, or a related role. - Proven experience managing complex, cross-functional technology programs with multiple teams and dependencies. - Strong skills in planning, RAID management, dependency tracking, reporting, meeting facilitation, and escalation. - Ability to translate technical information into clear business and executive communications. - Experience coordinating software delivery, integrations, testing, releases, or operational readiness. - Strong judgment, attention to detail, follow-through, and ability to work independently in a fast-paced environment. - Experience with common program management, collaboration, documentation, and reporting tools. Preferred Experience bullet points (these are under Qualifications? Actually after Qualifications there is "Preferred Experience" list. Should we include them under Qualifications or separate? The instruction: use headings like Requirements, Qualifications, Skills. We could treat "Preferred Experience" as part of Qualifications or maybe as Skills. But we have no separate heading for Preferred Experience. Could include them under Qualifications as additional items. Or we could create a Skills section. The instruction says use headings e.g. Skills. Might be appropriate to put Preferred Experience under Skills. However the list includes: Major sporting events, consulting, live events, hospitality, ticketing, ecommerce, or other time-critical consumer programs. Olympic, Paralympic, IOC, OCOG, federation, venue, or rights-holder environments. Enterprise integrations, data sharing, cybersecurity reviews, penetration testing, or third-party technology governance. Globally distributed teams and stakeholders across multiple time zones. These are preferences, could be placed under Skills or Qualifications. Since we already have Qualifications heading, we could add them there as well, but maybe better to split: Qualifications for required, Skills for preferred. Let's do:

    Qualifications

    for required items.

    Skills

    for preferred experience items. Thus we need Skills section. Check if any other sections: Requirements? Not separate. Thus final HTML:

    Who We Are ...

    About the role

    Role Summary ...

    Responsibilities

      ...

    Qualifications

      ...

    Skills

      ...

    Benefits

      ...

    Pay

    ...

    ...

    Make sure no extra whitespace issues. Now craft the Who We Are paragraph: It's long; we need to preserve all substantive information. The paragraph includes multiple sentences. We'll keep as one

    with the whole text. Let's copy: "On Location is a global leader in premium experiential hospitality, offering ticketing, curated guest experiences, live event production and travel management across sports, entertainment, fashion and culture. On Location provides unrivaled access for corporate clients and fans looking for official, immersive experiences at marquee events, including the Olympic and Paralympic Games, FIFA World Cup 2026, Super Bowl, NCAA Final Four, and more. An official partner and/or service provider to over 150 iconic rights holders, such as the IOC (the Milano Cortina 2026 and Los Angeles 2028 Olympic Games), FIFA, NFL, NCAA, UFC, WWE, and PGA of America, the company also owns and operates a number of its own unique experiences. On Location is a subsidiary of TKO Group Holdings, Inc. (NYSE: TKO), a premium sports and entertainment company. 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." Note duplicate sentence about TKO Group Holdings appears twice; we should preserve but could deduplicate? Instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Duplicate lines are considered boilerplate? It says remove duplicated lines. So we should remove duplicate lines. The duplicate is "TKO Group Holdings, Inc. (NYSE: TKO) is a premium sports and entertainment company." appears twice. We'll keep only one. Thus Who We Are paragraph will be: On Location is a global leader in premium experiential hospitality, offering ticketing, curated guest experiences, live event production and travel management across sports, entertainment, fashion and culture. On Location provides unrivaled access for corporate clients and fans looking for official, immersive experiences at marquee events, including the Olympic and Paralympic Games, FIFA World Cup 2026, Super Bowl, NCAA Final Four, and more. An official partner and/or service provider to over 150 iconic rights holders, such as the IOC (the Milano Cortina 2026 and Los Angeles 2028 Olympic Games), FIFA, NFL, NCAA, UFC, WWE, and PGA of America, the company also owns and operates a number of its own unique experiences. On Location is a subsidiary of TKO Group Holdings, Inc. (NYSE: TKO), 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. Now Role Summary paragraph: "On Location is seeking a Manager, Technology Operations to support the planning, governance, delivery, and operational readiness of the LA28 Olympic and Paralympic technology portfolio. Working in a matrixed environment, this role connects Technology Operations, Product, Engineering, Data, Cybersecurity, Architecture, Support, business teams, external vendors, and LA28/IOC stakeholders to maintain integrated plans, surface risks, facilitate decisions, and prepare initiatives for launch and Games-time operations. The ideal candidate is a structured and collaborative program leader who can bring clarity to ambiguity, manage competing priorities, influence without direct authority, and communicate effectively with both technical and executive audiences." Now Responsibilities list as above. Qualifications list as required. Skills list as preferred experience. Benefits list: from statement: "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'll list: Short- and long-term incentives, Growth and developmental opportunities, Health care, Retirement

  • Similar jobs