On this page
GTM engineer is a new title. Plenty of people do the work: they build the outbound systems, the enrichment pipelines and the CRM plumbing a sales team runs on. Far fewer have changed their job title to match.
So a search for the title finds the few who adopted the word. We wanted to know how few, so in November 2026 we searched GitHub from both ends.
Two searches, two very different counts
Start from the title. 317 GitHub users say "GTM engineer" or "GTM engineering" in their bio. We read 304 of them, with their own recent repos (not forks). 139 have built GTM work in their own repos since January 2025: outbound, enrichment, lead scoring, CRM syncs, signal tracking.
Start from the work. We searched repos about outbound automation, lead enrichment, cold email and Clay enrichment, and repos tagged gtm or gtm-engineering, and read the 1,080 people who own them. 885 of them pushed that kind of work since January 2025.
Of those 885, 67 say GTM, go-to-market, RevOps or growth engineer in their bio. 453 have no bio at all.
A search by title would have found fewer than one in ten of the people doing the work.
They are new and quiet
The usual shortcuts on GitHub are stars and followers. They don't work here.
- New accounts. 351 of the 885 opened their GitHub account in 2025 or 2026. Of the 201 repos tagged
gtm-engineering, 176 were created since May 2026. - No audience. The median follower count is 1. 717 of the 885 have fewer than 10 followers.
- No location, often. 364 of the 885 say where they are.
Sorting by stars or followers puts the people who write about GTM engineering first, and pushes the people building it off the page.
What they build
Across the 885, counted from repo names and descriptions (keyword matches, so read them as rough):
| Work in their own repos | People |
|---|---|
| Outbound and cold email: sequences, sending, deliverability | 522 |
| Enrichment and list building: finding contacts, waterfalls, scraping | 412 |
| AI agents and Claude Code skills for sales and marketing | 387 |
| Workflow automation in n8n or Make | 241 |
| Lead scoring and ICP fit | 241 |
| CRM and RevOps plumbing: HubSpot, Salesforce, Attio syncs | 203 |
| Buying signals and intent: job posts, funding, tech changes | 166 |
| Clay, by name | 115 |
A lot of Clay work never reaches GitHub, because it lives in Clay tables. The people above are the ones who also write code around it, which is usually what a "GTM engineer who codes" role is after.
What to read in a GTM engineer's repos
You don't need to read the code line by line. Look for four things.
- Does it run, or did it run once? Scheduled jobs (GitHub Actions, cron, n8n triggers), retries and error handling show a system a team could rely on. A single notebook shows an experiment.
- Does the README name the funnel problem? "Finds companies hiring for X from their job posts" is a GTM engineer talking. "Lead scraper" is a script.
- Does it protect the sending domain? Dedupe, suppression lists, unsubscribes, bounce handling and per-domain caps are the boring parts. People who have run outbound at volume write them, because they learned what happens without them.
- Does it say what happened? Reply rates, meetings booked, a before and after. Few repos do. The ones that do tell you the person measures their work.
Then ask for a walkthrough of the Clay table or workflow the repo feeds. The repo shows the engineering; the walkthrough shows the GTM judgment.
How to run the search yourself
On GitHub:
- Search repos for the work, in the words such repos use:
outbound automation,lead enrichment,clay enrichment,topic:gtm-engineering. - Keep the owners who are people, not organizations, and read their recent repos.
- Search bios too (
"gtm engineer" in:bio), but treat that as the small half. - For a place, add
location:to a user search. Repos have no location, so you have to go through people for that part. We wrote up how.
What AyHire does with a GTM role
AyHire reads the role and plans its GitHub searches in the words GTM repos use (outbound automation, lead enrichment, the tools the role names), adds a bio search for the title, then reads each person's own repos and judges them against the role's criteria, with the evidence for each call.
We list numbers here, not people: the developers didn't ask to be on a page about hiring. Run the search and you get the names, the repos and the reasons. A GTM engineer who builds outbound and enrichment systems or a GTM engineer who codes, with Clay and n8n, in London opens AyHire with that role typed in; change it to yours. 14 days free, no card.
The searches ran on GitHub on 8 November 2026. "GTM work" means a repo, pushed since January 2025, whose name or description has words like outbound, enrichment, lead, CRM, signal or Clay. GitHub returns at most 1,000 results per search, so the counts are of what it returned that day, not of everyone.