New opportunity

Director, Applied AI & Strategy

A+E Global Media · New York, United States

About this role

The Director, Applied AI & Strategy leads hands-on efforts to improve internal productivity at A+E Global Media. Working across business functions and Technology & Operations, the director analyzes complex workflows, identifies opportunities for agentic AI, and helps turn interventions into production-grade solutions. The role focuses on AI applications relevant to media and entertainment.

Responsibilities

  • Rapidly prototype agentic workflow solutions, refine them using business feedback, and estimate implementation costs to support business cases.
  • Help build and deploy production-grade AI agents with guardrails, evaluations, and observability for accuracy, reliability, and safety. Connect agents to enterprise resources through MCP and to applications, including legacy systems, through APIs.
  • Work with Legal & Business Affairs and Cyber Security on AI governance. Track hours reclaimed, cost savings, efficiency gains, and return on investment while keeping toolsets composable.
  • Monitor relevant AI developments and advise leadership using actionable “Buy, Build, Ignore” assessments. Translate leadership goals into a technical roadmap, manage scope and stakeholders from proof of concept through production, audit emerging tools, and develop budgets.

Required qualifications

  • A bachelor’s degree or demonstrated practical experience; 8+ years of total experience in a technical function such as solutions architecture, digital transformation, or technical operations, including delivery of enterprise-grade solutions, systems integration, and workflow automation.
  • Expertise architecting logic across complex SaaS ecosystems; 2+ years building production-ready agents with LLMs, including advanced prompting, multi-agent orchestration, RAG frameworks, and curation, enrichment, and accurate retrieval of unstructured content for LLM context.
  • 3+ years managing complex stakeholder relationships and turning business strategy into execution plans. Ability to rapidly deliver functional code and automations with AI-augmented development tools such as Cursor, Replit, or Claude. Hands-on experience implementing RAG at scale and/or fine-tuning LLMs.

Preferred qualifications include harness engineering with coding agents, AI/ML or cloud-platform certifications, and a background in statistical modeling or mathematics. The listed job locations are New York and Los Angeles. Employees collaborate in office three times per week; new hires must be commutable to an office in New York City, Los Angeles, Chicago, or Stamford, CT. Base pay is $188,034–$220,000 annually, with a 17.50% annual incentive target. Benefits include healthcare coverage and 401(k) matching.

For full details about this role, click “Apply on company site” to view the employer’s original posting.

Skills for this role

AI agentsLarge language modelsMulti-agent orchestrationPrompt engineeringRetrieval-augmented generationModel Context ProtocolAPI integrationWorkflow automationSystems integrationRapid prototypingAI evaluationsAI observabilityAI guardrailsSaaS architectureUnstructured content retrievalLLM fine-tuningCursorReplitClaudeStakeholder managementTechnical roadmappingStatistical modeling

Your skill match

Checking your profile…

YOUR NEXT STEP

Get interview-ready for this role

A focused preparation guide, built around this job’s responsibilities and requirements.

✦ AI-generated guide
Preparation suggestions, not the employer’s actual interview questions. Always check the original posting for current requirements.
01

Understand the role

What matters most

  • Find high-value workflow interventions

    The director analyzes complex workflows across business functions and Technology & Operations, prototypes agentic improvements, refines them with business feedback, and estimates implementation costs. Prepare to explain how you would identify friction, demonstrate a useful prototype, and build a case for production.

  • Deliver trustworthy production agents

    The posting calls for production-grade agents with guardrails, evaluations, and observability for accuracy, reliability, and safety. It also requires hands-on LLM work, including multi-agent orchestration and accurate retrieval of curated unstructured content. Prepare to distinguish a working demonstration from a system ready to operate.

  • Integrate across enterprise systems

    Agents must connect to enterprise resources through MCP and to applications, including legacy systems, through APIs. The role also requires architecture across complex SaaS ecosystems and composable toolsets. Prepare an integration approach that addresses dependencies without locking the solution to one tool.

  • Make productivity gains measurable and governed

    The director partners with Legal & Business Affairs and Cyber Security on AI governance, while tracking hours reclaimed, cost savings, efficiency gains, and ROI. Prepare to connect safeguards and measurement to a specific workflow intervention.

  • Turn AI developments into an executable roadmap

    The role translates leadership goals into a technical roadmap, prioritizes high-ROI work, manages stakeholders and scope, audits emerging tools, and gives leadership actionable media-relevant “Buy, Build, Ignore” assessments. Prepare to explain how evidence, cost, and business fit would shape those decisions.

