Most job descriptions for this role are a list of tools with a paragraph of ambition on top. Here is a version built around what the person will be held to, plus the template at the end.
The three sections that matter
1. The number. One, not five. Qualified meetings per month. Minutes to first contact. Percentage of closed revenue traceable to a source. If you cannot name it, the role is not ready to hire, and that is worth knowing before you post.
2. The decisions they own. Can they change a sequence without approval? Change routing? Pause a campaign that is burning budget? Add a field to the CRM? Write down the answers. A role with no decision rights produces a ticket taker, and the number will not move.
3. The systems they are accountable for. Everything between a lead arriving and a human closing: enrichment before contact, scoring, routing, channels, the write backs into the record, and the traceability from revenue to source.
Tools go at the bottom, under context, where they belong.
What to delete
- "Rockstar", "ninja", "wear many hats". The last one is a warning that the role is undefined.
- Ten years of experience with a tool that is four years old.
- Degree requirements, unless legally required. Many strong people in this field came from operations, sales or support.
- Every tool you own. List the stack as context, not as a checklist. Someone who has run Clay and n8n will learn your CRM faster than someone who knows your CRM will learn systems thinking.
The template
Copy from here.
Role: GTM Engineer Reports to: the person who owns the number below Location: remote, with overlap to our working hours
The number you own [Example: qualified meetings booked per month, from 30 to 60 within two quarters.]
What you will be accountable for
- Leads are enriched, scored and routed before anyone contacts them
- First contact happens within [X minutes] of a lead arriving
- Every outbound channel writes its outcome back onto the record
- We can trace closed revenue back to the campaign and list that produced it
- A second person can operate what you build, from documentation you wrote
Decisions you can make without asking
- Change sequences, scripts and routing rules
- Pause any campaign that is not producing
- Add or change fields in the CRM, within the naming convention
- Choose tools under [budget threshold]
What we already have [CRM, enrichment, automation platform, calling or messaging, reporting. Plain list, no adjectives.]
How we will evaluate the first 90 days
- Days 1 to 30: you can describe our funnel end to end and have found the biggest leak
- Days 31 to 60: one system in production, documented, with an owner
- Days 61 to 90: the number has moved, and you can explain why
What this role is not Not a sales quota. Not managing people. Not owning the message or the brand.
How to apply Send one thing you built that someone else now operates. Tell us the problem, what you did, what it produced and who runs it today. Four paragraphs is plenty.
Why that last line matters
It does two jobs. It filters for people who have shipped rather than studied, and it gives you a comparable artifact from every applicant, which makes the shortlist fast.
If you would rather read the work first
MitHub publishes open profiles where exactly that is already written out, with the technologies attached to each deployment. Browsing and contacting anyone is free.