GTM Engineer

The role

WarmUp is a growth-engineering firm. We put an engineer inside a client's team, in their Slack, their standup and their CRM, and build the system that finds and reaches the right accounts. Everything is built in accounts the client owns from the first day, and we run it with their team until they can run it themselves.

You will be that engineer for a small set of B2B clients. You decide what the system should do with the client, build it, run it every week, and show what it produced. The rest of the firm runs the paid media, LinkedIn content and RevOps for the same clients, so your work feeds theirs and theirs feeds yours.

The role is remote, with working hours that overlap US Eastern time.

What you'll do

• Work out with each client who they sell to, which accounts matter, and what has to happen at an account before a message is worth sending.
• Build the tables and workflows in Clay that find those accounts and people, enrich them across providers, score them and write the first line.
• Write your own scrapers, scripts and agents in Claude Code when the data a play needs is not for sale.
• Launch and run sequences in Instantly and HeyReach, and keep the sending domains healthy.
• Wire every send, reply and meeting into the client's HubSpot or Salesforce, so each meeting traces back to what started it.
• Document the system as you build it, and train the person on the client's team who will take it over.
• Join the client's standup and report each week on what ran, what it produced, and what changes next.

What we look for

• You have built and run outbound for B2B companies yourself, and can show what it produced.
• You know Clay well: waterfalls, AI research columns, scoring and written personalisation.
• You build with Claude Code or something like it, and the command line does not slow you down.
• You can describe one account signal you built a campaign on, who it fired on, and the message it produced.
• You can set up email sending from scratch and keep it out of spam once volume starts.
• You have worked directly with founders or revenue leaders at growing companies, and can hold a straight conversation when results are bad.
• You write plainly, because the person who takes over your system has to understand it without you.