Why this role exists

Most GTM teams are bottlenecked by manual work: researching accounts one by one, stitching data between tools, writing outreach that reads like a template because it is a template. We're hiring someone to make that bottleneck disappear.

A GTM Engineer sits between growth, sales, and engineering. You won't own a quota and you won't ship product — you'll build the systems that let a small team run outbound, enrichment, and lifecycle motions at a scale that would otherwise require twenty people. If you've ever looked at a sales workflow and thought "this should be a script," this is the job.

What you'll do

Build and own the GTM data layer

Design enrichment and scoring pipelines that turn raw firmographic, technographic, and intent signals into a ranked, actionable account list
Keep CRM data clean and trustworthy — dedupe logic, field hygiene, lifecycle stage rules, territory routing
Stand up reverse-ETL between the warehouse and GTM tools so sales works off the same numbers as the data team

Automate the pipeline

Ship outbound systems end to end: sourcing → enrichment → qualification → sequencing → routing → reporting
Build LLM-assisted research and personalization workflows that hold up under volume without sounding generic
Automate the handoffs nobody likes doing manually — inbound lead routing, PQL alerts, churn-risk flags, meeting prep briefs

Instrument and measure

Own attribution and funnel reporting closely enough that you can explain any number to the CEO
Run experiments on messaging, targeting, and channel mix; kill what doesn't work quickly and without ego
Build dashboards people actually open

Partner with the humans

Sit with AEs and SDRs, watch how they work, and remove the friction you find
Translate between "the sales team wants X" and what's actually buildable
Document what you build so the system survives you being on vacation

What we're looking for

2–5 years in growth engineering, revenue operations, sales engineering, founding GTM, or an adjacent role where you built things rather than just operated them
Working code, not just no-code. Comfortable with Python or JavaScript for scripting, SQL for analysis, and REST APIs / webhooks for integration. You don't need to pass a LeetCode round; you do need to debug a failing API call at 11pm without help
Fluency in the modern GTM stack. Clay or equivalent enrichment tooling, a CRM (HubSpot or Salesforce), an outbound platform (Smartlead, Instantly, Outreach, Apollo), and an automation layer (n8n, Zapier, Make, or your own scripts)
Real experience shipping LLM-powered workflows — prompt design, structured outputs, evals or at least a rigorous eyeball process for quality control. You know where models are reliable and where they quietly aren't
Commercial instinct. You understand ICP, pipeline math, and why a 2% reply rate can be a great outcome or a terrible one depending on the deal size
Bias to ship. You'd rather have a rough system live on Tuesday than a perfect one designed by Friday

Nice to have

Built and scaled an outbound motion from zero at a startup
Warehouse-native GTM experience (dbt, Snowflake/BigQuery, Hightouch/Census)
Web scraping, data enrichment, or lead-gen tooling built from scratch
Founder or side-project background — you've sold something you built
Public work: a newsletter, an open-source workflow, a Clay table people ask you for

First 90 days

Day 30 — You've audited the current stack, killed at least one thing we're paying for that doesn't earn its cost, and shipped your first automation
Day 60 — One full outbound motion is running on infrastructure you built, with reporting we trust
Day 90 — You're proposing the roadmap rather than working from ours

Eubrics is an equal opportunity employer. We hire on demonstrated ability, not credentials — if you've built the systems but don't match every bullet above, apply anyway and show us the work

Eubrics AI

New Jobs

GTM engineer