A GTM (go-to-market) engineer builds the systems a sales and marketing team runs on: the account data, the enrichment, the signals that say who to contact this week, the outbound that goes out, the CRM automation that routes a reply to the right person, and the reporting that shows what worked. It is revenue operations done as engineering, with AI now doing much of the research and drafting in the middle. You become one by building those systems end to end, usually from a sales, marketing or operations job, or from engineering towards revenue work.
One honest data point before the detail. In 3,610 public job postings we collected on 29 September 2026, exactly one was titled GTM engineer. That is not because the job is imaginary. It is because of where we looked.
What does a GTM engineer do day to day?
The work runs as a loop, and each stage is a system that has to keep running without you:
- The data layer. Turn the ideal customer profile into data: which companies, which roles, which signals. Build a clean account list from enrichment tools and keep it clean, because every downstream step inherits its mistakes.
- Signals. Watch for the things that make an account worth contacting now: a new hire, a funding round, a product launch, a visit to the pricing page. Score accounts daily, and make every score explainable, so a salesperson can see why an account is at the top.
- Outbound. Sequences where a model researches the account and drafts the message, and a person approves it before it is sent. Deliverability and compliance are part of the job, not an afterthought.
- CRM and routing. The CRM as the system of record: a reply or an inbound lead lands with the right owner quickly, with the context attached, and nothing is lost between tools.
- Attribution. Show which activity produced which meetings and pipeline, in a way that survives a sceptical revenue leader asking how you know.
The tools are the ones you would expect: Clay and other enrichment services, n8n, Make or Zapier for the glue, a CRM such as HubSpot or Salesforce, SQL for the reporting, and LLM APIs for research and personalisation.
Why did our job-ad sample find only one GTM engineer posting?
Our sample is the same public fetch behind our count of AI job ads, re-run on 29 September 2026: Hacker News "Who is hiring?" threads for July to September 2026, Remotive and Arbeitnow. Those are engineering-heavy boards, used mostly by startups and European employers, and Australia barely appears in them. Of 3,610 postings, one had GTM engineer in the title. It was a European posting on Arbeitnow, and it mentioned SQL, AWS, agents and Claude.
One posting is not a finding about the market; it is a finding about the boards. GTM roles are hired where sales and revenue people look for work: LinkedIn, sales and RevOps job boards, and the communities around the tools themselves. We did not sample those, so we cannot tell you how many GTM engineer jobs exist, and we will not guess. For contrast, the same fetch held 49 sales or solutions engineer postings, a revenue-side technical role that engineering boards do carry. The counts file is public, with the method in it.
If you search engineering job boards for "GTM engineer" and find nothing, you are looking in the wrong place. Search for the older names the same work goes by: revenue operations, marketing operations, growth engineer, sales operations and, increasingly, automation roles. Our piece on what an AI automation engineer is found the same pattern: real work, rare title.
How is a GTM engineer different from RevOps or an SDR?
By what they produce:
| Role | Produces |
|---|---|
| SDR or BDR | Conversations and meetings, one account at a time |
| Revenue operations | The CRM configuration, process and reporting the team works inside |
| GTM engineer | The automated systems that find, research, contact and route accounts at scale, and prove what they produced |
In small companies one person does all three. The difference that matters is leverage: an SDR's output grows with their hours, and a GTM engineer's output grows with the systems they build. That is also why the role has spread alongside AI: a model can now research an account and draft a first message, so the scarce skill is building the pipeline around it and keeping a human approving what goes out.
What skills do you need to become a GTM engineer?
Five, roughly in the order you will need them:
- Data hygiene. Deduplication, matching companies across sources, knowing what an enrichment provider gets wrong. A list that refreshes weekly without duplicates or stale rows is harder than it sounds.
- Automation tools. n8n, Make or Zapier well enough to build a multi-step workflow with error handling, and to know when a step needs code instead.
- SQL and basic scripting. For reporting, for joining data the tools cannot, and for calling APIs that have no connector.
- LLMs with guardrails. Structured output, research prompts that cite their sources, and an approval step before anything reaches a prospect.
- Commercial judgement. Knowing what a good account looks like, what a salesperson needs in front of them, and how to defend a number to a sales leader.
You do not need to be a software engineer, but you do need to be comfortable with data.
Can you become a GTM engineer without experience?
The most common routes in are sideways:
- SDRs, BDRs and account executives who got tired of doing research by hand and started automating it.
- Marketing and revenue operations people who already own the CRM and want to build rather than configure.
- Engineers and data analysts who want to work closer to revenue.
Each group has half the job: salespeople know what a good account looks like, engineers know how to make a pipeline reliable, and the gap on either side is trainable. If you have neither sales context nor any comfort with data, start with one of them first.
How do you prove you can do the job?
Show running systems, not screenshots of a sequence. A hiring manager wants to see an account list that rebuilds itself, a signal pipeline with explainable scores, an outbound flow with a human approval step and reply capture, routing that works, and an attribution view you can defend. A short written note on each, saying what it produced and what you would change, does more than any certificate.
Where should you start this week?
Pick one market you know and do the first stage properly. Write your ideal customer profile as fields, not adjectives. Build a list of fifty accounts from two sources, deduplicate it, and score it with a rule you can explain. Then automate one refresh in n8n or Make so it runs next week without you. The free GTM engineering skill check takes a few minutes, and the GTM engineer role page describes the day-to-day in more detail.
Square 1's GTM Engineer Bootcamp builds exactly that loop: twelve weeks, live on Zoom with one instructor, about 15 hours a week, in six blocks (the data layer, signals, outbound, CRM and routing, attribution, and a partner's brief with a hiring sprint), each ending in a deployed system and a gate you must pass, with a recorded viva defending your numbers. No code is required to start. Two on-demand courses, recorded by an instructor and graded by Nova, Square 1's AI tutor, cover parts of it: AI for Sales for prospecting and outreach, and Agents with n8n and Make for the automation. All three are taking a waitlist today.