GTM Systems Associate

The role

This is a Revenue Operations role built for the AI-native era. There's still real CRM work day to day: configuration, support, fixing what breaks, keeping the system governed. But we'd want you to treat the manual side as a backlog to automate down over time, not as the job. The goal is a regional revenue engine that stays stable while getting steadily faster.

If you already reach for Claude or Claude Code before a checklist, you'll fit in well here.

You’ll report to the Head of Revenue Operations and work closely with GTM Engineering. Your job is to keep the regional revenue engine running fast and clean, so the region can move quickly without the global system drifting out of shape.

Your region covers our in-timezone expanding markets, including Europe and South Africa. Some of this is keeping existing markets running cleanly. Some of it is helping build out the ops layer in markets where the process is still maturing.

• Run the regional revenue stack. Maintain Hub Spot and the adjacent tools (Clay, Gong, outbound platforms, enrichment, CPQ/CLM) for your region. Configure pipelines, lifecycle stages, routing and workflows within the global guardrails. Be the in-time-zone point of contact for Sales, CS, Marketing and Finance on anything system-related, and fix issues quickly and properly.

• Support the Mar Ops side. Back up the field marketing team on the automation and systems work behind their campaigns. Keep the data flowing cleanly between Marketing and Sales, and make sure the handoff works for both sides.

• Automate where it makes sense. Turn recurring manual work into AI-assisted workflows over time. Not everything needs automating, and not on day one, but the instinct we're looking for is to keep asking which tasks still deserve to be manual in three months.

• Keep data clean, especially forecast data. Hold CRM data integrity through a mix of automated checks, AI-assisted enrichment and basic discipline. Catch routing errors, lifecycle drift and queue-health problems before reps run into them. The forecast fields matter most: close dates, stage accuracy and deal amounts that leadership and Finance rely on every week.

• Govern without becoming a bottleneck. Hold the line on lifecycle rules, territory logic and field standards. Support deal desk and CPQ/CLM workflows on the system side, while Legal owns the contract logic. Set up a structured way for the region to raise requests so it doesn't turn into an ad-hoc queue. Document what matters, and give people a heads-up before anything changes underneath them.

• Close the loop with Global Rev Ops and GTM Engineering. Flag what's working regionally so it can be rolled out more widely, and flag what's broken so it gets fixed properly at the system level rather than patched locally.

• Strong CRM operator. Confident with pipelines, lifecycle, routing, workflows, permissions and reporting in a fast-growing company.

• AI-native by default. You use Claude or similar tools daily and have a good sense of what they can and can’t do reliably. You don’t need to be a trained engineer, but you should be someone who tries to build or automate a solution before defaulting to manual.

• Tool-fluent across the GTM stack. Working knowledge of Clay, Gong, outbound platforms, enrichment tools and how they connect.

• Systems thinker. You understand how a config change in Hub Spot plays out downstream in forecasting, attribution and rep behaviour.

• Owns the outcome. You care whether the system actually works for the region, not only whether the setup is technically correct.

• Calm under load. You triage quickly, stabilise fast and fix properly. A broken workflow the night before a Q  doesn’t rattle you.

• Commercial bias. You care whether the work moves pipeline, and you check that before shipping.

• Clear communicator. You document decisions simply, push back when a request should be a workflow, and can hold your own with an AE or a senior Rev Ops leader.

• A pure CRM admin role. When something repetitive comes up, your first instinct is to remove the work, not do it faster.

• A reporting analyst role. Dashboards are an output here, not the…