Likely challenges to think through

  • Speed versus production readiness

    A likely challenge is preserving rapid prototyping while adding the evaluations, guardrails, observability, and cost estimates needed for production. Prepare a staged approach that shows what a prototype must prove before scope and investment increase.

  • Integration ambition versus system constraints

    Connecting agents to complex SaaS ecosystems, enterprise resources, and legacy applications could make a promising workflow difficult to implement reliably. Prepare to discuss how you would map interfaces and dependencies, test retrieval quality, and keep components replaceable.

  • Efficiency versus governance and credible ROI

    An inferred trade-off is that faster workflows may not produce defensible savings if measurement is weak or governance concerns limit deployment. Prepare to describe baseline metrics, post-deployment checks, and how you would involve Legal & Business Affairs and Cyber Security without treating approval as an afterthought.

03

Practice your answers

Technical practice

How would you identify where an agent could improve a complex internal workflow?

What to coverPreparation suggestion: Explain how you would map handoffs, exceptions, system dependencies, and time spent before proposing an intervention. Compare an agent with simpler automation and define what evidence would show that the change frees people for higher-value work.

How would you turn a rapid agent prototype into a production proposal?

What to coverPreparation suggestion: Describe how you would build a functional demonstration, gather business feedback, and revise the design. Distinguish what the prototype proves from the remaining work, risks, and costs needed for a production decision.

When would you use multi-agent orchestration rather than a simpler LLM workflow?

What to coverPreparation suggestion: Discuss task boundaries, prompting, coordination, and how you would verify outputs between steps. Weigh potential gains against added latency, cost, and failure modes.

How would you design retrieval for unstructured enterprise content?

What to coverPreparation suggestion: Cover curation, enrichment, retrieval quality, and how relevant context reaches the LLM. Explain how you would test whether retrieved material supports accurate answers and diagnose missing or misleading context.

How would you choose between scaling RAG and fine-tuning an LLM?

What to coverPreparation suggestion: Compare the two approaches in terms of the problem being solved, content updates, evaluation, and operational effort. The posting calls for hands-on experience with RAG at scale and/or fine-tuning, not necessarily both.

How would you connect an agent to enterprise resources and legacy applications?

What to coverPreparation suggestion: Address the stated use of MCP for enterprise resources and APIs for applications, including legacy systems. Explain how you would handle permissions, integration failures, and composability across a complex SaaS ecosystem.

What would make an AI agent production-grade?

What to coverPreparation suggestion: Describe guardrails, evaluations, and observability for accuracy, reliability, and safety. Include how you would detect failures after deployment and decide whether to revise the agent or restrict its use.

How would you design an agent deployment with Legal & Business Affairs and Cyber Security?

What to coverPreparation suggestion: Explain how you would surface data access, output, and operational risks for review with those partners. Distinguish technical safeguards you can test from governance decisions that require cross-functional agreement.

How would you measure an agent’s productivity impact and return on investment?

What to coverPreparation suggestion: Establish a workflow baseline and explain how you would track hours reclaimed, cost savings, and efficiency gains. Account for build and operating costs, adoption, and the possibility that apparent time savings do not translate into realized value.

How would you make a Buy, Build, or Ignore recommendation for an emerging media-industry AI tool?

What to coverPreparation suggestion: Frame the decision around a specific workflow friction point and a technical and functional audit. Compare expected value, integration fit, safety, composability, and budget before presenting an actionable recommendation to leadership.

Behavioural practice

Tell me about a time you aligned stakeholders on a complex workflow change.

What to coverPreparation suggestion: Use a real situation to show differing goals across business and technical groups, the actions you took to reach an execution plan, and the result. Clarify your own contribution rather than attributing the whole outcome to yourself.

Tell me about a time feedback changed a prototype or technical approach.

What to coverPreparation suggestion: Describe the initial situation, what users or business partners revealed, and how you acted on it. State the result, including what you stopped, revised, or validated before further investment.

Tell me about a time you managed scope from proof of concept toward production.

What to coverPreparation suggestion: Give a real example of the delivery pressures and expectations involved, the boundaries and priorities you set, and the outcome. Explain how you communicated work that remained before the solution could be relied on.

Tell me about a time you resolved a governance concern with cross-functional partners.

What to coverPreparation suggestion: Set out the situation, the concern raised by legal, security, or another relevant function, and the actions you took together. Describe the result without implying that you alone approved the risk.

Tell me about a time you turned an ambiguous leadership goal into a funded or prioritized plan.

What to coverPreparation suggestion: Explain the situation, how you assessed options and estimated effort or cost, and what you recommended. State the result and how you handled uncertainty or competing claims on resources.

02

Sharpen your knowledge

