Founding GTM Engineer

tl;dr

⊹ You will turn Prox's GTM motion into an engineered system: find the right manufacturers, identify buyer committees, build high-context outbound, and convert warm customer signal into demos, trials, and deployed accounts.

⊹ This is not a classic marketer, AE, or RevOps-only role. You need to be technical enough to build systems, commercial enough to care about revenue, and operational enough to keep the pipeline clean without being reminded.

⊹ You will work directly with the founders across vertical research, LinkedIn signal, conference machinery, outbound infrastructure, Attio/CRM hygiene, customer briefs, demo follow-up, and deployment activation.

⊹ You should be very comfortable using agents like Claude Code and Codex, scraping and enrichment tools, spreadsheets, APIs, browser automation, and messy customer context.

⊹ Based in San Francisco. In person.

What We're Doing

Prox is building the AI product specialist for manufacturers.

Manufacturers use Prox as a technical support and product sales tool across the surfaces where their customers and teams already work: dealer tablets, service-desk computers, sales laptops, websites, internal tools, support workflows, and agent/MCP-style connectors.

A dealer, customer, support rep, or salesperson can ask Prox which product fits a use case, how to configure it, what parts are compatible, how to troubleshoot an issue, how to install or service it, or how to produce the right quote or setup guide.

The goal is simple: every manufacturer should be able to make their best product specialist available everywhere, instantly.

Why This Role Exists

Prox has cold leads, warm leads, customer conversations, founder networks, event opportunities, LinkedIn signal, and live deployments starting to move. The bottleneck is turning all of that signal into a repeatable machine.

More lead volume alone is not enough. We need the right accounts, the right buyer, the right wedge, the right demo angle, the right follow-up, and the right next action after every customer touch.

The founding GTM engineer owns that system.

You will help us find high-fit manufacturers, understand why they should care, reach them with context, book the meeting, prepare the founders, keep the CRM true, and make sure warm accounts do not drift after the demo. When a lead turns into a trial, you help push it into activation: docs collected, demo tested, blockers surfaced, feedback routed, and next steps clear.

This role sits between growth, sales, product, and deployment. It is a founder-level leverage role for someone who wants to build the distribution engine, not just operate inside one.

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 to do everything for you

⊹ 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

The Application Process

Step 1: Application. Send us evidence of work: systems, campaigns, scripts, writing, founder/customer work, or anything that shows how you think.

Step 2: Founder call. We will talk through your work, your taste, your intensity, and how you think about GTM.

Step 3: GTM systems challenge. We will give you a real vertical or customer signal and ask you to build the account list, buyer map, outreach angle, demo prep, next-action system, and follow-up plan.

Step 4: Work trial. You come to SF and work with us for a few days. The expectation is to move real pipeline or build a real GTM system.

Step 5: Offer.

--Dima & Greg