What does a GTM engineer do?

What is a GTM engineer? A GTM engineer builds the systems a go-to-market team runs on: data sources, enrichment pipelines, scoring models and campaign logic. Instead of adding reps to add pipeline, a GTM engineer builds software that finds the right prospects and gives each one a real reason to reply.

What a GTM engineer does day to day

The work changes by company, but it usually includes:

• Scoring the full total addressable market against the signals behind past wins
• Finding and joining public data sources such as permits, filings, government records and competitor signals
• Building enrichment pipelines and keeping lists fresh
• Writing the logic behind each campaign, so every message reflects real data
• Analyzing call transcripts, churn and customer health
• Automating research that reps used to do by hand

Jordan Crawford does all of this in Claude Code and publishes the method as he builds in On the Edge.

How companies describe the role

Companies now post jobs with this title, and their own wording is a good definition. In a review of public job postings, Jordan found Cresta hiring a GTM Engineer to "design and deploy an AI native operating system for our revenue engine." OpenAI's posting says its GTM Growth Engineering team "builds autonomous and semi-autonomous AI systems that help OpenAI's go-to-market organization operate at massive scale."

Both describe the same shift. Go-to-market becomes something you build as software instead of something you staff by hand. For the bigger picture, see what GTM engineering is.

Tools GTM engineers use

There's no single required stack. Common pieces include:

• Clay for enrichment and workflow tables. See what Clay is.
• Claude Code or Codex for building custom tools, scripts and agents.
• Public datasets such as license rosters, permit files and federal registries. See data sources for prospecting.
• Your own systems, including the CRM, call recordings, support tickets and billing data.

An example of the work

One project on the Blueprint homepage scored 32,493 fire departments in about six days. It pulled from 11 federal databases, scraped 57 state directories and extracted 23,262 fire chief contacts. Another scored 47,228 third-party logistics warehouses against 20 signals in about 48 hours, and 3,326 made the cut.

Neither list could be bought. Each one was built from a question about which companies had the problem, then the data to answer it.

The skills that matter most

The job is less about any single tool and more about judgment. AI can research, structure data and build workflows. It can't feel the tension in your buyer's quarter.

Jordan sets a simple bar for knowing your buyer. If you told ten of your buyers "I think you care about these three things," all ten would say yes. He also recommends writing ten messages by hand before building any system. If you can't name the condition that makes a message land, more connected data won't name it for you.

So a good GTM engineer needs a few things:

1. Curiosity about why customers actually bought
2. Comfort finding and joining messy data
3. Enough technical skill to build with AI tools
4. The patience to ship, measure and ship again

Jordan's point of view

Jordan sees the GTM engineer as the person who points the tools at understanding customers. When teams use AI to send generic messages faster, they add to the noise. When they use it to find prospects with a specific, provable problem, the same tools work like a research team.

If you want to move into the role, read how to become a GTM engineer. If you're already building, see On the Edge for GTM engineers or subscribe for new builds.