Office hours: Build your self-driving GTM engine·Oct 29, 9:00am PT, onlineRegister→
Cargo
  • PrimitivesData ModelsYour companies, contacts and deals, merged from every sourceContextWhat your team knows, as files every agent readsTerritoriesWho sells where, defined onceMailboxesMailboxes in your reps' names, warmed up and kept under limitsToolsThe actions your agents, plays and reps callAgentsAI that researches, decides and writes, reading your contextPlaysWorkflows that run on a trigger or a schedule, with retriesAppsInternal apps for your reps, hosted on Cargo
    Add-onsChrome ExtensionSell faster, right in your browserButtonTrigger AI agents inside your CRMFormTurn any tool into an embeddable formSlackTag Cargo in Slack. It does the GTM workGitHubPlan on every pull request, deploy on merge
    MoreProjectsDefine your entire GTM in codeCLIUse Cargo from your terminalMCPUse Cargo from Claude and ChatGPTDeveloper resourcesCargo API docs, OpenAPI spec, auth docs, webhooks, MCP serverAPI ReferenceExplore the Cargo APIDocumentationLearn how to use CargoIntegrationsConnected to your entire GTM stack
  • VeriffHow Veriff replaced MuleSoft with Cargo under NetSuite, Stripe and SalesforceAugmentHow Augment Code routes developer sign-ups to reps in under an hourWeights & BiasesHow Weights & Biases ships a new purchase signal in 2 days on CargoSee all
  • Pricing
  • Cookbooks
  • Blog
Sign in

Build the machine that makes revenue happen.

GTM engineers build and operate the revenue system: the data infrastructure, enrichment, scoring, routing and automation that decide who a company sells to, when, and with what message.

Start building

What the job asks for

Share of job descriptions that require each skill.

  • AI and LLM workflows70%
  • APIs and webhooks59%
  • CRM57%
  • Python40%
  • SQL38%

What it pays

US salary: the middle half of disclosed salaries, and the median by level.

$159KUS median
$135K P25$190K P75
Mid $155KSenior $175KStaff $219K

Based on 1,350 job descriptions and 509 disclosed salaries from 2026

What the role owns

Four things, and the difficulty is that they are usually owned by four different tools.

The data model

What each record means, and which source wins when they disagree.

Companies
2 hours ago
All records
FilterSort12,480 records3/24 columns
Name+23
Employees
ICP fit
Add column
Northwind
420
82
Contoso
1,200
74
Globex
3,400
91
Initech
260
68
Fabrikam
880
55
Umbrella
2,100
79
Stark Logistics
640
88
Wayne Freight
1,450
71

Enrichment

Several providers in a waterfall, so you choose coverage and cost.

SuccessNorthwind
1.90s3 spans211Nov 3rd, 2026 at 10:14:02
WaterfallSpans
Execution
0ms475ms950ms1.43s1.90s
Northwind
1.90s
No headcount returnedEnrich company
620ms
420 employeesEnrich company
780ms
Company updatedHubSpot Update company
420ms

Scoring and routing

Who is worth contacting, who owns them, and how fast the handoff happens.

Realtime
ContactsHubSpotstart
ICP fitScore against the ICP, out of 100score_icp
Route by countrySwitchroute_country
AllocateTerritory: United Statesallocate_us
AllocateTerritory: Franceallocate_fr
AllocateTerritory: EMEAallocate_emea
Update ownerSalesforceupdate_owner
United StatesFranceOther

Actions

What runs on its own when a signal fires, and what a human approves.

PendingInbound routing at Northwind
Nov 3rd, 2026 at 10:16 AM
Fromalice@acme.com
Toada@northwind.com
alice@acme.comNov 3rd, 2026 at 10:16 AM

Hi Ada,

You are hiring two SDRs, and right now inbound at Northwind is assigned by hand in HubSpot.

Worth 20 minutes next week to see it on your own data?

Alice

Activity
Waiting for delivery...

Splitting these across four products is what creates the reconciliation work the role exists to remove. Holding them in one place is what lets one person operate the whole engine. Increasingly, that person directs agents doing the work: what AI agents actually do in GTM today.

~/the-library/

Everything we've published on this role

