Reports to: Senior Director, AI Products & Platforms
Level: Senior Manager equivalent, individual contributor
Location: United States. Full East Coast business-day overlap required; East Coast base preferred, not required.
TKO has deployed Glean to Wave 1 across WWE, UFC, IMG, PBR, On Location and Corporate. The platform is live. What does not yet exist is a verified core of agents, skills and Glean projects that encode how TKO actually works — built once, trusted, and reused across business units rather than rebuilt locally six times.
This role builds that core. It is a hands-on build seat, and the work starts upstream of the build: going into a team’s actual workflow, understanding how the work really gets done, and identifying which part of it is common enough across TKO to be worth building as a verified, supported capability. Then building it — instruction sets, sources, actions, evaluation — and shipping it as the canonical version other teams adopt and extend.
The distinction that matters: this role does not exist to service agent requests. It exists to find the workflows underneath those requests, decide which ones generalize, and produce the small number of verified artifacts that let the rest of the organization build on top of them.
The most important thing about this role
This is a builder, not a coordinator. That distinction is the single most important filter for this hire.
Plenty of strong candidates can run a program — track a plan, chase owners, produce a status deck. That is not what this seat needs. The person here has to open Glean, write the prompt and instruction set, wire up the sources and actions, test against real edge cases, watch where it fails, fix it, and ship a working agent. Then do it again and teach someone else to do it.
Concretely, builder means:
•
You have personally built and shipped AI agents or assistants that other people actually used — not scoped them for someone else to build, not overseen a vendor building them.
•
You can write and iterate a system prompt or instruction set well enough to get a reliable answer out of an unreliable model.
•
You can explain why a given agent is failing, and distinguish between the causes: retrieval, permissions, instructions, source coverage, or intent scope.
•
You can design and run your own evaluation — build a test set of real user intents, define what a good answer looks like, measure fallback and error rates, and use that to decide whether something is fit to launch.
•
You are fluent enough in the platform to tell the difference between a genuine product gap that belongs on the vendor’s roadmap and something you could solve yourself in an afternoon.
•
You can look at twenty agent requests from six business units and see the three underlying capabilities worth building.
This is not a central agent-building service. Business units and individual teams are expected to build their own agents for their own local workflows, and this role exists to make that possible — not to do it for them.
Specifically, this seat does not:
•
Take agent requests and work them in order of arrival. Incoming demand is input to a prioritization judgment, not a queue commitment.
•
Build one-off agents for single teams where the underlying workflow does not generalize and the team could build it themselves. The answer in that case is a pattern, a template, and a working session.
•
Act as the platform help desk. Individual user support, access issues and how-do-I questions route to IT Service Delivery and the enablement team.
The correct read: a small number of verified, cross-functional builds that many teams depend on, plus the library and training that let teams build the rest without this person in the loop.