Job Opportunities API

The Public Ledger of Openings

← Back to the ledger

Director, AI Orchestration

Togetherwork
CompanyTogetherwork
CategoryData & Analytics
LocationTW Corp - Product
RemoteOn-site (inferred)
EmploymentNot stated
LevelDirector
SalaryNot stated by the employer
Posted26 Jun 2026
Last verified7 Aug 2026
SourceEmployer ATS (greenhouse)
Applications are handled by the employer, not by us.Apply on the employer's site →
Description
Department:  Product & Strategy Reports To: Chief Product Officer Location: Austin, TX (Hybrid Required 2-3 days/week)   Work Authorization Notice: At this time, we are unable to provide immigration sponsorship for this position. Candidates must have current, and future, unrestricted authorization to work in the country where the role is based. Overview At Togetherwork, we set a high bar for clarity, collaboration, and execution. Our Product & Strategy leaders own portfolio outcomes across a 15+ product portfolio serving associations, faith organizations, and fraternal groups. We work in deep partnership with Engineering, Revenue, CX, Operations, Managed Services, and Support, sharing accountability for delivering stable, modern, insight-driven products that help our customers thrive. Role Summary The Director, AI Orchestration owns the system that makes Togetherwork AI-native. The core of the job is replacing manual work with agentic workflows across the company, so people spend their time on the judgment, relationships, and decisions where humans matter most. You will set the agent standards every team builds to, run agent governance so we move fast without taking on excess risk, and measure whether the work is changing how the company operates. The operating model is hub and spoke. You are the hub. Each ELT member assigns Builders from their function to an AI guild that you help organize: a cross-functional community that builds on shared standards and tooling. You will run hackathons to map our cross-functional workflows piece by piece and test what level of agent orchestration each one can handle, from simple assistance to full agentic replacement. The wins get hardened into production workflows; the standards get updated with what we learn. Critically, this is a change management role as much as a technical one: you will need to bring people along, shift how work gets done, and build the organizational will to operate differently. This is a business orchestration role, not an engineering role. The right candidate has personally built agent-based workflows using low-code and no-code orchestration tools and AI platforms, understands cross-functional business processes, and can spec technical work for engineers without writing production code themselves. You report to the AI Council Lead day-to-day on overall strategy and priority. You partner closely with the CTO on tool approval, with the CTO's security leader on tool security review, and you partner with the CPO to run the AI Governance Council and prioritization. Success is measured in replacement and/or augmented workflows, adoption across functions, and dollars of cost saved or revenue generated. Key Responsibilities Knowledge Infrastructure Own the vision and ongoing curation of Togetherwork’s enterprise knowledge infrastructure (in coordination with the CTO and security team): the system that brings together product signals, support data, customer trends, and operational knowledge so agents and humans across every function can draw on it reliably. Define standards for how each function contributes to and maintains its knowledge domain, so the infrastructure stays current and accurate as the business evolves. Measure knowledge infrastructure health: coverage, freshness, retrieval quality, and actual usage by agents across the company. The brains exist to feed the agents; the agents are the point. Agent Standards & Tooling Set the standards every team builds agents to: design patterns, quality bar, human-in-the-loop checkpoints, testing, deployment, and retirement. Select and run the shared agentic tooling the company builds on, staying tool agnostic where possible and documenting the tradeoff whenever lock-in is the right call. Keep standards current as tooling and model capabilities change, and retire patterns that stop earning their place. Define how agent quality is measured be