You will own the build on two or three engagements: the data layer, the enrichment logic, the sending infrastructure, the CRM wiring, and the reporting that tells everyone whether it worked.
The engagements are structured so that the client eventually runs the system themselves. That constraint shapes everything: you are not building the cleverest possible machine, you are building the one an operator can still maintain in a year.
What you will own
Clay workspaces: enrichment waterfalls, scoring, segmentation and routing
Sending infrastructure: domains, inboxes, warmup, rotation and the monitoring on top
CRM wiring, usually HubSpot, including the object model and the reporting built on it
Automation that connects the pieces, in n8n or in code where it needs to be
Documentation good enough that handover is not a crisis
What we are looking for
You have built at least one outbound system yourself, not just operated somebody else's
Strong Clay. If you have not used it, you have used something comparable and can learn it fast
You understand why deliverability is a systems problem rather than a copy problem
You are comfortable in APIs, webhooks and enough scripting to unblock yourself
You would rather ask a client an uncomfortable question early than discover the answer in month three
What this is not
Not a list-building role. Enrichment is one part of the job, not the job.
Not siloed. You will see the whole system rather than a slice of it, which is the point.
Not a place to learn the basics. The team is small and everyone is expected to ship independently.
How to apply
Send your CV or profile and a few lines on what you have built to contact@kinetyca.com, with GTM Engineer in the subject line.
One of the founders reads every message. We do not use a recruiter and there is no application form.
AT A GLANCE
TypeFull timeLocationREMOTERegionEUROPE OR USLevelSenior
Kinetyca GTM NewsletterNews, cases and what is actually working in GTM right now.