A GTM Engineer Job Description You Can Actually Use
Most GTM engineer job posts read like a tool catalogue. That is how you end up hiring a list builder, a RevOps generalist, or a prompt hobbyist, and then wondering why the quarter did not move. One post on X put it cleanly: "Good: hiring a GTM engineer. Great: knowing which of the 3 jobs you're actually hiring for."
Pramod Kumar, co-founder of Kingdom of Kumar. On X
·
This article is a description you can paste, then edit. It is not a claim about the "average" role worldwide. It is grounded in two public analyses of what postings actually asked for, plus the work I think the seat should cover in the first 90 days. How to run the search is in How to hire a GTM engineer. The week itself is in What does a GTM engineer do. Interview prompts are in GTM engineer interview questions. The role is also described on GTM engineer and GTM engineering.
What 161 postings, and then 739, actually asked for
In early November 2026, Hlib S. published a breakdown of 161 GTM engineer job posts. In that set, data pipelines showed up in 79% of postings, enrichment in 71%, CRM in 65%. About two-thirds mentioned Clay. Claude appeared in 43% against OpenAI in 19%. n8n appeared in 45%, ahead of Zapier at 30%. SQL was in roughly half, Python in 42%. Sending tools appeared in only 14%. About one in nine roles was a company's first GTM engineer. Those figures are his count, from that sample, dated to that post.
In October 2026, Mateusz Sekta wrote up an analysis of 739 postings. The detail I would not ignore: only ten of those postings were junior. This is not, in the public market those analyses describe, an entry-level title you can fill with "interested in AI and sales."
I would not copy every logo from those lists into your post. If you do, you will filter for people who have touched the fashionable stack, not for people who can ship a motion in *your* accounts. Use the lists as a map of the labour market, then write the job you actually have.
"Knowing which of the 3 jobs you're actually hiring for"
I use three buckets. They overlap. They are not the same hire.
1. Motion builder. Someone who can take a defined offer and fit, and stand up the path from signal or list, through enrichment and a draft, to an approved send and a reply handoff. This is the hire most seed founders think they are making.
2. Data and systems person. Someone who can make enrichment, scoring, CRM fields, and pipelines trustworthy, and who will get irritable about bad data. This hire often looks like RevOps from the outside, and sometimes should be staffed that way.
3. Operator-with-tools. Someone who will run the motion week after week, tighten copy and rules, and not disappear into a side project of new automations. Without this, the first two become a demo.
Write which bucket is primary in the first paragraph of the post. If you truly need all three, you are probably describing a senior person you may not be able to hire, or a team, or a build-and-run engagement. Do not hide that.
If the product is not ready to sell, do not post any of the three. Take the App Launch Score first.
A job description you can copy
Edit the brackets. Delete anything you will not support in the first 90 days.
Title: GTM Engineer (first hire / motion builder)
The job, in one paragraph.
You will build and run one outbound (or inbound) motion for [offer] sold to [fit]. In 90 days, that motion should run in our company accounts, with a written fit rule, a way to collect and check contacts, drafts that a founder or AE approves before they go out, a clear reply path, and a Friday review we can do in thirty minutes.
What you will do
- Write and keep a short definition of who we contact, and who we never contact
- Choose and document the data sources; do not add a second enrichment tool without retiring a reason
- Build a path from "this account deserves a look" to an approved message
- Sit with the founder on approvals until the miss rate is low enough that the founder is not rewriting every line
- Keep CRM records current enough that we do not email people we already know
- Review the week every Friday: what ran, what broke, what we will change once
What you will not be hired to do
- Send volume for its own sake
- Own the company forecast
- Replace the founder on sales calls
- Rebuild the stack every month
What you have already done (proof, not adjectives)
- Show one motion you built: the rules, the tools, and what you would do differently
- Be ready to work in a messy CRM, not only a clean demo workspace
- Comfortable with [SQL / a spreadsheet / n8n or similar — pick what you actually use]. Clay is common in the market; it is not a requirement if you can get trustworthy data another way.
How we work
- Company-owned logins and workspaces
- No unapproved outreach
- You will have a named founder owner and a weekly slot that does not move
How to apply
Send a short note on one system you have built, what it was for, and one thing that failed. We will give a paid, tightly scoped work sample rather than a twelve-round process.
How to keep the post honest
Name the salary band you can actually pay, or say you will share it on the first call. Public 2026 figures for US in-house roles often sit in a mid six-figure base range; I walk through attributed numbers in GTM engineer salary. If you cannot carry that, do not post a full-time role at a fantasy number. Look at fractional, or at a done-for-you team.
Kingdom of Kumar is $500 a month with a three-month minimum: we build and run a scoped system on Grok and Claude, you own it, you approve what goes out. That is not the same as this job description. If you need the employee, use the post above and interview for proof of work.
A pre-post checklist
- [ ] One primary job, named
- [ ] A 90-day definition of done
- [ ] Tools listed as context, not as a shopping list
- [ ] Proof of work required
- [ ] Company-owned accounts stated
- [ ] A founder owner named
- [ ] A salary or process for sharing it
- [ ] A work sample, not only a culture interview
If you cannot tick those, you are not ready to post. You are ready to write a one-pager of the motion and run it yourself for two weeks.
FAQ
Should I require Clay?
Only if you already run Clay and will support it. Plenty of postings mention it. Plenty of good people can enrich and route without it.
Should I require Python?
Require it if the work lives in code. If the work lives in a CRM, a sheet, and an automation tool, say that. Do not require Python as a prestige filter.
What if this is our first GTM engineer?
Say so. In Hlib S.'s 161-post sample, about one in nine roles were a first hire. Candidates should know they will be writing the first rules, not inheriting a machine.
Can I use this for a contractor?
Yes. Change "90 days" to the length of the contract, and add a handover clause: everything lives in your accounts, with a written pass-off in the last two weeks.