# GTM Engineering and RevOps review: research methods

Automation Switch | Evidence retrieved 6 October 2026

This document accompanies the Automation Switch GTM Engineering and RevOps comparison and its reviewed-role CSV. It explains what the role descriptions establish and how to read the comparison.

## Sources and sample

The review contains **17 employer role descriptions: 12 GTM-title descriptions from 12 employers and five adjacent-role descriptions from five other employers**. Sources are public English-language employer career pages and employer-controlled applicant tracking pages. Each retained record was checked against the full available role description.

The GTM title family includes GTM Engineer and Go To Market Engineer, including seniority qualifiers. The adjacent cohort consists of RevOps, revenue systems and marketing operations roles with explicit technical workflow responsibilities. The five adjacent records retain their advertised titles and are excluded from the 12-record GTM denominator.

This is a purposive comparison, not a random sample or an exhaustive directory. One description represents each employer in this edition. Repeated links to the same requisition were not additional observations. Of 19 selected role URLs, 17 provided descriptions suitable for review. Two links returned no usable role description and were excluded. These counts describe selected role URLs, not all search results.

Provider marketing, practitioner accounts and accounts of the term's origins are separately attributed context in the article. They are not employer-role observations and are excluded from the sample counts.

## Reading the evidence table

The CSV preserves each employer, advertised title, location, source links and retrieval date. Responsibilities, systems and experience are summaries of the retrieved description, not verified accounts of daily work.

| Field | Meaning |
| --- | --- |
| `id`, `employer`, `title`, `cohort` | Record identifier, employer, advertised title and GTM-family or adjacent cohort. |
| `source_url`, `resolved_url`, `location`, `retrieved_date` | Original and final source address, advertised location and date the evidence was retrieved. |
| `placement` | Stated team, department or reporting relationship. Departmental placement, collaboration and a named manager are distinct. |
| `work_scope` | Advertised activities such as research, enrichment, routing, execution, reporting or systems ownership. |
| `build_mechanisms` | Configuration, low-code automation, APIs, code, queries or other implementation methods described. Native platform automation counts as implementation work. |
| `systems` | Systems or tools named in the description. Inclusion does not imply that each is mandatory or currently deployed. |
| `human_review_or_governance` | Explicit review, testing, permissions, documentation, reliability or ownership provisions. The description does not establish their effectiveness in practice. |
| `experience` | Requested experience, including mixed or qualitative requirements where present. |
| `supporting_phrase`, `interpretation_note` | A short source phrase or heading and a clarification needed to interpret the record. |
| `vacancy_status` | Whether availability was independently confirmed. It was not independently confirmed for these records. |

**Not stated** means the retrieved text does not establish the fact. It does not mean the responsibility is absent. A department is not automatically a direct reporting line. An employer's target or commercial remit is not evidence of an achieved result.

The Roboflow record uses the page heading **RevOps Analyst**. Its body also uses RevOps Analyst / Sr. Salesforce Administrator. It remains in the adjacent cohort; a different historical title is not assumed.

## Limitations

Sources were reviewed through one AI-assisted research process without independent second coding. Classification error remains possible, and inter-rater reliability was not measured.

The sample is concentrated in US and technology-company sources. The cohorts are not matched for seniority, employer size or geography. They show examples of overlap and variation, not the prevalence of responsibilities, the superiority of one title, a universal organisational boundary or a guaranteed route into employment.

Retrieval date is not posting date. A readable description does not confirm an open vacancy, and source pages can change or disappear. The dataset describes the retrieved evidence, not a live jobs feed.

The article's routing workflow and evaluation worksheet are illustrative. No operational experiment was run and no workflow-performance or revenue outcome was measured for this review. A proposed test is not a result. Claims about actual efficiency, quality or revenue would require separate evidence.