About the company
Aviator builds the AI developer workflow automation that lets large engineering teams ship AI-generated code safely and fast. It run inside the CI/CD pipelines of teams at Meta, Slack, Square, Figma, DoorDash, and Notion.
Our thesis: AI made code easier to write, not easier to ship. As AI floods engineering orgs with more PRs than humans can review, the bottleneck moves downstream — to review, verification, and merge. That's the layer we own, with a "proof, not judgment" approach to deterministic, pre-merge verification.
We're a small, senior team (YC S21) selling to some of the most technical buyers on earth. Which is exactly why this role exists.
About the role
Our buyers are staff engineers, platform leads, and DevEx teams. They ignore generic cold email, they can smell a template from a mile away, and they respect people who actually understand their problems. Winning them takes GTM that's as technical as the product.
That's the job. You'll write code to drive revenue — building the enrichment, research, and outbound systems that put the right message in front of the right engineering leader at the right moment. You're not an SDR with a sequencer; you're an engineer who happens to build pipeline using AI.
This is a build role with real ownership from day one. If it works, it converts to full-time.
What you’ll do
Build enrichment pipelines in Clay (or code) that identify companies with the signals that matter to us — large monorepos, high PR throughput, heavy CI spend, GitHub-native workflows, recent DevEx or platform hires.
Design signal-based outbound that references a prospect's actual engineering context, not a merged-tag {{first_name}}. Personalization at scale, driven by real research.
Ship AI agents and automations (using the Claude API and tools like n8n/Zapier) that scrape technical blogs, changelogs, conference talks, and hiring pages to build account intelligence ahead of every conversation.
Wire the GTM stack together — CRM, sequencer, enrichment sources, and product usage data — into workflows that surface next-best actions and keep data clean.
Instrument the funnel. Build the dashboards and reporting that tell us which plays generate pipeline and which don't, and kill the ones that don't.
Support the founder-led sales motion with account research, competitive teardowns, and the technical prep that makes each Verify conversation land.
What you’ll work with
Python and/or TypeScript · SQL · REST APIs · Clay · Claude API · a CRM (HubSpot/Salesforce) · a sequencer (Instantly/Smartlead/Outreach) · data sources (Apollo, ZoomInfo, GitHub) · automation glue (n8n, Zapier) · Playwright/Puppeteer for scraping. You won't have used all of these — we don't expect you to. We expect you to learn them fast.
Who you are
You can write code. College projects, side projects, freelance, or a repo you're proud of all count — you're comfortable with APIs, scripts, and data.
You're genuinely curious about how B2B companies grow, not just how software gets built.
You ship daily, measure everything, and don't wait for permission.
You can look at an engineering org and reason about whether they'd care about faster, safer merges — and articulate why.
You're comfortable with ambiguity and a small team where your work is visible immediately.
Nice to have
You've touched Clay, Apollo, a CRM, or built an automation before.
You've used AI coding tools (Claude Code, Cursor) to move faster.
You have a point of view on developer tooling, code review, or CI/CD — maybe you've felt these pains yourself.
You've done cold outreach, ran a newsletter, grew a community, or built an audience.
What you get
Real ownership of systems that directly drive revenue, with your impact measurable in pipeline.
Direct mentorship from the founder and access to the full GTM stack — the tooling most startups pay consultants $20K/month to set up.
A front-row seat to enterprise GTM against a technical, sophisticated buyer.
A clear path to a full-time GTM Engineer role if you're driving results.
How to apply
Send us:
A link to something you've built — a repo, an automation, a Clay workflow, a piece of outreach, anything.
One paragraph: which GTM system you'd build for Aviator first, and why.