Topics to prepare

  • Agent architecture and orchestration

    Review when advanced prompting, a single agent, or multi-agent orchestration is appropriate; sketch decision paths and failure modes for a hypothetical internal workflow. The posting requires production-ready LLM agents and multi-agent orchestration.

  • Unstructured-content retrieval

    Diagram how content would be curated, enriched, retrieved accurately, and supplied as LLM context; explain how you would assess retrieval quality at scale. The posting explicitly requires RAG frameworks and hands-on RAG at scale and/or LLM fine-tuning.

  • Enterprise integration and composability

    Sketch boundaries between agent logic, complex SaaS workflows, MCP-connected resources, and API-connected legacy applications; identify where components could be replaced. These integrations and composable toolsets are explicit responsibilities.

  • Production assurance and governance

    Define plausible accuracy, reliability, and safety failure cases and map each to a guardrail, evaluation, or observable signal. The role builds production-grade agents and partners with Legal & Business Affairs and Cyber Security on governance.

  • Productivity economics and delivery strategy

    Work through a hypothetical prioritization using implementation costs, hours reclaimed, savings, and efficiency gains; outline a proof-of-concept-to-production roadmap. The posting calls for ROI tracking, budgets, scope management, and translating leadership goals into execution plans.

  • Media-relevant AI decisions

    Practice a concise Buy, Build, Ignore assessment of a hypothetical AI tool for a media-workflow friction point, stating assumptions and audit criteria. The role calls for media-industry insights and actionable leadership assessments; the particular workflow is only a practice scenario.

Skills to revise

  • Analyze and prototype a workflow

    Map a hypothetical cross-functional workflow, select one agentic intervention, and build a small functional automation using a posting-named AI-augmented development tool such as Cursor, Replit, or Claude. Rehearse incorporating business feedback and estimating production effort; rapid prototyping is explicitly required.

  • Implement retrieval-backed agent behavior

    Using sample unstructured documents, build a small RAG agent that curates source content, retrieves relevant passages, and checks whether responses reflect the retrieved context. This practices the posting's hands-on agent and RAG requirements without implying a specific employer dataset.

  • Connect agents to enterprise interfaces

    Create a small illustrative agent integration through MCP and an API adapter; document input validation, error handling, and how a legacy application could be isolated behind the adapter. The posting explicitly names MCP, APIs, and legacy-system integration.

  • Test and observe agent outputs

    Assemble a small test set with expected outcomes and unsafe or inaccurate cases; run evaluations, record failures, and describe the signals you would monitor after deployment. This exercises the stated guardrails, evaluations, observability, and safety responsibilities.

  • Present an execution decision

    Prepare a one-page hypothetical business case with cost assumptions, an hours-reclaimed calculation, stakeholder checkpoints, a scoped roadmap, and a Buy, Build, Ignore recommendation. This practices the role's budgeting, ROI, stakeholder-management, and leadership-advisory duties.

04

Your preparation checklist

  • Map evidence to the core requirements

    Prepare a one-page evidence map with specific examples, where available, of enterprise integration, complex SaaS architecture, workflow automation, production LLM agents, RAG at scale or fine-tuning, and stakeholder leadership. The posting specifies these areas; do not claim experience you cannot substantiate.

  • Rehearse a production project walkthrough

    Choose a relevant project you can discuss. Prepare a short account of the workflow, your hands-on and leadership decisions, architecture, integrations, stakeholder feedback, production outcome, and measured results. Separate your contribution from the team’s.

  • Practice diagnosing a productivity workflow

    As a preparation exercise, select a hypothetical media-business workflow and sketch its current steps, bottlenecks, and an agentic intervention. State assumptions rather than presenting the scenario as an A+E project; identify what business feedback would change your design.

  • Draw an agent and retrieval architecture

    Prepare a diagram showing where prompting, multi-agent orchestration, and curated unstructured-content retrieval fit. Include proposed MCP access to enterprise resources, API connections to applications or legacy systems, and choices that keep the toolset composable.

  • Plan a rapid prototype demonstration

    Outline a small functional automation you could explain or demonstrate, including how AI-augmented coding tools helped, what the prototype proves, what feedback it needs, and what remains before production. The posting emphasizes rapid delivery and refinement, not a specified interview exercise.

  • Define a production-readiness review

    Prepare a checklist of guardrails, evaluation cases, observability signals, and failure handling for accuracy, reliability, and safety. Show where Legal & Business Affairs and Cyber Security would review governance decisions; do not assume their specific policies.

  • Build a roadmap and ROI sketch

    Draft a phased path from proof of concept to production with scope decisions, stakeholder checkpoints, cost-estimate assumptions, and a budget range. Explain how you would track hours reclaimed, cost savings, efficiency gains, and ROI to prioritize workstreams.

  • Prepare an industry assessment and employer questions

    Create a brief hypothetical Buy, Build, Ignore assessment for an AI tool relevant to media workflows, with technical and functional audit criteria. Bring questions about which workflows are priorities, available integration constraints, governance review, and how success is measured.

AI-generated from the job information · Prepared Sep 30, 2026 (UTC)Useful preparation, not a guarantee of eligibility or an offer.

Availability last checked: Nov 4, 2026. Status can change after a check; confirm on the employer’s website. Report an issue · Our checking policy

KEEP EXPLORING

Similar AI jobs

Related skills and specializations in United States. Matched to this role, not your profile.

Explore more jobs
Finding similar opportunities…