GTM Engineer

Strattmont; India; On-site; INR 8,646,000 - 12,488,000; Full time

Job summary

Strattmont is seeking a GTM Engineer to build the full outbound engine from the ground up. You will stand up signal sourcing, enrichment, and sequencing across our outreach stack, including Apollo/HubSpot/Gmail integrations.

You will design personalized, trigger-driven outreach and establish tracking to measure reply and meeting rates. This role requires hands-on work with APIs, data wrangling, and pipeline optimization.

Qualifications

• Built lead-gen or enrichment pipelines in Clay, n8n, Make or similar tools.
• Comfort with APIs, webhooks and basic Python/SQL for data wrangling.
• Understanding outbound sales mechanics and signal-driven outreach.

Responsibilities

• Design and build signal-based lead pipelines using Clay, n8n/Make and APIs.
• Create enrichment workflows turning raw contacts into contextualized prospects.
• Write first-line personalization logic for outbound messaging.
• Set up tracking to measure reply rates by trigger type and source.
• Continuously test and optimize signal sources for conversions.

Skills

Lead-gen pipelines

APIs

Python

SQL

Tools

Clay

n8n

Make

Apollo.io

HubSpot

Gmail

Aimfox

Sendpilot

Reachinbox

Job description

GTM Engineer - Strattmont

Location: Remote

Engagement: Full-time

Reports to: Founder

About Strattmont

Strattmont is a recruitment and executive search firm. We run 5-day shortlists, a 90-day replacement guarantee, and a 97% 12-month retention rate across our placements. We're looking for someone to build the outbound engine that gets the right prospects in front of us at the right moment — not another person sending more generic emails.

The Problem You're Solving

We have the outreach tools in place (Apollo.io, HubSpot, Gmail, Aimfox, Sendpilot, Reachinbox) — but need someone to build the full outbound engine properly from the ground up. This isn't a light optimization job; it's a build job. We need someone to stand up the full pipeline: signal sourcing (a company posting multiple open roles in our placement verticals, a funding round, a senior exec departure, a competitor's key hire), enrichment, and the sequences themselves — and get it actually running, not just designed.

What You'll Own

• Design and build signal-based lead pipelines using Clay (or equivalent), n8n/Make, and relevant APIs — job-posting data, funding/news triggers, LinkedIn job-change/hiring-intent signals




• Build enrichment workflows that turn a raw contact into a fully contextualized prospect: company, role gap, trigger event, and a usable personalization hook — feeding directly into our existing Apollo/HubSpot/Sendpilot/Reachinbox/Aimfox stack




• Write or heavily inform the first-line personalization logic (AI-assisted or rule-based) so outreach references the actual trigger, not a generic template variable




• Set up tracking so we can see reply rate and positive-reply rate by trigger type and list source — not just opens/sends




• Continuously test and kill underperforming signal sources; double down on what converts

You're a Fit If

• You've built lead-gen or enrichment pipelines in Clay, n8n, Make, or similar — not just used off-the-shelf list tools




• You're comfortable with APIs, webhooks, and basic Python or SQL for data wrangling




• You understand outbound sales/BD mechanics well enough to know why a signal matters, not just how to pull it




• You can write — or work closely with someone who writes — a first line that doesn't sound like a mail-merge




• Bonus: experience in recruitment, staffing, or another relationship-driven B2B service business, where the \"signal\" isn't just firmographic data but timing and pain

Tools & Budget

We currently run Apollo.io, HubSpot, Gmail, Aimfox, Sendpilot, and Reachinbox — but we're not limiting you to this stack. If Clay, a paid intent-data source, or another platform will meaningfully move the signal-to-meeting pipeline forward, make the case and we'll get it.

What Success Looks Like

By Day 30

• Signal sourcing and enrichment pipeline live (at least one trigger type fully wired end-to-end, from signal to a contextualized contact loaded into our outreach tools)




• At least one campaign actively sending against that pipeline




• First qualified meetings booked and on the calendar — this is the bar, not \"campaign is ready to launch\"

By Day 60

• 2-3 trigger types running in parallel, with underperforming ones already cut




• A steady, predictable weekly rate of qualified meetings booked, not one-off spikes




• Reply rate and meeting-booked rate tracked and broken out by trigger type and list source, so we know which signals to double down on

By Day 90

• The pipeline runs with minimal manual intervention from us — new trigger types can be added without rebuilding the system each time




• A clear, repeatable playbook documented well enough that a future SDR or second hire could execute against it




• Enough volume and consistency in booked meetings that we're deciding where to scale, not whether the engine works

What \"qualified\" means: a meeting with someone who has real, current hiring need we can place against — not just a booked call that shows up on the calendar. Volume without qualification doesn't count toward this metric.