Learn GTM & Sales Automation GTM Engineering

Career roadmap

How to become a GTM engineer

It's not a Clay job and it's not an outbound job. It's fixing the places a company loses revenue, time or data quality, and proving it with a number.

5 areas of the job 8-step skill roadmap 6 portfolio projects

Most people meet GTM engineering through Clay screenshots, AI agents and cold email volume. So they assume the job is knowing those tools. The tools matter less than you'd think. The business process and the revenue problem come first.

Don't start with "what can Clay automate?" Start with "where is this company losing money?"

Every good GTM engineering project can be read left to right, like this:

  1. 01

    Business problem

    Reps miss hot inbound leads

  2. 02

    GTM process

    Inbound lead → owner → first reply

  3. 03

    Data & signals

    Company size, title, pricing-page visits

  4. 04

    Orchestration

    Enrich, score and pick an owner

  5. 05

    Automation

    Route to CRM + Slack alert in under 5 min

  6. 06

    Measured outcome

    Speed-to-lead, meetings booked, pipeline

Example: an inbound speed-to-lead project, from problem to proof.

The job

Where GTM engineering shows up

Outbound is one of 5. Pick an area to see what you'd build and the numbers you'd be judged on.

What you build

  • Account and contact lists built from your ICP, not from a vendor's default filters
  • Research done before the BDR opens the record, so they spend the hour selling

KPIs you report

  • Qualified pipeline created
  • Meetings per BDR
  • Hours of manual research saved
  • Tool spend per meeting

The common thread, especially in marketing ops: more output without hiring at the same rate. Revenue per employee is the number leadership cares about.

The skill nobody lists: talking ROI

A CFO doesn't care that you built a Clay workflow. They care about more qualified pipeline, more meetings per BDR, lower tool spend, fewer manual hours and data they can trust. Sell the economic impact, not the technology.

Measure the number before you build, so you have something to compare against afterwards. A few made-up examples of the same work said two ways:

I built a Clay table with a 4-provider email waterfall.

Valid-email coverage went from 52% to 81%, so each BDR has 30% more people to reach.

I set up n8n to route inbound leads to Slack.

First reply on demo requests dropped from 9 hours to 6 minutes.

I wrote a dedupe script for HubSpot.

We cut 18,000 duplicate contacts, which drops us a HubSpot contact tier.

I automated our blog-to-LinkedIn repurposing.

Same two marketers now ship three times the posts, no new hire.

The stack, by layer

Learn what each layer does and you can pick up any tool inside it in a week. Get attached to one tool and you're stuck when the company uses another.

Layer Its job Tools you'll see
Orchestration Pulls data together and runs the logic Clay, n8n, Zapier, Make, Claude Code
Enrichment Emails, phones, firmographics, maps data Apollo, People Data Labs, Prospeo, Datagma, Google Maps scrapers
Intent & signals Who is in market right now G2, HG Insights, website visits, custom signals (jobs, funding, tech changes)
Sending Gets the message out without landing in spam Smartlead, Instantly, Outreach
Sales & CRM Where reps work and pipeline is counted LinkedIn Sales Navigator, HubSpot, Salesforce

You don't need to become the Salesforce or HubSpot admin. At bigger companies there already is one. You need to know how the CRM is shaped well enough to work with them.

What to learn first, in order

