Platform Engineering (platformengineering.org) is home to the world's largest community of platform engineers. Through PlatformCon, one of the world's largest conferences dedicated to platform engineering, we bring together more than 50,000 engineers, technology leaders, and decision-makers every year. Alongside our events, we run a university, a newsletter read by hundreds of thousands of engineers, a growing YouTube channel, and Weave Intelligence, our research arm.
We are looking for a Head of Revenue Operations & Systems to own operations end to end: our growth-ops and CRM data layer, the tool stack, event & ticketing infrastructure, and performance-marketing data, the systems and processes that let the rest of the company scale. Today, growth ops and internal tooling run on a mix of point-to-point integrations and manual fixes that have carried us this far but won't carry us through the next stage. We are already improving parts of this, you will be picking up that momentum and driving it the rest of the way, not starting from a blank slate.
This is a management role from day one. Two people already work in ops, one on revenue ops and one on tooling and custom software, and they will report to you from the start. You will be hands-on yourself too: building pipelines and workflows directly, not just directing others to. You will join the Platform Engineering Masters leadership team, reporting to Luca, Managing Director of Platform Engineering Masters, alongside peers like the head of revenue and the head of growth.
Replace the current patchwork of Zapier point-to-point integrations with a proper operational data layer, so that fixing one connection doesn't mean detective work across a dozen fragile Zaps.
Own enrichment, deduplication, and lead scoring in our CRM (HubSpot), currently unowned and blocking the marketing team from running effective campaigns.
Give non-technical team members self-service access to their own data and segments, instead of routing every query through engineering.
Connect ad spend to actual outcomes: get click and conversion data from our ad managers (LinkedIn, Google, Meta) flowing into HubSpot so campaign performance can be measured and fed back into targeting.
Own our tool stack: build and maintain a registry of every tool in use (technical owner, business owner), lead the retirement of Airtable, and run tool-selection decisions as a cross-functional process, not a unilateral ops call.
Stabilize ticketing and webinar operations ahead of high-volume periods, our two biggest scale risks right now.
Manage and grow the ops team: one person on revenue ops and one on tooling and custom software report to you from day one, and you will assess where further hiring is needed.
Run operations reporting to a predictable calendar, feeding into the company's quarterly budgeting process.
Hands-on engineering skills: you design and build data pipelines and workflows yourself, in SQL and code, not just through no-code tools or by directing someone else to.
Experience building performance marketing / ad-tech systems: conversion tracking, click-ID matching (LinkedIn, Google, Meta), attribution pipelines, and getting that data to actually land in a CRM correctly.
Experience with CRM systems (HubSpot or equivalent) at a technical level: custom objects, workflows, API integrations, not just day-to-day admin use.
Solid data modeling and architecture skills: comfortable designing a schema in Postgres/Supabase and deciding what belongs in a warehouse versus in the CRM itself.
A track record of making tooling decisions that account for the whole team's needs, not just what's easiest to build.
People management experience. You will be managing two people from your first week.
Comfortable picking up a system that's already partway improved and driving it forward, rather than needing a blank slate to start from.
Experience with no-code/low-code automation tools (n8n, Zapier), and knowing when to replace them with something more robust.
Familiarity with ad platform APIs (LinkedIn Marketing API, Google Ads API, Meta Conversions API) and server-side tracking approaches (e.g. Conversions API vs. pixel-only).
This is a role to take an operations function that's already moving in the right direction and drive it the rest of the way, not a maintenance job, and not a blank-slate build either. You would be walking into a company that knows exactly what's broken and is ready to invest in fixing it properly, with a small team already in place, direct access to leadership, and the mandate to build the operations function the company needs for its next stage of growth.
