Our CDP is live on Databricks and activating audiences to multiple channels. The identity-resolution model you built handles deterministic and probabilistic stitching across our ecosystem and brand portfolio.
AI agents draft audiences, briefs, copy variants, and stakeholder reports - and you've measurably raised the quality of their output by owning the human in the loop QA. When a user triggers an event, that signal reaches every activation channel within four hours.
The global and talent marketing teams across the regions activate new campaigns by themselves. Direct sourcing audiences are live and we can measure bid to placement uplift by segment.
The spike we're hiring forWe don't need a generalist. We need a senior operator unusually good at one thing: orchestrating identity, audiences, and activation on a Databricks native data platform - writing the PySpark and SQL that makes it work - while raising the bar on an AI agent layer that drafts work for you.
Why this role existsHeadFirst Group is building a new function from scratch, inside the Product organisation. The objective is to leverage our data fast, to enable product led growth across our marketplaces and brand portfolio, starting with direct sourcing / direct fulfilment activation, global campaigns by job category, and personalisation at scale.
This is not a marketing campaign role. The global marketing team and the talent marketing teams across the regions own content, channels, and campaign execution. You provide the data foundation, activation tooling, and experimentation capabilities that let those teams scale performance consistently.
You are the first hire into the team. Your manager runs strategy, architecture, vendor selection, stakeholder politics, and the agent roadmap. You own the activation layer - config, identity, events, and the day to day quality of what ships out of the agents.
How your time splitsCDP configuration and audience design - 50%.
Identity resolution and event taxonomy - 25%.
Event tracking across our platforms - 15%.
Agent QA and prompt iteration - 10%.
By the time you start, three agents are already live in production. Five more come online in your first six months. They draft audiences, briefs, copy variants, segmentation logic, prioritisation calls, and stakeholder reports - the kind of work that used to consume a team.
Your job is the 20% of judgement those agents can't do: identity calls, consent decisions, and the call on whether an agent's output is good enough to ship. You are the human in the loop on every QA cycle. If you read "AI agents draft your work" and feel relief, this isn't your role.
What "good" looks like to usWe hold ourselves to the bar of teams that have publicly figured out warehouse native MarTech: composable stacks, the GTM engineering shift, operations as orchestration. We notice when a marketing engagement tool list quietly drifts away from the rules we defined for it. We argue about identity stitching. We think a Job Description should be a stake in the ground, not a checklist.
What you bring/What you can show usA reverse ETL flow you shipped to production. Not training; production.
A dbt model you wrote and got merged into production. Not a course you took - code that shipped.
A PySpark job you shipped to Databricks production - pipeline code, not a notebook demo.
An identity resolution decision you made - deterministic vs probabilistic, with the trade off you accepted and what broke later.
One example of correcting AI drafted output that would have shipped wrong, with what your judgement caught.
Data platform: Databricks
CDP / activation: Hightouch / GrowthLoop
ESP: HubSpot for B2B, Braze / Iterable under evaluation for Business to Talent.
CMS: Sanity headless.
What we offer