Founding GTM Engineer

What You'll Work On

Vertical GTM Systems

• Source manufacturers, score accounts, identify buyer committees, understand the dealer/support/sales motion, and turn each vertical into a repeatable campaign.

Warm Lead Conversion

• Keep warm replies, intros, website leads, LinkedIn conversations, and customer referrals moving.
• Write the next email, define the next action, prep the demo, ask for the right docs, and make sure every promising account has an owner and a path forward.

Conference Machinery

• Build the before/during/after system for conferences: exhibitor lists, floor maps, target accounts, buyer committees, meeting routing, QR demos, founder prep, content capture, follow-up, and Attio tracking.

LinkedIn Signal Loops

• Turn posts, comments, reactions, event networks, founder content, and customer conversations into qualified lead pools, specific outreach, and useful CRM context.

Outbound Infrastructure

• Build and maintain scraping, enrichment, email/LinkedIn workflows, campaign folders, message rendering, reply reconciliation, deliverability hygiene, and CRM updates.

Customer-Specific Kits

• Create account briefs, product questions, demo hooks, objection notes, artifact ideas, follow-up assets, and deployment handoff notes that make every customer touch sharper.

Deployment Activation

• After demos, keep accounts moving toward usage. Make sure docs are requested, agents are tested, deployment specialists have context, blockers are visible, and customer feedback gets routed back into product.

Pipeline Truth

• Keep Attio, ProxGraph, campaign files, demo links, blockers, next actions, and customer context clean enough that the founders do not need to reconstruct reality from memory.

Growth Automation

• Use Codex, Claude Code, scripts, browser automation, APIs, CSV workflows, Clay/Apollo-style enrichment, and MCPs to make the second campaign faster than the first.

What We're Looking For

• Technical enough to build: you can work with APIs, scripts, CSVs, browser automation, agents, and messy data without waiting for an engineer.
• Commercial enough to care: you understand that the point is revenue, demos, trials, usage, and customer trust.
• Strong writer: you can write customer-specific outbound, follow-ups, LinkedIn hooks, account briefs, and internal notes that do not read like AI slop.
• Research obsessed: you can find non-obvious directories, associations, event lists, buyer committees, dealer networks, forums, support pain, and vertical-specific context.
• Operationally intense: you keep the CRM, campaign folders, next actions, and customer context clean even when everything is moving quickly.
• Customer-facing: you can join calls, ask good questions, listen for real pain, and help the founders move a conversation forward.
• High agency: if a warm account goes quiet, a campaign is blocked, a list is dirty, or a follow-up is missing, you do not wait for someone to assign the obvious next move.

Strong signals: growth engineering, founder experience, technical sales, forward-deployed engineering, customer implementation, RevOps, scraping, agent automation, conference-led outbound, or experience around manufacturers / complex products.

What Good Looks Like In 90 Days

• One repeatable vertical campaign from raw source list to qualified outreach to booked demos.
• One event engine for an OEM-heavy conference: accounts, buyers, demo links, content plan, follow-up loop, and Attio tracking.
• One high-signal LinkedIn or event network converted into a qualified lead pool and outbound sequence.
• Warm accounts have deployment briefs, docs asks, demo test plans, next actions, blocker lists, and assigned specialists.
• At least three repetitive GTM workflows are automated or made dramatically faster.
• Founder memory load decreases because pipeline state and customer asks are visible in the system.