- GTM Engineering isn't a new discipline. It's RevOps repriced at engineering-level comp.
- Bloomberry found GTM Engineering postings grew 205 percent year over year at a $127,500 median salary, and 9 of the 10 listed responsibilities match traditional RevOps work. The gtm-skills GTM Engineer pack covers that stack in 7 free skills with no free-tool version, because routing rules and scoring models only mean something wired into live pipeline data.
- Install the skills or wire the Intempt agent to the pipeline directly.
GTM Engineering job postings grew 205% year over year, with a median salary of $127,500, according to Bloomberry's analysis of 1,000 live postings. That's a real hiring signal, not a trend piece.
But Bloomberry's own breakdown of the role's responsibilities found something worth sitting with: 9 of the 10 most commonly listed duties match work RevOps teams already do - lead routing, scoring, workflow automation, pipeline reporting. The honest framing isn't that a brand-new job appeared. It's that RevOps work is getting repriced at engineering-level comp, with SQL and Python each showing up in 38% of postings and 4.11 years of average experience required.
| Metric | Number | Source |
|---|---|---|
| GTM Engineering postings, year over year growth | 205% | Bloomberry |
| Median salary | $127,500 | Bloomberry |
| Average years of experience required | 4.11 years | Bloomberry |
| Postings listing SQL as a requirement | 38% | Bloomberry |
| Postings listing Python as a requirement | 38% | Bloomberry |
| Listed responsibilities that match traditional RevOps work | 9 of 10 | Bloomberry |
If you already do this work under a RevOps title, the real question isn't whether AI replaces the role. It's whether your actual skill set matches what's now labeled "GTM Engineer" on a job posting and priced accordingly. That's an upskilling question, not a replacement one, and it's what this pack is built to answer.
TL;DR
- GTM Engineering postings grew 205% year over year with a $127,500 median salary (Bloomberry), and 9 of 10 listed responsibilities match traditional RevOps work.
- gtm-skills' GTM Engineer pack is 7 free skills: lead-to-opportunity routing and scoring, lead assignment logic, workflow automation design, call transcript mining, sales enablement collateral, competitor research, and a pre-launch readiness check.
- Install once with npx skills add sidchaudhary/gtm-skills.
- There's no free tool version of this pack - routing rules, scoring models, and SLAs only mean something wired into live pipeline data.
- Start with the-routing-engine - lead handoff is the most common break point between marketing and sales.
- Intempt's GTM Engineer agent runs this same logic continuously against live pipeline data instead of as a one-time design doc.
How to install these in about 60 seconds
- Run npx skills add sidchaudhary/gtm-skills.
- Create a Claude project per skill - "Routing Engine," "Transcript Miner."
- Paste the skill's SKILL.md into the project instructions.
- Start a chat with your lead criteria, call transcript, or workflow description.
The 7 skills
7 skills now covering the layers a GTM Engineer owns end to end: designing the lead-to-opportunity scoring model, the assignment logic once a lead qualifies, general-purpose workflow automation, transcript mining after a call, sales collateral by persona and stage, structured competitor research from public sources, and a pre-launch readiness gate.
| Skill | What it does |
|---|---|
| 1. The Routing Engine | Designs the MQL scoring model, routing rules, and speed-to-lead SLAs between marketing and sales |
| 2. The Lead Router | Designs the assignment logic for a qualified lead - round-robin, territory, or score-threshold - with tie-break and fallback rules |
| 3. The Workflow Builder | Designs trigger-condition-action automation workflows, with branching logic and error handling |
| 4. The Transcript Miner | Extracts deal signals, objections, and a stakeholder map from a raw sales call transcript |
| 5. The Enablement Kit | Produces sales collateral - one-pagers, ROI calculators, proposal templates - mapped to persona and deal stage |
| 6. The Competitor Dossier | Builds a structured competitor profile from their public website: positioning, pricing, strengths and weaknesses |
| 7. The Launch Gate | Runs a go/no-go checklist before a launch: stock, page, tracking, flows, support, margin |
1. The Routing Engine
Designs the lead-to-opportunity layer between marketing and sales: MQL scoring model, routing rules, speed-to-lead SLAs, and lifecycle stage definitions. Use it when leads aren't reaching sales fast enough, or marketing and sales disagree on what counts as qualified. Read the skill.
2. The Lead Router
Designs the actual assignment logic for a lead that's already qualified - round-robin, territory, or score-threshold - with explicit tie-break and fallback rules. The layer right after the-routing-engine: once a lead clears the bar, deciding who actually gets it. Read the skill.
3. The Workflow Builder
Designs marketing and sales automation workflows: trigger-condition-action patterns, branching logic, error handling, and retries at every step. The general-purpose layer underneath everything else in this pack. Read the skill.
4. The Transcript Miner
Takes a raw sales call transcript and extracts deal signals, objections, confirmed pain points, and a stakeholder map. Use it before writing a follow-up email or updating a CRM record, so nothing from the call gets lost. Read the skill.
5. The Enablement Kit
Produces sales collateral - one-pagers, ROI calculators, proposal templates, and playbooks - mapped to buyer persona and deal stage. For when a rep needs a specific asset for a specific deal, not a generic template. Read the skill.
6. The Competitor Dossier
Researches a competitor from their public website and builds a structured profile: positioning, pricing, strengths and weaknesses. For real research on one specific competitor, not a one-off talking point. Read the skill.
7. The Launch Gate
A one-time go/no-go gate before a launch, restock, or spend increase: stock, page, tracking, lifecycle flows, support, and margin, as a checklist the launch owner signs off against. For when finding a gap after go-live is expensive. It's a single pre-launch pass, not ongoing automation - that's the-workflow-builder. Read the skill.
Why there's no free tool for this pack
Every other job in this series has at least one free tool that runs the skill live in the browser. This one doesn't, and it's worth explaining why instead of repeating an old claim that it was the plan from day one.
The honest history: this was an unexamined gap, not a considered decision. Nobody sat down and decided a GTM Engineer pack should ship with zero tools. It just never got one.
What changed is the search data. Testing this year covered the obvious tool-shaped ideas for this pack - a lead scoring calculator, a lead routing generator, an SLA calculator, a workflow generator - and every one of them came back with zero measurable search volume. Nobody is searching for a paste-and-generate version of this work.
That result holds up for a structural reason, not just a keyword accident. A routing rule, a scoring model, or an SLA commitment only means something once it's wired into live pipeline data: actual lead volume, actual rep capacity, actual response times. A stateless tool that takes a text description and outputs a generic scoring model isn't solving the GTM Engineer's problem. It's just reformatting the same guesswork the role exists to remove. The skill works as a design pass with a human reading the output. The job itself only works connected to a live CRM.
Intempt's GTM Engineer agent runs this same routing and scoring logic against live pipeline data continuously, not as a one-time paste-and-generate pass.
The order to build them in
Start with the-routing-engine. Lead handoff between marketing and sales is the most common break point in any pipeline, and fixing the scoring model and lifecycle stages changes downstream conversion more than any other single change. Add the-lead-router right after, since it's the layer that completes the handoff once a lead is qualified. The-workflow-builder comes next, once you know what the routing and assignment logic actually needs to trigger. The-transcript-miner is worth adding once calls are happening regularly enough to be worth mining systematically. Save the-enablement-kit and the-competitor-dossier for when a specific deal or a specific competitor needs deeper prep.
What to never hand over
The actual SLA commitment to sales. The-routing-engine designs a speed-to-lead target, but promising reps a number your team can't operationally hit is a leadership call, not a generated one. And competitive claims about a rival's weaknesses should never go external without a human checking them against the-competitor-dossier's actual sourcing - that kind of research ages fast, and a wrong claim about a competitor does more damage than no claim at all.
When you outgrow the manual version
Intempt's GTM Engineer agent wires this same layer into live workflows: stage transitions, lead routing, task creation, and Slack alerts that run without manual input, while it monitors deal age and flags risk before deals fall through the cracks. Same six jobs, running as infrastructure instead of a one-time design doc you write once and forget.
Frequently asked questions. Answered.
Not based on the job description itself. Bloomberry's breakdown of the role found that 9 of the 10 most commonly listed responsibilities match traditional RevOps work - lead routing, scoring, workflow automation, pipeline reporting. The honest read is that RevOps work is getting repriced at engineering-level comp and given a new title, not replaced by a new discipline.