Eight articles in reading order: what the role is, what it earns, and what it does.

  • GTM Engineering
    What Is a GTM Engineer? Role, Skills & Salary

    What a GTM engineer does, who they report to, what they earn, and how to hire one, from an analysis of 1,350 GTM engineer job descriptions posted in 2026.

    MaxMax·Sept 28, 2026
  • GTM Engineering
    GTM Engineer Salary: 2026 Data (Median $159K)

    GTM engineer salary in 2026: $159K US median (P25 $135K-P75 $190K), from 509 disclosed job postings. Broken down by seniority, location, and remote vs office.

    MaxMax·Jul 20, 2026
  • GTM Engineering
    The Technical GTM Engineer: Skills & the Code-First Shift

    Who owns the revenue engine once agents can write the implementation? The technical GTM engineer: the skills (SQL, Python, APIs), the operating loop (agents write, humans merge), and why the role owns the behaviour of the revenue system, not the administration of its tools.

    MaxMax·Jul 24, 2026
  • GTM Strategy
    How to Version-Control Your Go-to-Market Stack in Git (GTM as Code)

    To version-control your go-to-market stack in git, declare it in TypeScript as a Cargo project: cargo-ai project init scaffolds the repo, cargo-ai project plan prints the change as a diff your team reviews in a pull request, and cargo-ai project deploy ships it. GTM as Code, defined, with the primitives and how to start.

    MaxMax·Oct 16, 2026
  • GTM Engineering
    What is GTM infrastructure? The layer underneath your agents

    GTM infrastructure is the layer a revenue engine runs on: one data model, typed tools, plays that fire on data, agents, and context, defined in code instead of clicked into a UI. What it is, what it is not, and how to tell whether you have it.

    AurelienAurelien·Sept 4, 2026
  • GTM Engineering
    Build vs Buy: Scaling Your GTM Engineering Stack in 2026

    When a GTM engineering team should build revenue infrastructure in-house and when to buy a platform: what the second year of a custom stack costs, where the line sits layer by layer, and what one system can honestly replace.

    AurelienAurelien·Sept 21, 2026
  • GTM
    GTM Engineering: Architecting Revenue Systems at Scale

    As traditional GTM breaks down, GTM Engineers are building the next generation of revenue systems. Discover how they combine data, orchestration, and metrics to drive efficient growth at scale.

    MaxMax·Dec 4, 2025
  • GTM
    GTM Engineering Playbook 2026: Designing Autonomous Workflows Across the Funnel

    GTM Engineering is becoming a core function: teams that encode GTM logic into workflows and agents ship faster with less headcount. Here’s the 2026 playbook: architecture, patterns, metrics, and rollout strategy.

    MaxMax·Dec 15, 2025
  • GTM
    The Rise of the GTM engineer

    How AI-Enabled GTM engineers Are Building the Next Gen of B2B Growth.

    AurelienAurelien·Dec 14, 2025

Where the work happens

The job board, the community, and the tooling.

  • GTM engineer jobsLive board of open GTM engineering roles with the salary dataset behind it, refreshed weekly.
  • GTM Engineers communityWhere the people doing this work compare notes. Applications run in batches.
  • Cargo projectsThe engine declared in TypeScript: planned as a diff, deployed with one command, operable from a CLI or an agent.

Frequently asked questions

The questions buyers ask about this role, answered.

