Go to market engineer (Data only)

About the role

You build and run the outbound machine for [5–10] client accounts: the list, the sending infrastructure, the campaigns and the automation underneath. Then you improve it every week.

Every account pairs a GTM Engineer with a Strategist. The Strategist decides who we target and what we say. You make it real, and you make it run without being babysat.

Most people in this seat get handed a pile of tools and a queue of tickets. Here you get a system that already works, built in Claude Code and Codex, and every fix you ship gets reused across the whole client base.

This is not an entry-level role.

• Reports to: Cameron (Founder)
• Location: Remote, anywhere, with at least 4 hours’ overlap with US Eastern working hours
• Compensation: $1,500–$4,000 USD per month, depending on experience
• Bonuses: Tied to results across your accounts

About The GTM Company

The GTM Company is an outbound agency for B2B companies. We build the list, write the offer and the copy, set up the sending infrastructure, and automate everything underneath so it runs every week without being babysat.

Our clients include some of the fastest-growing venture-backed startups, from Y Combinator and Antler companies to startups backed by other leading VCs and accelerators.

• We’re an early-stage company of 6 people.
• We’re growing revenue 20–50% month on month.
• New clients onboard every single week.
• We have a refined process for taking a new client from onboarding to results.

We’re an AI-first agency. Every process runs in the terminal through Claude Code and Codex. Research, lists, offers, copy and campaigns are built there with our own internal skills, not clicked together across a dozen tools. If something happens twice, it becomes a skill or an automation. This is central to how we work, and you’ll be working this way from day one.

What you’ll do

• Build every account. Turn the Strategist’s plan into a live list using custom scraping, enrichment and signal scoring, based on real evidence about who buys.
• Own deliverability. That covers domains, inboxes, inbox rotation, warmup, and matching how we send to each prospect’s email provider.
• Launch on Mondays. New campaigns and this week’s experiments go live every Monday. Nothing ships until it runs reliably on its own.
• Automate the work underneath. Build n8n flows, CRM sync and reply routing.
• Fix what breaks before the client notices.
• Report every Friday on what ran, what it returned and what we learned.
• Build the system. Turn every repeated task into a Claude Code skill or automation, and ship it back into the shared system so every Engineer and account benefits.

What you won’t do

• Sell. Clients are closed before they reach the team.
• Own the client relationship. Your Strategist owns client communication and strategy, so you can focus on the build. You’ll join calls when the technical detail matters.

You must have

• Hands-on experience running real B2B outbound, and the ability to explain why most of it fails.
• Clay or a similar tool, used day to day.
• Technical enough to read an API doc, debug a webhook payload and write a small script when you need one.
• Comfort working in the terminal with Claude Code or Codex, or the ability to get there fast.
• Experience running several accounts or projects at once without dropping any of them.

You’ll stand out if you

• Have already built your own Claude Code skills or automations
• Use EmailBison, Instantly or Smartlead
• Use n8n or Make
• Have an agency or founder-led GTM background

How you work

• You’d rather build the machine than do the work twice.
• You use AI to do the actual work, not just to write subject lines.
• You notice when something breaks, and you fix it before anyone asks.
• You don’t need managing into motion.
• You explain technical problems clearly to your Strategist and the founder.

How we measure success

• Campaigns launched on time
• Deliverability health: bounce rate, inbox placement and warmup scores
• Positive reply rate across your accounts
• Experiments shipped per account per week
• Reusable skills and automations shipped back into the system

Your first 90 days

• First 30 days: you’ve learned our skills and stack and are co-running 2–3 accounts.
• 60 days: you own accounts end to end and have shipped your first reusable skill.
• 90 days: you’re running your full set of accounts and launching experiments every week without prompting.

Why join

• You work directly with the founding team. You report to Cameron, and there is no one between your idea and it going live.
• Your work compounds. Every skill and automation you build gets reused across every client account.
• A real system from day one. You start in Claude Code and Codex with internal skills that already exist, not a blank page.
• A Strategist beside you. Targeting, copy and the client relationship are handled, so you focus on the build.
• The role grows with the company. At this rate of growth we’ll hire more Engineers, and the person who built the system is best placed to lead them.

Hiring process

1. Intro call: 30 minutes with Cameron, our founder
2. Paired trial ([paid], about [3] hours): build a small piece of a real campaign with us.
3. Final conversation: 30 minutes
4. Offer and kick-off



How to apply

• Apply through LinkedIn and send a link to something you’ve built (a workflow, a Clay table, an automation or a script) with two or three sentences on what it did.