GTM Engineer
Indexed description
- Full-Time
- Remote
Share:
- Job Openings
- GTM Engineer
- GTM Engineer
FinancialReports is building the global public equity data layer for the AI era — 48,000 public companies, 30 million filings, one structured, AI-ready feed. Hedge funds, asset managers, data vendors, and AI labs use our API to build the models that move capital.
We are small, profitable, and moving fast. Every SDR we do not hire is an SDR we automate. We need someone who can build the machine.
The Role
You are the one-person GTM engineering team. Sales, marketing, ops — all of it runs on systems you build. Your job is to make one SDR output like five, one AE close like three, and one founder see the whole funnel without asking anyone for a report.
You will build the outbound engine, the enrichment stack, the signal pipeline, the internal tools, and the reporting layer. You will ship in days, not quarters. You will kill what does not work and double down on what does.
You will work with everyone — SDRs, AEs, marketing, engineering, the founders. No ops manager above you. No tickets to file. You see a problem, you fix it.
What You Will Do
- Build and run outbound infrastructure in Clay — enrichment waterfalls, intent signals, sequencing, deliverability
- Engineer signal pipelines — API signups, MCP usage, GitHub stars, funding rounds, hiring signals — into qualified outreach
- Own HubSpot end-to-end — pipeline, automation, attribution, reporting, hygiene
- Write internal tools in Python, TypeScript, whatever fits — scrapers, dashboards, agents, bots
- Stand up reporting that tells us what is working, in real time, without anyone asking
- Partner with marketing on landing pages, conversion, and experimentation
- Partner with engineering on product signals — usage, activation, expansion triggers
- You ship. You have built systems that other people used and that made money. Not slides, not proposals — actual systems in production
- You are Clay-native or Clay-ready. Waterfalls, HTTP columns, webhooks, Claygent. Or you can learn it in a weekend.
- You can code. Python or TypeScript level where you can write an API integration, spin up a Next.js page, or script against OpenAI/Anthropic without help
- You also know when not to code. If Zapier or n8n solves it in an hour, you use Zapier or n8n
- You understand sales. You do not need to carry a bag, but you need to know what a well-run sequence looks like, why MEDDIC matters, and what breaks pipeline at the handoff
- You are obsessed with leverage. Your instinct is to build the thing that makes the next ten things easier
- You write well. You will document what you build so the team can use it without you
- Your stack preference. Use what ships fastest.
- Whether you call yourself a "RevOps" person, a "growth engineer," a "GTM engineer," or a "founding ops hire." Titles do not build pipeline.
- Where you live. Work from anywhere.
Process
- Short written application — tell us the best GTM system you ever built, what it did, and what it produced
- 30 min Interview
- Work sample — you take a real GTM problem we have and show us how you would build it (paid)
- Final Interview
- Offer
Apply now Refer
Share:
- Job Openings
- GTM Engineer
- GTM Engineer
Create a free Caio profile to unlock more results and save your role and location preferences.
Unlock free search