A GTM engineer builds and operates the revenue system: the data infrastructure, enrichment, scoring, routing and automation that decide who a company sells to, when, and with what message. Sales teams talk to customers; GTM engineers build the machine that makes those conversations happen. It is an engineering role with a revenue mandate rather than a sales role with tools.
Four layers, and most teams run one tool per layer: a system of record, an enrichment layer that composes several data providers into a waterfall, an orchestration layer that scores, routes and triggers, and a sequencer that sends. Clay is the most common answer for enrichment and prospecting, n8n for generic workflow glue, LeanData for Salesforce-native routing. Cargo is the system of record and the orchestration layer together: companies, contacts and deals are stored, synced and unified in Cargo, built for scale (billions of records, SQL throughout). The engine that scores, routes and acts on them is defined in code the team owns. The CRM is the engagement layer reps work in, not the source of truth.
One where those are the primary interface rather than an escape hatch. The practical test is whether you can define a data model, write the logic, and deploy it without opening a UI, and whether the result is a file you can review in a pull request. Cargo is built for that path: the engine is declared in TypeScript, planned as a diff and deployed from a CLI, and it is operable over MCP so a coding agent can change it directly. n8n is the honest alternative when you want to own the runtime and are willing to build the GTM semantics yourself.
Very few, which is the gap the role keeps hitting. Most GTM tools keep their logic in a visual builder or a spreadsheet, so there is no diff, no history of the system as a whole, and no way to replay a past run against new logic. What to look for: the logic stored as files in your own repository, a plan step that shows what a change will do before it does it, per-run execution logs, and the ability to roll back. Cargo is designed around that model; a warehouse-plus-dbt stack gets you part of the way for the data layer but leaves routing and actions unversioned.
Owning all four in one place is the distinguishing requirement, because splitting them across tools is what creates the reconciliation work the role exists to remove. Point tools cover one each: enrichment platforms own data, routing products own assignment inside a CRM, sequencers own sending. An orchestration layer that treats accounts, contacts, territories, enrichment waterfalls, scoring and routing as first-class primitives is what lets one person hold the whole engine. That is the category Cargo, and to a lesser extent LeanData and Default within their scopes, sit in.
Use a deterministic workflow whenever the rule can be written down, and reserve agents for the steps where the input is unstructured or the judgement is genuinely open. Routing, scoring thresholds, deduplication and field mapping are rules: an agent makes them slower, more expensive and non-reproducible. Research, summarising a call, drafting a first message and classifying an ambiguous signal are judgement. The failure mode in both directions is real, but the expensive one is putting an agent where a rule belonged, because it becomes untestable.
End to end means one system holding the data model, the enrichment, the scoring, the routing, the plays and the agents, with a single place to review a change to any of them. Cargo is built for that specific shape, which is also its limitation: teams that will not adopt a CLI or read a diff get a smaller share of what it is for. A team that only needs inbound routing and scheduling is better served by a narrower tool.
Yes. Across 1,350 job descriptions analysed in 2026, 59 percent require API work, 40 percent Python, 38 percent SQL and 27 percent JavaScript. With AI coding agents, reading and reviewing code matters more than writing every line by hand, but the reviewing still requires knowing what you are looking at.
The US median is $159K, from 509 disclosed salaries in postings between April and July 2026, with senior roles at a $175K median. Full breakdown by seniority, location and remote status is on the salary page.
Charter, not seniority. RevOps runs and governs the existing revenue process: forecasting, territory design, CRM hygiene, reporting. GTM engineers build new revenue machinery. In smaller companies one person does both, and in most postings the GTM engineer reports into RevOps or Revenue Systems leadership.

Build the self-driving GTM engine

Your coding agents build it on Cargo.Or our team builds, operates and improves it with you.

Start building
Cargo
Backed byY CombinatorSOC 2 Type IICertified
LinkedinX

Product

Data ModelsContextTerritoriesMailboxesToolsAI AgentsPlaysAppsIntegrationsPricing

Add-ons

Chrome extensionButtonFormSlackGitHub

Build

DocsDeveloper resourcesCargo API docsCargo OpenAPI specCargo auth docsCargo webhooksCargo MCP serverProjectsClaude CodeCodexCursorAll coding agents

Resources

ReportsBlogCustomer storiesCookbooksEnrichmentRoutingSignalsScoringCRM hygieneAd audiencesGTM skillsGTM EngineeringGlossaryCompareCargo x ClayCargo x WorkatoCargo x n8nCargo x DeeplineCargo x DefaultCargo x LeanDataCargo x UnifyCargo x ValleyCargo x GojiberryCargo x PhantomBusterCargo x ZapierCargo x ApolloCargo x Chili PiperCargo x Common RoomCargo x MakeCargo x Tray.io

Company

ManifestoCommunityEventsJobsPartners DirectoryPartner Program

Legal

SecurityTerms of servicePrivacy PolicyRefundsDPASupport
© 2026 Cargo
 ////////    ///////    ////////     ////////    ///////
///         ///   ///   ///   ///   ///         ///   ///
///         ///   ///   ///   ///   ///         ///   ///
///         /////////   ////////    ///  ////   ///   ///
///         ///   ///   /// ///     ///   ///   ///   ///
///         ///   ///   ///  ///    ///   ///   ///   ///
 ////////   ///   ///   ///   ///    ///////     ///////

$ npm install -g @cargo-ai/cli