field notes · GTM engineering · published October 13, 2026
What does a GTM engineer do?
A GTM engineer builds the systems that connect market research, go-to-market execution, CRM workflows, and feedback. In my work, that means mapping total addressable markets, designing GTM motions, and applying AI where it makes revenue work more repeatable.
The title is still taking shape, and companies use it in different ways. Here is the practical version I use: a GTM engineer works across the research, process, data, and tooling that help a team find and serve the right market.
What does a GTM engineer build?
A GTM engineer can build a connected motion from four parts: define which market to pursue, decide how to reach it, make the workflow operational in the CRM and other tools, then use results to improve the next pass.
That can include a total addressable market map, prospect research, campaign workflows, routing rules, reporting, or AI-assisted classification. The specific tools matter less than whether the system gives the team a clear next action and useful feedback.
How is GTM engineering different from RevOps?
The boundary depends on the company. RevOps often focuses on the reliability of revenue processes, systems, and reporting. GTM engineering often focuses on building and iterating the data and workflows used to execute go-to-market motions. In a small team, one person may do both.
I think of the work as practical systems building: start from a revenue problem, map the steps and information needed, then automate only the parts that are stable enough to repeat.
What does market mapping look like in practice?
Market mapping turns a broad category into a researched, usable list. That means defining inclusion criteria, collecting companies from relevant sources, resolving duplicates, checking fit, and identifying people connected to the buying process.
On a Relevance team project, a European security-provider map reduced 20,256 directory listings to 1,544 qualified companies and 2,422 buying-committee contacts. The qualification rules and rejection reasons mattered as much as the final list: the team could see why a company fit or did not fit.
Where does AI fit into GTM engineering?
AI is useful when it reduces repetitive research or helps classify information consistently. Examples include summarizing company evidence, applying a qualification rubric, extracting details from posts, or routing a signal to the right workflow.
It still needs clear inputs, checks, and a human decision where the cost of a wrong result is high. I treat AI as one component in the workflow, not as a replacement for deciding who the team should reach and why.
How do you know whether the system works?
Measure the outcome the motion is meant to change: qualified companies, useful replies, completed handoffs, or time spent on research. Track the quality of the inputs too. A large list or a high activity count does not prove the motion is working.
For a separate content-research project, I analyzed 10,172 LinkedIn posts and checked the classification against a blind holdout set, reaching 90% accuracy. That project helped me study how evidence and format relate to engagement; it did not prove a universal formula for writing posts.
Explore the 10,172-post analysis ↗
What should a team automate first?
Start with a repeated step that has stable inputs, a clear output, and an easy way to catch mistakes. Prospect enrichment or CRM routing may be good candidates. A poorly defined qualification decision usually needs clearer criteria before automation.
That is the work I want to keep doing: build a GTM motion, map the market it serves, and connect the research, CRM, and AI workflows so the team can act and learn from the result.