What we're building

Mutiny is the self-improving AI infrastructure for GTM teams to execute faster and close more revenue. Our ambition is to do for revenue velocity what Cursor and Claude Code did for engineering velocity. With Mutiny, everyone in sales and marketing gets a bench of GTM athletes that handle any work across their revenue motion and learn from what's actually moved their deals.

In April we re-launched the product as an agent-first platform. Anthropic showcased us as a leader in AI GTM. MRR is growing more than 70% month-over-month, with customers like Uber, Rippling, and Snowflake. We're backed by Sequoia, YC, and Insight, and we're building a generational company.

The opportunity

Most GTM engineers wire up someone else's stack. You'll build a new one. As Mutiny's GTM engineer, you'll own the systems that power how we go to market, from outbound and onboarding to enrichment, routing, and the AI-native workflows that let a small team operate like a much bigger one. You'll define what GTM engineering looks like at an AI-native company from the ground up. This role is in person in New York City, five days a week.

What you'll own

• The GTM stack. The systems behind outbound, onboarding, enrichment, routing, and segmentation. If a workflow is slow or a number is wrong, you fix it at the source.

• Automations and internal tools. Build the workflows and tools that make sales and marketing faster. The tool you ship today saves the team a week next month.

• The plumbing. APIs, data flows, integrations between every tool we run on. You make systems talk so the team doesn't have to.

• AI inside the walls. Bring agents and AI workflows into how we operate, not just what we ship. The way we run becomes the playbook for how customers should run.

• Pattern to playbook. Take what's working in one motion and turn it into something repeatable. The automations and tools you build become the foundation the next ten teammates inherit.

Who you are

• A systems thinker. You see one-off work and want to make it repeatable. You spot patterns and bottlenecks before they become someone's full-time problem.

• A builder. You've shipped automations, internal tools, and workflows that made a team measurably faster. You'd rather build than brief.

• Comfortable with plumbing. APIs, data flows, enrichment, routing. You know how to connect systems and make them work, even when the docs are wrong.

• AI-curious, AI-fluent. You're already experimenting with agents and AI workflows in your own work. You know which abstractions hold up and which are demo-ware.

• Bias to ship. You'd rather ship something at 80% this week and improve it next than wait for the perfect spec. There's no playbook for this role and you'll write a lot of it.

• A cross-functional translator. You can explain what you're building and why it matters to a CMO, a CRO, and an engineer in the same week. None of them feel talked down to.