Director of Go-to-Market Engineering (Revenue Operations)

• Define Perk's GTM engineering architecture - how CRM, enrichment, signal, sequencing, orchestration and data layers fit together.

• Make the tooling calls: what we adopt, what we consolidate, what we retire, and why it pays for itself.

• Set the roadmap with the VP of Revenue Operations, Sales leadership, and the Revenue Systems and Data teams.

• Establish the standards the team builds to - version control, documentation, testing, and rollback.

• Design and build in Clay: tables, waterfall enrichment, AI columns, webhooks and API integrations in production.

• Own the orchestration layer - the logic deciding which records enter a workflow, when, and on what criteria. This is where GTM automation succeeds or fails.

• Build agentic workflows on modern LLM and agent tooling to take research, qualification, summarisation and data entry off people entirely.

• Write the code the job needs - Python, SQL, SOQL or TypeScript.

• Own account prospecting automation globally: TAM sourcing, enrichment, ICP and intent scoring, prioritisation and distribution.

• Give AEs their selling time back - CRM autofill, quoting, meeting prep, opportunity hygiene, first outbounds.

• Build account intelligence for Account Management: risk signals, whitespace, account planning.

• Take each project from prototype to production properly - instrumented and validated before it scales.

• Turn commercial problems into technical architecture, and technical output into impact a revenue VPs recognises.

• Understand Perk's revenue goals and how to leverage AI capabilities for us to achieve them quicker and more efficiently.

• Understand and drive clear and tangible commercial outcomes. For example, how to reduce the time that quota-carrying roles spend on non-core activities such as account research, be able to quantify the impact, and clearly communicate the outcomes to leadership.

• Lead and grow a small, senior team across Europe and North America.

• Set clear ownership, and the review discipline that makes shipping fast also means shipping safely.

• Grow the team's technical depth and commercial judgement in equal measure.

• Deep background across Revenue Operations, GTM Engineering, Sales Systems, Growth Engineering, or an adjacent technical commercial function in B2B SaaS

• Proven track record in GTM Engineering specifically, with delivery at real scale — systems hundreds of sellers relied on, not a pilot for one team

• Time as both a builder and a leader. This role needs both.

• Clay expertise in production - complex tables, waterfall enrichment, webhook integrations and AI column logic that revenue teams actually depended on.

• Deep Salesforce fluency: the data model, integration patterns, and where the constraints really are.

• Working proficiency in code — Python, SQL, SOQL, TypeScript or equivalent. You pull your own data. Not all coding languages are necessary, but proficiency in one or some is required.

• Architecture instincts: you build for scale, monitoring and recovery, not just for the first successful run.

• Depth across several layers of the modern GTM stack - enrichment and data (Apollo, Clearbit, ZoomInfo, Cognism, PredictLeads), signal and intent (6sense, Bombora, UserGems), sequencing (Outreach, Salesloft), orchestration (n8n, Make, Workato), data infrastructure (Snowflake, dbt, BigQuery) and LLM and agent tooling. Nobody has all of it. We care that you have real depth somewhere and can learn the rest quickly.

• You judge your work by whether it moved a commercial metric, not by whether it shipped.

• You have the credibility with Sales leaders to scope the right build - and to say when automation is the wrong answer.

• You understand the funnel end to end: TAM, ICP, pipeline generation, conversion, expansion, and the economics underneath.

• Having stood up a GTM engineering function at a high-growth SaaS business, ideally above $100M ARR.

• Experience taking an automation programme from pilot to global production, including what you learned when it got bumpy.

• Multi-region GTM experience across EMEA and North America.

Why This Role GTM Engineering is a discipline being written right now, and most companies are still treating it as a tooling function. This is the chance to own it properly, the stack, the architecture, the build, and the commercial outcome across a $300M+ revenue business with 800 people in the field, a genuine appetite for automation, and the budget and executive backing to move fast. You would be the first person in this seat, with real systems and real data to work with rather than a blank page, and the freedom to decide what Perk's automation layer should look like. There is a lot to go after, the problems are interesting, and the impact is immediate and visible. If you want to build the automation layer of a commercial engine at this scale and you want to still have your hands on it come and build it here.