Go-to-Market Engineer

atqleads•Montreal, QC

6d•Remote

About The Position

ATQLeads builds GTM systems for B2B companies that are done waiting on agencies and tired of the cost of full-time hires. We sit between the two: a network of vetted GTM operators who embed directly inside client teams — inside their tools, their Slack, their stack — and deliver against outcomes, not hours. We don't sell retainers. We deploy capacity. Operators are part of the company. If you want to own real work, operate inside real companies, and be compensated like a partner rather than a contractor, this is where you belong. The GTM Engineer is the engine builder at the core of every ATQ Squad engagement. Strategy without a GTME stays theoretical. Campaigns stay manual. Data stays fragmented. Pipeline stays unpredictable. The GTME is the person who turns direction into operational machinery and then keeps that machinery running. You won't be assigned tickets. You'll be given a GTM problem, a client stack, and a capacity commitment. Your job is to build the system that solves it, own its reliability, and push it forward without being asked.

Requirements

Clay (required) — multi-source tables, waterfall enrichment, formula columns, Claygent prompts
Make or n8n — multi-step scenarios with error handling, retries, webhooks
Python, JavaScript, or SQL (at least one) — including pandas for cleaning, deduplicating, and transforming CSV/Excel data
APIs, webhooks, and structured data — used as the default approach, including when native integrations exist
LLM API integration (Claygent, OpenAI, Anthropic) into production workflows, with prompts that produce consistent and accurate output
CRM configuration (HubSpot, Zoho, or Salesforce) — workflows, custom objects, lead routing, lead scoring, bidirectional sync
Debugging fast and using AI as a co-pilot, not a crutch
Learn new tools on your own. Figure things out before asking.
Think in outcomes, not tasks.
Know what a qualified lead costs, why conversion rates matter, and how your work connects to a number.
Describe your work in outcome terms ("produced X meetings via Y% conversion"), not activity terms ("sent X emails").
Explain a multi-step workflow in 60 seconds.
Communicate in plain language to people who care about results, not your stack.
When a technical decision is challenged, revise it or add reasoning — don't restate the original answer.
Acknowledge gaps in your knowledge and propose how to resolve them.
Manage your own priorities without being managed.
Spot a broken funnel before anyone tells you.
Improve a process before you automate it.
Treat client systems like your own, with urgency, ownership, and judgment.
Track record: at least one shipped system still running at a previous engagement after you left.
Fluent in English.
Apify or equivalent web scraping (BeautifulSoup, Playwright) when standard enrichment fails.
Zapier, Retool.
Deliverability ops: domain warmup, sender rotation, content variation, blacklist monitoring.
Composite scoring across firmographic, technographic, hiring, funding, intent, behavioral signals.
Failure-mode planning: enrichment fallback, deduplication, sync failures, deliverability blacklist.
pandas for CSV/Excel cleaning and transformation.
Async-first work in Slack, Notion, Linear.
Deliver a working artifact within 72 hours of an unstructured brief.
Ship documentation with every build (handoff doc, README, Loom).
Communicate directly with clients — no PM intermediary.
Manage your own priorities and blockers.
Report upstream data and strategy quality issues, don't work around them.

Nice To Haves

Make (preferred) or n8n
Zapier, Retool, Apify, and equivalent web scraping tools (BeautifulSoup, Playwright) when standard enrichment sources do not return the required data
LLM API integration (Claygent, OpenAI, Anthropic) into production workflows

Responsibilities

Own four interconnected systems end-to-end: Outbound, Inbound and Pipeline Generation Engine; Data and Enrichment System; Automation and Workflow Layer; Conversion Infrastructure.
Build the initial outbound and data infrastructure, translate the GTM Strategist's ICP into Clay filter logic, configure CRM workflows, and establish the reporting layer.
Define and instrument the metrics needed to evaluate system performance before launch.
Launch and manage campaigns, enrich and refresh lead lists, monitor deliverability, handle replies, and maintain CRM accuracy.
Calculate conversion rates at each funnel step (open, reply, positive reply, meeting set, show).
A/B test messaging, targeting logic, and conversion paths.
Prioritize improvements at the funnel step with the largest gap between current performance and benchmark.
Expand into new segments and channels once the existing system delivers consistently.
Reduce manual steps systematically by automating any step still requiring human action.
Refine ICP using actual response and conversion data.
Manage upstream dependencies actively: report data quality issues, flag missing Strategist inputs, and request clarification when a brief lacks the inputs needed for accurate delivery.
Communicate directly with clients without a project manager intermediary.
Generate your own ideas and diagnose bottlenecks early.
Prioritize by revenue impact and build experiments that compound.
Build systems that continue functioning after you leave the engagement, with no required maintenance from the original builder.
Deliver a working artifact within 72 hours of an unstructured brief.
Ship documentation with every deliverable — handoff docs, READMEs, Loom walkthroughs are part of the build, not an afterthought.
Plan for failure modes (enrichment fallback, deduplication, sync failures, deliverability blacklist) before they break the system.