GTM Engineer

We're looking for our first GTM Engineer to help us engage at just the right moment without being annoying about it.

You'll design, build, and ship the workflows and data infrastructure that turn product and market signal into pipeline, plus the internal apps and tools that compound our output. You'll walk in, audit what we have, decide what's missing, and start shipping.

Our users are developers, which makes this harder and more interesting than GTM engineering at most companies. Developers have antibodies against generic outbound, and the most valuable signal lives in product usage, not a lead form. We are deeply allergic to slop: the last thing the world needs is another ill-conceived cold email, and we won't ship one.

Anything we send should be something a thoughtful person would be glad to receive. We're not anti-AI by any means (helps us stay lean and move fast), and you'll be the person who keeps us on the right side of the line. The plays that work here are technical, specific, and earned, which is why we think the best version of this role is held by someone technical enough to build on Convex themselves.

- Turn Convex product usage into the GTM signal it should be: model which deploys are getting serious, surface intent the moment a team crosses a threshold, and route it to the right play or the right human automatically.

- Build agent + human-in-the-loop outbound that's genuinely useful, and keep it from ever becoming slop.

- Build the AI agents and internal tools that compound the commercial team's output as we grow.

- Audit the stack, generate your own backlog, and know when to reach for a point-and-click tool versus building something custom. Do the unglamorous data cleanup that makes all of it trustworthy.

- Write a bunch of cool GTM code on Convex itself. We dogfood.

- Measure your results and double down on what works best.

- A few years spent building revenue and automation systems, whether you got there through Revenue Operations, Sales Ops, growth engineering, or as a software engineer who drifted toward the commercial side. You don't need "GTM Engineer" on your resume; the title barely existed a year ago, and we care far more about what you've built than what it was called.

- Technical enough to build and wire systems together yourself. You don't have to be a career software engineer, but you're comfortable with APIs, data, and a bit of code (SQL, a scripting language, or TypeScript, which is what Convex itself is built in).

- Hands-on experience inside a modern GTM stack.

- Hands-on with AI in real work, not just in theory. You know where models are reliable and where they break, and you're not afraid to fire up Claude Code or Codex to stand things up yourself rather than waiting on someone else.

- Systems thinking: you consider what happens at 10x volume, when an API goes down, or when the same account hits your queue five times in parallel, and you design for it instead of leaving debt for someone else to unwind.

- Bonus points for exposure to technical or developer-led sales motions, or genuine curiosity about Convex itself (building something small on it before you start wouldn't go unnoticed).

- Interest in working in-person at Convex's office in SF.

This is an attempt to outline some characteristics of candidates who tend to thrive at Convex. We have a high demand for both commercial judgment and the ability to actually build, while also having the typical demands of a small startup.

Do they think in systems, not tasks?

The job is not to do GTM work faster by hand. It's to build the machine that does it. We want someone who, handed a recurring manual process, instinctively reaches for the version that runs itself.

Someone who has built things that kept working after they walked away, and who measures their impact in leverage created, not hours logged.

Can they earn a developer's trust?

Developer tools are different. Your users are technical, skeptical, and quick to spot inauthenticity. The plays that work for a business app fall flat here.

We want someone who understands, in their bones, what it feels like to be a developer evaluating a product, and who builds GTM motions that respect that instead of spamming through it.

Are they a commercially oriented builder?

The best GTM engineers we've met are hybrids: they care about revenue and they can ship. Not a marketer who can't build, not an engineer who doesn't care whether the work moves the business. We want someone who lives in the middle and is genuinely good at both.

Do they value simplicity and pragmatism?

Simplicity is at the heart of all good systems, and GTM systems are no different. Don't come here to build a Rube Goldberg machine of fifty chained automations. Come here because you want to get really good at achieving great things in the simplest possible way

Do they bring energy to the room?

Startups are hard. Building something from nothing is hard. Driving forward progress despite uncertainty is hard.

Shitting on stuff is easy and just brings everyone else down. We have a high bar for quality but also a high bar for being constructive, positive, and excited about making things better. We're meant to be having fun here.