Program Management - Program Manager III

Program Manager, Audience Identification

Seniority: Senior program manager - expected to operate independently and own a workstream end to end
Reports to: Team Lead, Partner Acquisition
Duration: 6 months
Location: Remote
About the role

We are hiring an experienced contingent program manager to build and operationalise how our team identifies and reaches potential partners using licensed third-party audience data sources.
Today this capability runs as a largely manual, lightly integrated process: data is held in disconnected spreadsheets, aggregation and consent capture are inconsistent, and records are not retained in a durable, reusable structure. There is a clear opportunity to turn this into a documented, repeatable capability that multiple internal teams can use.
This is a senior, end-to-end program management role. You will set the point of view on how the organisation uses third-party data, own the cross-functional program that turns it into a documented capability, and represent the team credibly with product, analytics, tooling and external data vendors.
Minimum qualifications

Senior program or operations management experience, including ownership of a cross-functional program with real dependencies (not a task queue).
Experience setting direction in an ambiguous space and building process while running it.
Strong data fluency : enrichment, matching, dedupe, field normalisation and QA at volume.
Demonstrated vendor management experience - holding a commercial relationship to a spec and timeline, plus contracting and invoicing exposure.
Privacy and consent fluency : experience in environments where data privacy and opt-in/consent management are foundational to data handling.
Experience influencing product, analytics and technical partners without formal authority, and communicating credibly with senior stakeholders.
Excellent written documentation habits; the durable output of this role is process and playbook.
Preferred qualifications

SQL familiarity.
Experience with CRM or marketing automation platforms.
Experience standing up a data capability that was later adopted by multiple teams.
Key partners

Operations, Analytics, Product, internal tooling teams, adjacent business teams, external data vendors
Responsibilities

Own the third-party audience identification program

Own the program end to end: roadmap, milestones, dependencies, risks and stakeholder communication, with a regular readout to the team lead.
Set the point of view on how the team uses its third-party data vendor set, and bring strategic oversight to vendor usage that today happens in a decentralised way.
Act as the single decision point for prioritisation across competing internal requests.
Propose new vendors based on business priorities and industry trends; manage vendor relationships commercially and operationally - holding vendors to spec, scope, timeline and quality, navigating contracting conversations and managing invoicing.
Build the process, guardrails and data foundation

Define and document the end-to-end process for each vendor: request intake, enrichment, QA, hand-off and storage.
Establish how records are aggregated and retained, and how consent is captured and tracked, resolving current gaps in data retention.
Set guardrails for appropriate vendor use, with clear escalation paths for exceptions.
Move audience data out of disconnected spreadsheets into a consolidated, reusable structure with consistent fields and definitions that serve multiple internal teams.
Partner with analytics and tooling teams on the integration points that make the capability durable rather than dependent on individuals.
Drive expansion and cross-functional adoption

Onboard additional internal teams and use cases onto the process as it stabilises.
Lead evaluation of prospective vendors using a consistent test structure, ending in a clear recommendation.
Feed cost, volume and efficiency inputs into the team's acquisition efficiency reporting.
Represent the team in relevant cross-functional forums on audience data.
Leave behind a durable capability

Produce the documented playbook, definitions and operating model so the capability survives the engagement.
Make a recommendation on what a permanent version of this role should own.
What this role is not

Not an analytics build role - audience sizing sits in a separate workstream, though this role coordinates with it.
Not a tooling-team representative role.
Not a pure execution seat; day-to-day request throughput is part of the job, but the expectation is program ownership.

J-18808-Ljbffr