Part I · The job · Chapter 1
What a GTM engineer actually does
Half commercial thinker, half builder: how the role differs from RevOps, SDRs and software engineers, and where it sits.
9 min read
A GTM engineer builds the systems that find the right companies, notice when they are ready to buy, and get a relevant message in front of the right person, then keeps those systems running as the market and the tools change. It is a building job judged by a commercial number: pipeline.
What you'll take away
- 01A working definition you can say in an interview without buzzwords.
- 02How the role differs from RevOps, sales development, marketing ops and software engineering.
- 03The three kinds of employer, and what each one wants from you.
- 04Why the people who think about revenue first and tools second get paid more.
The role in one paragraph
A GTM (go-to-market) engineer is half commercial thinker and half builder. The commercial half decides who the company should sell to, why now, and what to say. The building half wires up data sources, enrichment, signals, outreach tools and the CRM so that those decisions run every day without someone doing them by hand. The title was popularised by Clay around 2023, but the work existed before under other names.
Judge the role by what it produces: qualified pipeline. Not by how many tools it touches.
How it differs from its neighbours
| Role | Main job | Measured on |
|---|---|---|
| Sales development rep | Works a list: calls, emails, books meetings | Meetings booked |
| RevOps analyst | Keeps the revenue data clean and reports on it | Accurate forecasts and reports |
| Marketing ops | Runs campaigns, forms, lead handoff from marketing | Marketing-sourced leads |
| Software engineer | Builds the product customers use | Working, maintainable product |
| GTM engineer | Builds and runs the system that finds, prioritises and reaches buyers | Pipeline generated, and its cost |
The boundaries blur in practice, and the title varies: growth engineer, revenue engineer, sales systems, automation lead. When you read a job ad, look past the title at the deliverable. If the job is to build things that create pipeline, it is GTM engineering, whatever it is called.
Where GTM engineers work
- In-house at a B2B company, usually reporting to sales, growth or RevOps. You own one company's pipeline machine end to end and live with what you build.
- At an agency that builds outbound systems for several clients. You see many markets and tools quickly. It is often the fastest way to build a portfolio, and the pace is high.
- Freelance or fractional, building specific systems for a few clients at a time. Your reputation and case studies are the whole business.
Early-stage companies want someone who can stand up the whole machine from nothing. Larger companies want someone who can make an existing, messy setup reliable and measurable. Both need the same core skills, applied at different depths.
Operator or engineer
The common trap for newcomers is to learn tools, then look for problems to use them on. Tools change every year. The people who last start from a revenue question: who buys, why, and what would make them reply? Then they build the smallest system that answers it. A campaign with one well-chosen data point and a clear message regularly beats one with twenty enrichment columns and nothing to say.
| A tool operator | A GTM engineer |
|---|---|
| Starts with what the tool can do | Starts with who should buy and why now |
| Adds data because it is available | Adds data because the message needs it |
| Measures emails sent | Measures replies, meetings and pipeline, and their cost |
| Builds a new table for every request | Builds systems others can reuse and trust |
What a good week looks like
- Reviews last week's numbers with sales: what was sent, what landed, who replied, what turned into meetings.
- Fixes the biggest leak first: a broken sync, a bounce spike, a segment nobody answers.
- Ships one improvement: a new signal, a better list, a tighter message, an automation that saves reps an hour a day.
- Writes down what changed and why, so the system can be understood by someone else.
Try it
Read a job ad
A job ad for a "Revenue Operations Specialist" at a 60-person software company says: "Own our outbound data stack. Build lead lists in Clay, keep HubSpot clean, set up sequences in our sending tool, and report weekly on pipeline sourced from outbound. Some scripting is a plus."
Is this a GTM engineering role? What would you ask in the first interview to be sure?
Write your answer down first, then reveal the worked answerWorked answer
Probably yes. Building lists, running sequences and reporting on pipeline sourced from outbound is GTM engineering work under a RevOps title. Keeping HubSpot clean is shared ground with RevOps.
Ask: who decides which accounts and segments to target; whether you would build the system or mostly run what exists; how outbound success is measured today; who owns deliverability and sending domains; and whether there is budget to try new data sources. If the answers show you would only produce reports, it is a RevOps role. If you would design and build the machine, it is the job.