Systems that sell

Hiring a GTM engineer? Read this before the job ad

August 20, 2026
Ryan Hall
Ryan Hall
Founder
Hiring a GTM engineer Read this before the job ad

A GTM engineer is the person who builds the automated systems behind a company's sales and marketing. They connect data providers, the CRM, AI tools and outreach software so that finding prospects, researching them and starting conversations happens without someone doing it by hand. Think of them as part sales ops, part developer, with a commercial brief.

It's the hire a lot of founders are weighing up right now.

My answer is nearly always the same. A good GTM engineer is worth having. But the job ad is usually written before anyone has decided what the engineer is meant to engineer. So before you post one, here's what the role actually does, what it needs from you, and how to tell whether it's working.

If you want the wider picture first, I've written about what GTM engineering is as a discipline. This piece is about the person.

What a GTM engineer actually does

Strip away the job titles and a GTM engineer spends their week on five kinds of work:

  1. Building and cleaning data. Pulling target companies and contacts, filling gaps in records, and keeping the CRM accurate as people change jobs.
  2. Setting up signals. Deciding which events count as a reason to get in touch, such as a new hire, a funding round or a repeat website visit, and wiring them to alerts.
  3. Automating research and first drafts. Using AI to summarise an account and draft an opening line a salesperson can check and send.
  4. Routing. Making sure the right lead reaches the right person at the right moment, rather than sitting in a shared inbox.
  5. Measuring. Reporting what the systems produced, and switching off what doesn't work.

Notice what's missing from that list. A GTM engineer doesn't decide who your ideal customer is. They don't write your positioning. They don't run sales calls or nurture a relationship over six months. They build the machinery that carries those things, and that only works if someone has already decided what they are.

What a GTM engineer needs before day one

This is where most hires go wrong. A GTM engineer needs four inputs, and they rarely come with the role:

  • A defined ideal customer profile. Not "B2B companies with 50 to 500 staff", but the specific problem, trigger and buyer you win with. Without it, the tooling ends up deciding who you target: whoever the data finds.
  • A story that already lands. Automation multiplies your message. If it isn't converting by hand, it won't convert at scale. That's the job of Positioning that connects.
  • A pipeline with owners. Clear stages, clear handoffs, and someone accountable for each one. Otherwise the engineer fills the top of a funnel nobody is working.
  • A plan for warm replies. Most people who reply aren't ready to buy. If nobody owns the follow-up, the best output of the engineer's work goes cold in the CRM. That's Nurturing that converts.

Hire before these exist and you're paying an engineer to build on sand. They'll be busy, the dashboards will look healthy, and pipeline won't move.

The UK rules the job ad leaves out

A GTM engineer handles personal data at volume: names, work emails, job titles, often pulled from third-party providers. In the UK, that comes with rules most job ads never mention.

  • Who you can email without consent. Under PECR, you can email corporate bodies, such as limited companies and LLPs, without prior consent. Sole traders and ordinary partnerships are treated as individuals, so you need their consent or an existing customer relationship (ICO).
  • Every email needs a real sender and an opt-out. You "must not disguise or conceal your identity", and you must give a valid address to unsubscribe (ICO, same guidance).
  • Enriched data triggers a notice. When you collect someone's details from another source, UK GDPR requires you to tell them, at the latest within one month or at your first message to them, whichever comes first (ICO).

The ICO notes both pages are under review following the Data (Use and Access) Act, so check them before you build. The point stands either way: a GTM engineer who can't explain how your outreach meets these rules is building a liability, not a system.

When to hire a GTM engineer, and when not to

You're ready if You're not ready if
Outreach already converts when done by hand, and you want more of it You're hoping automation will find what works
Salespeople lose hours every week to list building and research Nobody is sure who the ideal customer is
Warm replies have an owner and a follow-up rhythm Replies land in a shared inbox and wait
You can name the three signals that predict a deal Every new hire or funding round counts as a signal

If most of your answers sit in the right-hand column, the first hire isn't an engineer. It's the work that gives an engineer something worth scaling: the story, the targeting and the pipeline. That's a sales engine, and it's what we build with clients.

How to judge a GTM engineer's work

The easy numbers are the wrong ones. Emails sent, records enriched and workflows built all go up from week one, and none of them pay the bills.

Judge the role on what reaches the pipeline instead:

  • Meetings that progress. Not meetings booked, but meetings that move to a next stage.
  • Time given back. Hours a week your salespeople no longer spend on research and admin, and what they do with them.
  • Signal accuracy. Of the accounts the system flagged, how many turned out to be in the market.
  • Domain health. Reply and complaint rates. Volume that damages your sending reputation costs more than it earns.

Five questions to ask in the interview

  1. Talk me through a system you built that you later switched off. Why?
  2. How would you work out our ideal customer profile if we handed you a vague one?
  3. What happens to a warm reply in the systems you build?
  4. How do you make sure our outreach meets PECR and UK GDPR?
  5. Which metric would you want us to judge you on in your first 90 days?

Good candidates answer with judgement, not tools. If every answer is a software name, you're hiring an operator for a stack, not an engineer for an engine.

Not sure whether you need the hire or the foundations first? Our Sales engine assessment shows where your pipeline leaks, and whether a GTM engineer would fix it or just make it leak faster.

FAQ

What does a GTM engineer do?

 A GTM engineer builds the automated systems behind sales and marketing: data and enrichment, buying signals, AI-assisted research, lead routing and reporting. They build the machinery. They don't set the ideal customer profile or the positioning it runs on.

What skills does a GTM engineer need? 

Commercial judgement first, then technical skill: data handling, CRM administration, workflow automation, and enough scripting to connect tools. Knowledge of UK data rules (PECR and UK GDPR) matters for any role sending outreach.

Is a GTM engineer the same as a sales ops or RevOps manager? 

They overlap. RevOps runs the revenue process and its reporting. A GTM engineer builds automation inside it, mostly at the top of the funnel.

When should a company hire a GTM engineer? 

When outreach already converts by hand, the ideal customer profile is defined, and warm replies have an owner. Before that, automation scales the gaps.

More Opinions

GTM for CFOs

Cutting spend isn’t efficiency. Stop renting your growth and build an engine your CFO wants to invest in.

Systems that sell

GTM engineer or GTM engine?

You can hire someone to make your engine faster. Just make sure you’ve built one first.

Systems that sell

AI is killing your CRM

Your CRM is about to become a database. The teams already treating it that way are pulling ahead.

Systems that sell