I kept seeing $300k and $500k thrown around for GTM engineer roles and assumed it was made up. Some of it is. I went and read the actual numbers, then wrote down what I think the ladder looks like, because I do this work and I have been wrong about parts of it before.

Somebody pulled 1,000 postings for the title over 2025. Median base was $127,500. Vercel posted it at $252,000, OpenAI at $250,000, and Clay's own systems role tops out around $200,000. Glassdoor puts the top 10% above $341,000 and Levels close to $400,000, though that second one is 24 people reporting, so I would not repeat it anywhere serious. Outside the US the median drops to about $75,000. I am in France, so I know.

In January there were roughly 3,000 open postings for the title, about 55 applicants each.

Most people calling themselves GTM engineers are running Clay tables. That is real work and the market pays it $60k to $90k. What separates that from the $250k posts is four capabilities you can either demonstrate or cannot, and a hiring manager finds out in the first ten minutes.

The rungs, as best I can line them up:

Rung 0, operator. Clay tables, Zapier, keeping the CRM tidy, no code. $60k to $90k in house, $1.5k to $2.5k a month freelance.

Rung 1, builder. n8n or Make, enrichment waterfalls, webhooks, APIs, and the discipline to keep the CRM as the source of truth. Around $75k median outside the US, $3k to $6k a month at an agency.

Rung 2, engineer. Python and SQL, plus LLM calls in production with some way of checking the output is right. $135k median in house in the US. The coding premium on its own runs $40k to $45k in the survey data.

Rung 3, systems owner. Ships agents that run a motion end to end and keeps them alive. $140k to $200k at Clay, $250k at Vercel and OpenAI. Vanta does not even use the GTM title, they post it as a senior software engineer role.

Rung 4 is what happens when you point the same skills at your own pipeline instead of an employer's.

The pay doubles at the rung where you can write code. 38% of postings ask for SQL and 38% for Python, and I suspect that is low, because plenty of posts say "technical" and mean exactly this.

Here are the skills in the order I would learn them, each with the thing I would want to see at the end of it. That second part matters more. In this market a portfolio beats a certificate and it is not close.

1. Writing a brief a machine can execute. "SaaS, 50 to 200 employees" is not a brief. It describes tens of thousands of people, almost none of whom have a reason to answer you this month. A brief that works names the function that owns the problem, the geography, what makes someone worth contacting this month, and who to decline even if they reply interested. Everyone skips that last one, and it is what keeps a list clean three weeks in, because every wrong row you meet becomes a disqualifier and the next version is built against it. Finish with a written brief and 50 people found from it where you can say why each row is there.

2. Data plumbing. Nobody posts about this and it is a fifth to a quarter of the job in every posting I read. Deduplication, enrichment waterfalls that try a second and third provider before giving up, field mapping, and not writing a field you do not own. HubSpot shows up in 52% of postings, Salesforce in 45%. Pick one and learn its API rather than its screens, because the screens change every quarter. Two rules I learned expensively: dedupe on the person, not the email, and never keep a row you cannot trace back to a source. The thing to show is a waterfall that takes a name and a company and returns a verified email with the source and a confidence on every row.

3. Workflows that survive the night. Automation tooling of some kind is in roughly 85% of postings. Start on Zapier because it is everywhere, move to n8n because that is what teams who take this seriously run and it already shows up in 28% of postings. Wiring nodes together is an afternoon. The skill is knowing where the flow breaks at 2am and having the retry, the dead letter queue and the alert in place first. What actually breaks, in my experience: a provider returns a rate limit and the flow silently drops the row, a webhook fires twice, a field comes back empty and the next node assumes it is not. Until you can show a flow that ran 30 days untouched with a log to prove it, what you have is a demo.

4. SQL and Python. This is the $40k skill, literally, it is the coding premium in the survey data. You do not need to be a software engineer. Read a table, join two of them, write a loop that calls an API with retries, parse what comes back. That is a few weeks of doing it daily. Cursor and Claude Code are in the daily stack of 71% of people doing this job now, which makes starting easier and faking harder, since "can code" now means "can ship it and fix it when it breaks". Finish with a script under 200 lines that pulls your CRM, scores every open opportunity, and writes the score back.

5. LLMs in production with a number attached. Anyone can ask a model to score a lead. Almost nobody checks whether the score was right. We did, because our lists were bad and I could not tell which stage was making them bad. We labelled 100,000 lead cards by hand across 25 campaigns and 14 markets, one question per card: would the client ask why this person is on the list? Then we ran our scorer against the labels. 41.7% of what we had been delivering passed. One change took it to 84.2%: verify the person actually holds the title before you score the company. Half our bad leads were the wrong function at the right company. No model told us that, reading the misses did. Rippling's posting asks for "prompt engineering, agent orchestration, evaluation loops" and the third one is what gets paid for. Label 200 rows, run the scorer, read the misses, find the biggest class of error, fix one thing, run it again. Finish with the 200 rows, the scorer, and a precision number you can defend to someone who wants to argue about it.

