GTM Engineer Job Description Template
Most GTM Engineer job postings are recycled SDR descriptions with "automation" sprinkled in. That attracts the wrong people. Here's a template built from 200+ real postings and hiring manager interviews.
Why Most GTM Engineer JDs Fail
The GTM Engineer role didn't exist three years ago. Companies writing job descriptions for it often copy-paste from adjacent roles and hope for the best. The result: postings that read like a mashup of SDR, Sales Ops, and Marketing Ops descriptions with no coherent identity.
Three problems show up repeatedly. First, the responsibilities section lists tasks from three different roles without prioritizing any of them. A candidate reading "manage CRM hygiene, build outbound sequences, create marketing reports, and maintain API integrations" has no idea what their actual day looks like. Second, the required skills section is a wish list rather than a filter. Requiring Python, SQL, Clay, HubSpot, Salesforce, JavaScript, and Tableau simultaneously means you're describing a unicorn who doesn't need your job. Third, most postings omit compensation. In a market where GTM Engineer salaries range from $95K to $250K, hiding the number wastes everyone's time.
The template below fixes these problems. Copy it. Modify the bracketed sections. Post it.
The Template: Senior GTM Engineer
Title: Senior GTM Engineer
Location: [City, State] / Remote / Hybrid
Salary: $150K-$190K base + equity
Reports to: [VP Sales / Head of Growth / CRO]
About the Role
You'll own the outbound revenue pipeline from data sourcing through meeting booked. That means building and optimizing enrichment workflows, designing multi-channel sequences, managing sending infrastructure, and measuring pipeline output. You're the person who turns a target account list into qualified meetings on the calendar.
This is a builder role. You'll spend 60% of your time in Clay, sequencing tools, and CRM automation. 20% on data analysis and reporting. 20% on cross-functional work with sales and marketing teams. You won't manage people or run demos. You build the systems that generate the pipeline.
Core Responsibilities
Pipeline infrastructure. Build and maintain enrichment workflows in Clay. Design waterfall enrichment sequences across 3-4 data providers. Target: 75%+ email coverage on all target lists. Manage 10-20 sending domains, warmup schedules, and deliverability monitoring.
Outbound execution. Design, launch, and optimize multi-step email and LinkedIn sequences. Own A/B testing for subject lines, copy, and send timing. Target: 4%+ reply rate, 50%+ positive reply-to-meeting conversion.
CRM operations. Ensure clean data flows from enrichment through CRM. Build automated lead routing, scoring models, and lifecycle stage transitions. Maintain data hygiene through automated deduplication and decay management. For CRM specifics, see our CRM hygiene playbook.
Measurement and reporting. Track pipeline generated, cost per meeting, and revenue attribution from outbound. Build weekly dashboards. Present results to leadership monthly. Identify bottlenecks and fix them without being asked.
Required Skills
Must-have:
2+ years building outbound automation systems (not just configuring existing ones). Proficiency in Clay or equivalent orchestration platform. Experience with Instantly, Smartlead, or Outreach for email sequencing. Working knowledge of HubSpot or Salesforce administration. Understanding of email deliverability: SPF, DKIM, DMARC, domain warmup, inbox placement. Ability to analyze campaign data and make optimization decisions independently.
Nice-to-have:
Python scripting for data transformation and API integration. Experience with Make or n8n for workflow automation. Familiarity with intent data platforms (6sense, Bombora). Previous work in B2B SaaS with $30K+ ACV deals.
What We Offer
$150K-$190K base salary depending on experience and location. [X]% equity with 4-year vesting. Full benefits. $2,000/year tool budget for personal development. Remote-friendly with optional [City] office.
Modifying for Seniority Levels
Junior/Associate GTM Engineer ($95K-$130K). Change "own" to "support." Remove the measurement and reporting responsibility (they'll learn it, not own it). Drop Python from required skills. Add "mentorship from senior GTM team" to the benefits. Emphasize learning trajectory over existing expertise. For junior salary benchmarks, see the junior salary page.
Mid-Level GTM Engineer ($120K-$160K). The template above works nearly as-is. Reduce experience requirement to 1-2 years. Keep all responsibilities but frame measurement as "contribute to" rather than "own." Most GTM Engineer postings target this level.
Lead/Staff GTM Engineer ($180K-$250K). Add team leadership: "Mentor 1-3 junior GTM Engineers." Add strategy: "Define ICP criteria and target account selection methodology." Add architecture: "Design the end-to-end data infrastructure connecting enrichment, sequencing, CRM, and analytics." Require Python. Require experience at scale (50K+ contacts/month, 20+ sending domains). Check lead/staff salary data for current benchmarks.
Screening Criteria: What to Test
Resumes tell you what someone claims. Screening tells you what they can do.
Resume red flags. "GTM Engineer" titles at companies that don't have outbound motions (likely renamed SDR or Marketing Ops roles). Tool lists longer than 15 items (breadth without depth). No mention of metrics or outcomes. Phrases like "helped with" or "assisted in" without ownership language.
Resume green flags. Specific pipeline numbers ("generated $2.4M in pipeline from cold outbound in Q3"). Named tools with context ("built 12 Clay tables processing 8,000 contacts/month"). Evidence of infrastructure ownership ("managed 15 sending domains with 94% inbox placement"). Links to a portfolio or case studies.
Technical screen (30 minutes). Ask them to walk through a Clay table they've built. If they can't describe column types, enrichment sources, and filter logic in detail, they haven't done the work. Ask about deliverability setup for a new domain. The right answer involves DNS records, warmup timelines, and volume ramp. "I just used Instantly's warmup" is insufficient for a senior role. See our interview question bank for more screening ideas.
Take-home exercise (optional, 2 hours max). Give them a target ICP and ask them to design an enrichment and outreach workflow in a written doc. No need for them to build it in Clay. You're testing their system thinking: data sources, enrichment order, verification steps, sequencing logic, measurement plan. The best candidates include fallback scenarios and cost estimates.
Common Mistakes in GTM Engineer Hiring
Requiring enterprise sales experience. GTM Engineers don't sell. They build the systems that feed the sales team. Requiring "5+ years in B2B sales" filters out the best technical candidates. Look for automation experience and data fluency instead.
Conflating GTM Engineer with SDR Manager. An SDR Manager coaches reps and reviews calls. A GTM Engineer writes Clay workflows and manages sending infrastructure. These are fundamentally different jobs. If your real need is an SDR Manager, don't post a GTM Engineer role. The GTME vs SDR ROI analysis covers this distinction in depth.
Skipping the salary band. The market for GTM Engineers is competitive. Companies that post salary bands get 2-3x more qualified applicants. The candidates you want have options. Transparency signals respect for their time.
Over-indexing on tool-specific experience. A strong GTM Engineer can learn a new tool in a week. Clay expertise matters, but a candidate who's built similar systems in Apollo, Outreach, or custom code will ramp fast. Test for system thinking and automation instincts, not checkbox tool familiarity.
Where to Post
LinkedIn is the default. But GTM Engineers also cluster in specific communities. Post in the Clay Community Slack, the GTM Engineer School Discord, and on Twitter/X with the #GTMEngineer hashtag. Niche channels outperform generic job boards for specialized roles. Our hiring guide covers sourcing strategy in more detail.
Frequently Asked Questions
What should a GTM Engineer job description include?
A strong GTM Engineer JD covers five areas: core responsibilities (pipeline building, enrichment, sequencing), required technical skills (Clay, Python, APIs), tools they'll use daily, measurable KPIs, and a transparent salary band. Vague descriptions attract the wrong candidates.
What salary range should I list for a GTM Engineer?
Mid-level GTM Engineers earn $120K-$160K base in major tech hubs. Senior roles reach $180K-$220K with equity. Listing a salary band increases qualified applicant volume by 30-50% compared to hiding compensation.
Should I require Python for a GTM Engineer role?
Depends on your stack complexity. For Clay-centric workflows with minimal custom code, Python is a plus, not a requirement. For teams building custom API integrations, data pipelines, or LLM-powered scoring, Python is mandatory. Be honest about which one your role needs.
How is a GTM Engineer different from a Sales Ops role?
GTM Engineers build automated outbound systems from scratch using code, APIs, and orchestration platforms. Sales Ops manages existing tools, reporting, and process optimization. GTM Engineers create infrastructure. Sales Ops maintains it. See our full comparison for details.
Source: State of GTM Engineering Report 2026 (n=228). Salary data combines survey responses from 228 GTM Engineers across 32 countries with analysis of 3,342 job postings.