About you
The GTM Systems Engineer at LiveKit owns the infrastructure layer that makes the entire revenue engine work — and builds the automation and agentic workflows that run on top of it. Systems engineering is at the core of this role, but it doesn't stop there. You're equally comfortable architecting Salesforce as a trusted source of truth and building the outbound workflows, enrichment pipelines, and AI-driven automations that help the GTM team move faster and smarter.
Salesforce is our system of record – it holds the bulk of our GTM data and is the source of truth for revenue, pipeline, and customer data. HubSpot is our marketing layer for campaigns and lead gen, and what it captures needs to flow cleanly and reliably into Salesforce. Both systems are in place. What we're building now is the engineering layer that makes all of it trustworthy and intelligent: real change management, observable pipelines, data models built for AI consumption, and agentic workflows that act on GTM signals at scale.
You understand the difference between owning a system and gatekeeping one. Sales lives in Salesforce. Marketing lives in HubSpot. Your job is to make sure both are governed well enough that others can work in them effectively — and powerful enough that the GTM team can do things they couldn't do before.
You'll thrive as a GTM Systems Engineer if you
- are known as the go-to person for tackling tough technical problems
- can clearly explain complex technical concepts to others
- you believe systems should be managed with engineering discipline
- work hard and can build and ship fast
- are a fast learner, frequently picking up new languages and tools
Who you are
- Deep, hands-on Salesforce expertise — you understand the data model, have built complex flows and automation, and you think about it as an engineering system, not an admin tool. This is the primary bar.
- HubSpot experience in a marketing context — you've owned or operated it for campaigns and lead gen, and you've managed the HubSpot-Salesforce sync, including what breaks and why.
- Integration engineering experience – you've built and/or maintained integrations using APIs, webhooks, and event streams, and you've handled what happens when they break silently.
- Technical depth beyond the UI – you're comfortable with APIs, webhooks, and scripting, and you know when a native tool (a Flow, a Clay table, a HubSpot workflow) is the right answer versus when it's time to write code.
- Agentic workflow experience – you've built or extended AI agent workflows that act on GTM data. Not "we used AI tools" but actually designed and deployed agents in production.
- Strong change management practices – you've managed deployments in live systems where a mistake breaks active deals or campaigns.
- Comfortable partnering with Sales and Marketing stakeholders directly — fluent in both worlds, able to translate their needs into system requirements without becoming a bottleneck.