Founding GTM Engineer
- Compensation
- Not disclosed
- Location
- New York, NY
- Work setup
- Hybrid
- Seniority
- Not specified
- Employment
- Not specified
- Experience
- Not specified
- Category
- Sales
- Posted
Skills
Must have
- You think in revenue, not features. You look at a funnel and know which fix is worth the most.
- You ship in days, not quarters. A week spent planning instead of building feels like a loss. You'd rather put something live and learn than wait on the perfect spec.
- You grow as the tools grow. What was prompts and personas last year is Claude Code and full apps now; you reinvent your workflow the moment something better lands.
- You'd rather rebuild a tangled CRM than inherit a clean one. You've built inside real Salesforce and HubSpot, and the mess is the fun part.
- You get things done through people. You co-drive with the sales and marketing leaders and earn the trust to change how they work.
Full description
The Opportunity
You build the systems that run Hearth's go-to-market: the whole engine, one motion at a time. You're a business builder, not an engineer who needs a brief. You find the lever that moves the number and ship the system that pulls it, fast: a sales lead flags a broken handoff on Monday, the fix is live on the floor by Wednesday.
Hearth is the AI growth system for local home-improvement contractors. Over 50% of these businesses go under without software like Hearth, and when you ship a system that works, a roofer stops losing 40% of his inbound calls and gets home for dinner. The loop between your work and someone's livelihood is short.
You're the first hire on our GTM engineering function, and the timing is the point: we're launching new products, and each one needs its own go-to-market built around it: the routing, the outreach, the tooling, the measurement. You co-own clear success metrics, like revenue and headcount, with the Director and VP peers in Sales and Marketing: they run the floors, you build the systems that move the numbers, and the metrics are shared. You won't be handed a clean slate, and you won't be asked to just tune what's there. You'll rebuild the baseline and define what a true AI-native go-to-market looks like.
This is the founding seat on the function, with a leader's runway. Prove the model on one motion, then hire under you as each number earns it.
What You'll Build:
You move the numbers, and you build whatever moves them. Sometimes that's a routing change, sometimes a new scoring layer, sometimes an AI agent that takes a rep's busywork. The thread through all of it: you decide where the leverage is, then build it.
We've started on inbound conversion (routing and next-best-action on our existing lead-scoring model), but it needs scale and a real rethink. From there the surface is wide: the outbound motion, marketing automation and testing, the measurement model that points spend at what actually converts, and the repfacing AI that handles research and follow-up so reps sell. Underneath it is one backbone, the data and integrations that connect our CRM, enrichment, and scoring, so the motions run on one system instead of four bolted together. We already run AI in production today (lead scoring, Clay workflows); your job is to push it deeper across every motion.
What You've Done:
The first two decide it.
- You moved a number and knew why. You decided which lever mattered, built the thing that moved it, and can quote the result: not "improved conversion" but "this segment went from X% to Y% over Z weeks, and here's how I measured it." Extra credit for a time you decided not to build something, and were right.
- The bar isn't deep engineering. It's that you ship, yourself. You live in Claude Code (or whatever's best) and build with AI doing the heavy lifting: an integration, a workflow, an agent that did a real job your team depended on. Python and SQL where they help. Show what you shipped; commentary and slides don't count.