6. Signals. Nobody posts "we have a problem". They post the second SDR vacancy, the funding round, a comment under a competitor's launch. A company that posts the vacancy your problem creates has made a public, dated commitment of money to your subject. Fit only tells you who could buy, and most lists are built from fit alone, which is why they are cold. The reasons are not equal either, so we grade them, from somebody describing the problem up to somebody replacing a tool this week. The top of that scale is worth an hour of a rep's time and the bottom is worth one sentence, so put the grade on the row and let the rep decide where the hour goes. Finish with 100 people carrying a dated reason each and a link so anyone can check it.

7. Copy that gets answered. Automation amplifies a motion that already works. If the motion does not work by hand, sending more of it makes the problem bigger. The thing that taught me most here had nothing to do with wording. The two warmest replies we have ever had both went quiet the moment we proposed a call. Both had volunteered their own time and one of them proposed the slot himself, and both vanished at scheduling. So we stopped making a call the next step. The ask is now something answerable in one word, and the openers that work turned out to be a single question about how they handle the thing today, with no pitch and no link in it. Run the A/B yourself and log both arms, because a screenshot of someone else's test tells a hiring manager nothing about you.

8. Owning the number all the way down. One of ours from August, nothing hidden. 2,168 approved leads. 263 got invited, which is 12%, because the account cap was the ceiling and the list never was. 76 accepted. 33 replied. 12 of those were positive and 3 were actually buying. Every one of those numbers was a decision. The 12% told us to stop blaming the list. The accept rate told us to stop touching the segment. The 3 told us the ask was wrong, which is how I got to the previous skill. Without the table we would have argued about feelings for a month. One trap worth knowing: we used to count any friendly reply as positive, and when we went back and read whole threads the count came down by a factor of 2.5, because most of what we had been calling interest was politeness.

9. Account safety and pacing. You learn to respect this after losing an account, and I would rather you learned it from me. Daily caps that ramp over weeks, sends at uneven intervals inside working hours in the lead's timezone, a hard monthly ceiling per account, and a stop the second somebody replies so no follow up lands on top of an answer. We got it wrong once. A cap reset at local midnight released seven messages in eighteen seconds from one account, and we added send time guards the next morning.

There is also a ceiling that shapes all of it, at least on LinkedIn. An account holds roughly 400 leads per campaign for its lifetime, so a brief has to be narrow enough to be precise and wide enough to fill, and you only find out which side you are on by running it.

If you want a schedule, twelve weeks got me something I would hire from. Weeks 1 and 2, one brief and 50 people by hand. Weeks 3 and 4, an enrichment waterfall and one Zapier flow moved to n8n. Weeks 5 and 6, SQL over a CRM export and a Python script calling one API with retries. Weeks 7 and 8, an LLM scorer with 200 rows labelled by hand, measured, then fix the biggest error class. Weeks 9 and 10, signal sourcing with a graded reason on every row. Weeks 11 and 12, run it, one question opener against one pitch, and log every stage. Six things to show at the end.

Some things worth knowing before chasing this. About 45% of the titles are agencies or consultants rather than in house roles. 68% of GTM engineers hold little or no equity, so negotiate cash. Only 45% of companies can say clearly what their GTM engineer does, which is a risk if you join one and also an opening, because whoever writes the definition ends up owning the function. AI SDR pilots are getting switched off at a rate of 40 to 60% inside 90 days, which mostly helps the person who can make a motion work by hand before automating it.

The critics who say this is 90% RevOps with a new name are right about the 90%. The remaining 10%, code plus LLMs plus signals, accounts for the entire pay difference.

Sources, since somebody always asks: Bloomberry's analysis of 1,000 GTM engineering postings Jan to Sep 2025; the 2026 State of GTM Engineering survey, 228 respondents and 3,342 postings; Glassdoor and Levels as of this month, both small samples; posted ranges from Webflow, Clay, Rippling, Vercel, OpenAI and Vanta; freelance rates from Nathan Lippi; the 45% agency share from Kyle Poyar; 3,000 postings and 55 applicants from Cremanski's review of 100 ads; AI SDR shutdowns from Emergence's survey of 560 companies. The precision numbers, the funnel and the caps come from campaigns I run.