What that looks like day to day
You’ll work closely with BDRs, AEs, Customer Success, Marketing and GTM leadership to understand how work actually gets done: where people are spending time on repetitive tasks, where data or context gets lost between systems, and where the tools we have are getting in the way.
From there, you’ll work out what the right solution is. Sometimes that will be an automation or integration. Sometimes it’ll be an internal tool, an AI workflow, or a piece of software you build yourself. Sometimes the right answer will be simplifying a process or getting rid of a tool entirely.
You’ll spend plenty of time building, but this isn’t a role where requirements arrive neatly packaged. You’ll talk directly to the people using what you make, understand the underlying problem, ship something, and follow up to see whether it actually helped.
You’ll also take a broader view of our GTM systems. You’ll understand how data and workflows move between tools, make decisions about where logic should live, and help us evolve the stack as the company changes. We want systems that are understandable and dependable, rather than a collection of one-off automations that happen to work today.
And you’ll own what you build in production. If an integration breaks or a workflow behaves strangely, you’ll debug it, fix the underlying problem, and improve the system around it. Supporting the revenue team is part of the feedback loop, not a separate ticket queue.
AI is already a normal part of how we work, and there’s a lot of opportunity to use it here. We’re interested in where agents and models can genuinely improve a workflow, as well as where conventional software is still the better answer. You’ll have room to experiment, measure what works, and turn the useful parts into things people can depend on.
Who you are