How we measure.

What counts as an "AI GTM" role

The index covers go-to-market roles (sales, marketing, RevOps, growth, customer success, post-sales, BD, partnerships, and supporting engineering) at AI-native companies — companies whose core product is built on or around AI. The company list is curated, not algorithmic: we add companies manually as they raise, launch, or otherwise enter the AI-native universe. The active company count shown in totals is the number flaggedactive = true in our database.

Index refresh & dead links

Each company's careers page is scraped on a continuous schedule from its source ATS (Greenhouse, Lever, Ashby, Workable, custom). When a role disappears from source, it's marked closed and excluded from all research totals. The "live roles" count is the number of postings currently status = 'published'.

Tech stack extraction

Tools are extracted from each job description against a curated dictionary of ~150 named tools (Clay, Apollo, Instantly, HubSpot, Salesforce, Gong, Outreach, etc.). Extraction is dictionary-based with word-boundary matching — no fuzzy inference. A role counts once per tool regardless of how many times it's mentioned. The "share" column is the percentage of all live roles that mention the tool at least once.

Salary normalization

We use only salaries the company published directly in the job posting. Hourly rates are annualized at 2,080 hours. Non-USD currencies are converted at a fixed reference rate (USD = 1, EUR = 1.08, GBP = 1.27, CAD = 0.73). Midpoints below $30k or above $1M are excluded as data-entry errors. The "midpoint" is the mean of the disclosed min and max; if only one is disclosed, that value is used.

Seniority buckets

Inferred from the role title with regex, in this order: Intern/Grad, Junior, Staff+, Lead/Manager, Senior, Mid. Examples: "Senior Software Engineer" → Senior; "Head of Growth" → Lead/Manager; "Staff RevOps Architect" → Staff+; "Marketing Analyst" → Mid. Roles whose title doesn't match any bucket are excluded from the salary-by-seniority chart.

Region buckets

Locations are bucketed by city/country keyword: US — West (SF Bay, LA, Seattle, etc.), US — East (NYC, Boston, DC, etc.), US — Central (Austin, Chicago, Denver, etc.), UK & Ireland, Europe, Canada, Asia-Pacific, Remote, Other. Roles with no location string and remote = true are counted under Remote.

Comp by tool

For each tool, the median midpoint salary across all roles that mention it AND disclose comp. Tools with fewer than 10 disclosed-salary samples are excluded. The sample size n is shown on every bar.

External benchmarks

The national-benchmark salary table is from the Stack Overflow Developer Survey 2024. It's labelled as external on the Insights hub. It is not SVGTM data and is shown only as a sanity check against our AI GTM-specific medians. As an external dataset it does not refresh with our index.

What we deliberately don't publish yet

We don't publish trend or time-series metrics — hiring velocity, week-over-week deltas, 30-day tool momentum, or "rising and cooling" rankings — until we have enough continuous ingest history to back them with confidence. We're archiving a frozen snapshot of the dataset every month at /research/{YYYY-MM}, and we'll release trend reporting once those snapshots can sustain it.

We also don't publish anything we can't audit row-by-row. Every chart links to the underlying roles on the board so anyone can click through to the raw source.

Citation

All SVGTM research is free to cite under CC BY 4.0. Cite as: SVGTM AI GTM Hiring Report, {Month Year}. https://svgtm.com/research. For press logos and boilerplate, see the press kit.