Home / GTM Engineering

How to Write a GTM Engineer Job Description (Free Template)

By the PaddockGTM team. Updated October 2026.

A good GTM engineer job description says what the person will own, what success looks like in 90 days, and which one or two tools actually matter. Everything else is noise that scares off the people you want.

Search "GTM Engineer" on LinkedIn and you'll see the two failure modes. Half the posts list every tool on the market: Clay, Apollo, HubSpot, Salesforce, n8n, Zapier, Make, Python, SQL, Smartlead, Instantly, Gong. The other half say "high IQ, hard working, startup mindset" and stop. Strong operators skip both, because neither tells them what the job is.

The 5 things every GTM engineer JD needs

  1. The outcome, in one sentence. "Build our outbound engine from zero to 30 qualified meetings a month." Not "drive growth."
  2. The current state. What exists today? A founder doing sales from Gmail? A HubSpot nobody updates? Operators want to know what they're walking into.
  3. The archetype. Do you need a seller who builds, a growth marketer, a RevOps builder or a data builder? (Here's the difference.)
  4. Must-have vs nice-to-have tools. Two or three musts. The rest are learnable in a week.
  5. Proof you want to see. Ask for a Loom, a workflow screenshot or a write-up of one system they built. This filters better than any resume.

Copy-paste template

# GTM Engineer (Founding) at [Company]

[Company] builds [one line on product] for [who buys]. We've closed [X] customers through founder-led sales and raised [round] from [investors]. Now we need someone to turn what's working into a repeatable pipeline engine.

## What you'll own
- Outbound from zero: ICP, lists, enrichment, messaging, sending infrastructure
- [Second outcome, e.g. inbound lead routing or a signal-based motion]
- Weekly reporting on what's working, so we scale it

## What success looks like
- 30 days: first campaigns live, sending infrastructure set up
- 60 days: [X] qualified meetings booked, messaging iterated weekly
- 90 days: a repeatable motion with numbers we trust

## You might be a fit if
- You've built an outbound or pipeline system that booked real meetings
- You can talk to buyers, not just build workflows
- You've worked somewhere with no playbook

## Tools
- Must: [2–3 tools you actually use, e.g. Clay, HubSpot]
- Nice to have: [the rest]

## How to apply
Send a 3-minute Loom walking through one system you built: what it did, how it worked, what the results were.

## Comp
[Base range] + [equity range]. [Remote / hybrid / in-person, location].

Why posting the salary range matters

Several US states and cities now require pay ranges in job posts, so check the rules where you hire. Even where it isn't required, a clear range gets you more serious applicants and saves both sides a wasted first call.

What to cut

FAQ

What should a GTM engineer job title be? "GTM Engineer" or "Founding GTM Engineer" is clearest in 2026. If the role is mostly selling, "Founding AE (technical)" also works.

Should I require coding skills? Only if the role is data-heavy. For most seed roles, comfort with Clay, n8n and AI tools matters more than code.

Want us to write your JD and send you vetted candidates? Book a 30-minute call →

Looking for a GTM role with a clear scope and real comp? Introduce yourself →

Keep reading