We're looking for a Director, Data & Technology
ROLE OVERVIEW:
The Director, Data & Technology leads two pods at Intercept. The Platforms pod builds and runs InterceptOS, the internal platform our teams work in, and PartnerOS, the client-facing side of that platform. The Data & Analytics pod produces the insights, data assets and context that inform our strategies and campaigns. You own the roadmap, the delivery and the people in both.
The second half of this job is building our data capability. Our clients sell to IT and business decision-makers, and the better we understand those audiences, the better our strategies and creative work perform. Your job is to build that understanding: find and acquire new data assets, decide what we can responsibly do with them, and turn them into intelligence our strategy and creative teams work from. You report to the CTO and present the state of both pods and the data roadmap to the executive leadership team.
Responsibilities:
- Lead the Platforms pod: Own the roadmap, delivery and reliability of InterceptOS and PartnerOS. You work with stakeholders across the business to decide what gets built, what gets bought, and what gets retired, and you are accountable when the platform our teams and clients depend on is not working.
- Lead the Data & Analytics pod: Own the insights, data assets and context that inform our strategies and campaigns, so account and strategy teams start from evidence rather than instinct. You set the standard for what a defensible insight looks like before it reaches a client, and you help turn our data assets into commercial offerings.
- Make PartnerOS something clients choose to use: Work directly with clients and account teams to understand what they need from the platform, then turn that into a prioritized roadmap rather than a backlog of one-off requests.
- Acquire new data assets: Identify, evaluate and bring in new first-party and third-party data sources. You run the vendor evaluation, you judge whether the data is accurate enough to build client strategy on, and you negotiate the terms we can actually work within.
- Build out the data offering: Turn raw data assets into the insight and context our strategy, creative and account teams work from, and shape how that capability shows up in what we offer clients. You are responsible for the offering existing, not just for the pipelines behind it.
- Own data governance and privacy: Set how we collect, store, use and retain audience data, and keep us compliant with PIPEDA, CASL and GDPR where client work reaches the EU. Enterprise clients audit this, so it has to hold up under review.
- Set the technical direction: Make the architecture and build-versus-buy calls for InterceptOS, PartnerOS and the data stack underneath them, and document the reasoning so the decisions survive after the meeting.
- Hire and grow both pods: Own recruiting, interviewing, onboarding and development for Platforms and Data & Analytics. You decide who joins and how the teams are shaped as the work grows.
- Report to the executive leadership team: Provide portfolio and progress updates across both pods and the data roadmap, including where you need investment and where you are at risk.
- What Success Looks Like:
- By 90 days: You understand both pods, the current state of InterceptOS and PartnerOS, and the data assets we already hold, and you have given the CTO a prioritized assessment of what to change.
- PartnerOS adoption grows: Clients use the platform regularly, usage increases over time, and account teams present it as part of Intercept's offering.
- InterceptOS reduces manual effort: The internal platform measurably reduces manual work for delivery teams, and you can name the specific processes it replaced.
- New data assets are live and defensible: The data sources you brought in are in production, accurate enough to build client strategy on, and covered by terms our legal and client teams have approved.
- Data informs client work: Strategies and assets reference insights produced by the Data & Analytics pod, and the pod is consulted during planning rather than after it.
- Governance withstands client review: How we source, store and use audience data is documented, and that documentation passes enterprise client audits.
- Delivery is predictable: Both pods meet the dates they commit to, and risks to dates are raised early with a mitigation plan.
Qualifications:
- Six or more years in data and technology roles: with at least three of those years leading teams, including hiring, performance conversations and development.
- Experience owning a platform or product end to end: not only delivering features against someone else's roadmap. You have decided what to build and lived with the consequences.
- A hands-on data background: covering pipelines, warehousing, data modelling and SQL. You can review a data model and say what will not scale.
- Experience sourcing or licensing third-party data: including how you judged data quality, what you rejected, and how you handled the commercial terms.
- Working knowledge of privacy and data governance in a marketing context: specifically PIPEDA and CASL in Canada, and GDPR where campaigns reach the EU.
- Commercial judgment: you can build the business case for a data investment and explain it to people who do not care about the technology.
- B2B marketing or martech domain knowledge: you understand how demand generation, ABM and campaign strategy actually work, ideally from agency or enterprise technology marketing.
- Clear communication with non-technical stakeholders: because you will spend as much time with sales, client services and executives as with engineers.
- Comfortable working fully remote across a distributed team, with occasional travel for client and team meetings.
