How GTME Pulse Counts Jobs, Pay, and Market Signals
Every newsletter number starts with a public job listing or a sourced news item. The method below governs the Monday briefing, homepage market proof, and job archive. Survey-based salary pages use a separate survey methodology and must keep their survey denominator visible.
Four Counts, Four Meanings
| Label | Meaning | Current repository evidence |
|---|---|---|
| Active listings | Qualified listings present in one current weekly export after deduplication and taxonomy review. | 30 in Issue #24, dated August 17, 2026 |
| Qualified historical listings | Unique candidate listings accepted by the role taxonomy across retained dated snapshots. | 177 |
| Unique candidates reviewed | Deduplicated listings evaluated before the role-scope filter. | 212 |
| Usable compensation records | Qualified listings with an annual salary range whose midpoint falls inside the plausibility band. | 99 |
Snapshot rows are a pipeline volume measure. They aren't unique jobs. The retained files contain 1,180 rows across 17 snapshots, which collapse to 212 unique candidate listings. Repeated appearances of one job count once in the historical listing denominator.
Role Taxonomy
Core roles contain GTM Engineer, GTM Engineering, go-to-market engineer, or go-to-market engineering in the title. The historical sample contains 151 core listings.
Adjacent roles start with a narrow title set such as GTM Systems Engineer, Revenue Engineer, Growth Engineer, Marketing Automation Engineer, or Sales Automation Engineer. The description must contain at least two commercial-scope signals and two technical-scope signals. Commercial signals include GTM, RevOps, CRM, outbound, demand generation, revenue team, and pipeline. Technical signals include automation, APIs, integrations, data pipelines, code, AI, enrichment, and orchestration.
Product software work is screened separately. Listings with dense frontend, backend, mobile, DevOps, distributed-systems, or product-engineering language fail the adjacent rule. The retained history accepts 26 adjacent technical listings and excludes 35 candidates.
Deduplication
The pipeline uses the source job ID when available. A direct job URL is the next key. Title, company, location, and posting date form a fallback key when neither exists. The version with the more complete description is retained for taxonomy review. A listing can reappear in several dated snapshots without increasing the unique historical count.
Compensation
Posted-pay analysis uses employer-disclosed salary ranges in USD. A missing bound is treated as a single-point estimate. The annual range midpoint must fall between $50K and $500K. Hourly, monthly, equity, bonus, commission, and total-compensation figures stay outside the base-salary midpoint unless the source provides a defensible annual base conversion.
The historical qualified sample has 99 usable annual records and a $150K median range midpoint. The latest issue reported a 73.3% disclosure rate. Issue-level medians describe that weekly sample. Historical medians describe the retained cross-snapshot sample.
Skills, Tools, and Companies
Tool and skill mentions come from the qualified listing descriptions in the same issue. A mention shows employer demand in the observed sample. It doesn't prove product adoption across the whole market. Percentages use the qualified active listing count as the denominator.
Company tables count qualified active listings by employer. A company's appearance means the source export found at least one qualifying listing. It doesn't establish a partnership with GTME Pulse, a company-wide hiring plan, or a future opening.
Current Events and Early Signals
Current events come from a seven-day Google News RSS query with the original source name, publication date, and link retained. Titles must contain explicit GTM, RevOps, sales-automation, marketing-automation, or relevant tool-and-technical-change language.
Funding, acquisition, launch, leadership, and workflow-change items are research leads. They aren't counted as jobs. The issue tells readers to check the company careers page and technical GTM leadership before treating a signal as an opportunity.
Freshness and Failure Rules
Each issue carries its source date. The automated send aborts when the current job export is more than eight days old or contains zero qualified listings. The job archive displays a freshness warning and never labels an older repository export as open roles. A feed failure removes the news section instead of filling it with unsourced material.
Known Limits
- Job boards can remove, duplicate, or rewrite listings between collection runs.
- New role names can fall outside the adjacent title set until a human reviews the pattern.
- Pay-transparency laws make disclosure rates uneven by location and company type.
- Tool mentions can appear in preferred qualifications without being central to the role.
- Weekly changes can reflect listing churn. Four-week direction carries more weight than one issue.
Corrections are welcome through the About page. Compare the current sample in the issue archive, then review survey and posted-pay benchmarks with their separate denominators. The taxonomy and counts will change when stronger evidence supports a revision.