What are the responsibilities and job description for the GTM Engineer position at Fractional Demand?
At Fractional Demand, we embed senior GTM engineers directly into B2B revenue teams. We don’t advise. We build. Our team thinks like marketers and builds like engineers, and that combination is exactly what our clients pay for.
We’re hiring a GTM Engineer to own the hands-on execution side of our client engagements. You’ll be the person who turns a whiteboard conversation about pipeline problems into a live system by Friday.
You’ll be embedded across 5-7 clients at a time, running the full build cycle from audit to automation to optimization. On any given week, that means:
- Building Clay tables from scratch: ICP scoring, multi-source enrichment, signal stacking (job changes, funding rounds, tech stack, website visits)
- Writing AI prompts inside Clay that produce actionable sales research, not just data
- Connecting Clay to HubSpot, Slack, and outbound tools with clean, reliable field mapping
- Custom audience scraping for hard-to-reach personas
- Designing and implementing lifecycle stages, lead routing rules, and pipeline workflows
- Building full-funnel dashboards: SDR/AE views, channel performance, exec-level reporting
- Running data hygiene and deduplication workflows
- Lead-to-account matching and territory assignment automation
- Building signal-triggered outbound plays: intent stacking, LinkedIn engagement, competitor displacement
- Connecting tools via n8n, Zapier, or webhooks into end-to-end automated workflows
- Automating pre-meeting research briefs, Slack alerts, and SLA handoff tracking
- Building and deploying Clay to HubSpot to Slack automation chains
- Using Claude Code or similar LLMs for enrichment, intent scoring, and research automation, etc.
- Building structured prompt pipelines that output clean, CRM-ready data
- Integrating Apify actors and web scraping pipelines where neede
- Have 5 years working in GTM Engineering, RevOps, or Sales Engineering inside a B2B environment
- Know Clay deeply: not just the basics, but API’s, webhooks, lead routing, etc.
- Can own a HubSpot instance end to end: properties, workflows, pipelines, reports, and integrations
- Think in systems. When a client says “our outbound is broken,” you’re already mapping the data flow in your head
- Can operate independently across 2–3 client accounts without losing the thread
- Communicate clearly with non-technical stakeholders. You can explain a Clay workflow to a VP of Sales without making their eyes glaze over
Clay · HubSpot · Apify · Supabase · Slack · LinkedIn Sales Nav · Apollo · Outreach · Claude Code · Google Sheets · Webhooks · API’s
No fluff. Clients aren’t paying for strategy decks. They’re paying for systems that run. You’ll see your work live fast.
Variety by design. Because we’re fractional, you’ll touch various GTM stacks. You’ll get better faster than in any in-house role.
Month-to-month client relationships mean we have to earn trust every month, which keeps the work sharp and the bar high.
Send us a short note (not a form letter) and one example of a GTM system you built: a Clay workflow, HubSpot architecture,a vibe coded solution, whatever you’re proud of. We care more about how you think than your resume format.