GTM Engineer
- Compensation
- $150K–$200K / yr
- Location
- NYC & Palo Alto
- Work setup
- Hybrid
- Seniority
- Not specified
- Employment
- Not specified
- Experience
- Not specified
- Category
- Sales
- Posted
Skills
Must have
- You've shipped a revenue system that ran in production and moved a number you can name. Clay, n8n, Python, TypeScript, SQL, or plain APIs — the tool matters less than the outcome.
- You're fluent in SQL against a warehouse — and you know why a metric definition has to be agreed before it's automated.
- You've lived inside a GTM org — RevOps, growth, sales engineering, or as a founder doing all three. You understand how a rep, a marketer, and a CS manager actually spend their day.
- You build with AI agents daily — not just drafting with them. You can explain where they fail and how you catch it.
- You write specs people can build from — a one-pager a stakeholder signs off on and a teammate can execute without a meeting.
- You have high agency — you identify the gap and go after it. You don't need a ticket to fix something broken.
Nice to have
- Agent orchestration and evals experience (queues, cron, Temporal, or similar).
- Prior work on paid acquisition loops — creative generation, bid management, kill/promote logic.
- Deep HubSpot fluency (APIs and data model).
Full description
About the Role
This is our founding GTM Engineer. Nothing is inherited: no legacy stack, no old playbook, no "that's how we've always done it." You get first pick of what to build, and you own the results.
The job is to build the revenue machine as software: a clean data spine, an action layer that writes safely into our CRM, ad accounts, and email, and a fleet of narrow agents that each own one motion and one number. You are not a RevOps analyst who produces dashboards and waits for someone else to implement. You are a strategist who codes.
And there's a twist most companies can't offer: every agent we run internally becomes a reference architecture we show customers. Your work won't sit in an ops backlog — it'll be on stage in sales conversations.
This role reports to the Head of GTM Engineering — flat org, no layers between you and the decision-maker.
What You'll Do
- Build and own two to four GTM agents end to end — the loop, the evals, the guardrails, and the metric each one moves. First candidates: speed-to-lead routing, call prep, CRM hygiene from transcripts, and PQL detection from product usage.
- Stand up the data spine — pipelines from CRM, product usage, billing, ads, and web analytics into a warehouse, with agreed definitions of CAC, pipeline, ICP fit, and PQL before any agent touches them.
- Earn automation, don't assume it — every agent ships in propose mode with a named human approver, and graduates to auto mode only when its acceptance rate earns it.
- Instrument everything — every agent decision logged with the data snapshot behind it, a cost-per-outcome number per agent, and a scorecard leadership can read in one screen.
- Fix the funnel we have — lead scoring and routing, the enrichment waterfall, de-anonymizing traffic, and the handoff from self-serve to sales-assisted.
- Turn internal wins into external assets — demos, write-ups, and talk tracks the sales and SE teams use with customers.
Who You Are
- You've shipped a revenue system that ran in production and moved a number you can name. Clay, n8n, Python, TypeScript, SQL, or plain APIs — the tool matters less than the outcome.
- You're fluent in SQL against a warehouse — and you know why a metric definition has to be agreed before it's automated.
- You've lived inside a GTM org — RevOps, growth, sales engineering, or as a founder doing all three. You understand how a rep, a marketer, and a CS manager actually spend their day.