Written for people coming from marketing or outbound ops who are fine with no-code and want to get more technical. If you already know a step, skip it. Each one comes with a first rep: a small thing to build this week.

  1. 1

    How revenue actually gets made

    ICP, funnel stages, how reps spend their day. Without this you automate the wrong thing quickly.

    First rep: Shadow two sales calls and write down every manual step that happened before the call.

  2. 2

    APIs, JSON and webhooks

    Every tool in the stack talks this way. Reading API docs and a raw JSON response is the line between using Clay and building with it.

    First rep: Call one enrichment API from a Clay HTTP column or n8n HTTP node and map the response to columns.

    Our guide: URI vs URL for GTM people
  3. 3

    One orchestration tool, deeply

    Clay or n8n. Learn waterfalls, conditional runs, error handling and cost per row in one before you touch a second.

    First rep: Build a 3-provider email waterfall that stops at the first verified result.

    Our guide: n8n vs Clay
  4. 4

    CRM data model

    Objects, associations, lifecycle stages, field types. You do not need to be the Salesforce admin, but you need to talk to them as an equal.

    First rep: Draw your CRM's contact, company and deal objects and which field drives each report.

  5. 5

    JavaScript basics

    Clay formulas, n8n Code nodes and Apps Script are all JavaScript. Variables, arrays, objects, map and filter cover most of it.

    First rep: Rewrite one messy Clay formula as a clean n8n Code node.

  6. 6

    SQL

    The moment data lives in a warehouse or you need a report the CRM can't build, SQL is the answer.

    First rep: Load a CRM export into a free Postgres or BigQuery sandbox and count leads by source and stage.

  7. 7

    AI workflows

    LLMs for research, classification and first drafts at row level, plus Claude Code to build scripts you would not write by hand.

    First rep: Classify 200 companies into ICP tiers with an LLM column, then spot-check 20.

    Our guide: Claude Code prompts
  8. 8

    Deliverability

    You already have SPF, DKIM and DMARC. Add domain rotation, warmup, volume limits and how to read a bounce.

    First rep: Audit a sending domain and write the one-page fix list.

    Our guide: SPF, DKIM, DMARC explained

Watch out for the content trap. Another video or course feels like progress, but you learn this job by building things. Watch one, then build for a week before the next.

Show what you've built

6 portfolio projects that answer real problems

One from each area beats six outbound tables. Ship each with the number that proves it worked.

  • Inbound

    Inbound lead router

    Form fill → enrich → score → assign owner in the CRM → Slack alert with a summary.

    Proof: Time from form fill to alert, and how many test leads landed with the right owner.

  • CRM & RevOps

    Job-change alerts

    Watch past champions and customers; when one moves to an ICP company, create a task for the owner.

    Proof: Alerts per month from a sample list, and how many matched the ICP.

  • ABM

    Renewal-timing ABM list

    Find accounts on a competitor's product with a renewal likely in the next 90 days, ranked by fit.

    Proof: The ranked list plus the rule behind each rank.

  • CRM & RevOps

    CRM data-quality cleanup

    Dedupe, standardize titles and countries, backfill missing company fields with a waterfall.

    Proof: Fill rate and duplicate count before vs. after, and cost per fixed record.

  • Outbound

    Signal-based outbound list

    Pick one signal (hiring for a role, new funding, a tech install), build the list, write the first line from the signal.

    Proof: List size, valid-email rate, and a few example first lines.

  • Marketing ops

    Content repurposing pipeline

    New blog post → LinkedIn drafts, a newsletter blurb and a log row, with a human approval step.

    Proof: Minutes per post before vs. after.

Getting your first real reps

Here is the chicken-and-egg problem. You need practical experience to get hired, and it's hard to get practical experience without a job. Courses and bootcamps get you part of the way. After that, somebody has to let you do real work for them.

There are two ways to get someone to say yes:

A

Build in public

Build your own projects and post about them, along with your story, on LinkedIn. Don't be boring. Most people never post, and fewer post well or often, so doing it at all makes you stand out.

B

Ask your network

Find someone who already rates you, a past manager, a founder friend or a client, and offer to fix one problem from the list above. Posting (A) is often how those people find out you can do it.

A background in marketing or outbound ops is an advantage here. If you've set up SPF and DKIM, run Smartlead campaigns and wired up n8n, you already know the process you'd be automating. Most engineers moving into GTM have to learn that part from scratch.

For structured learning, start with free vendor material: Clay University, HubSpot Academy and Salesforce Trailhead. Bootcamps such as Bootprint (formerly Clay Bootcamp) add feedback and real projects if you want someone to check your work.

Common questions

FAQ: GTM engineering

Sources: the YouTube talk "The Only GTM Engineering Video You Will Ever Need", a LinkedIn post by Bootprint's CEO on breaking in, and the questions people moving over from marketing and outbound ops keep asking.

Keep going

More GTM and sales automation breakdowns, built the same way.