GTM Engineer

Baseten's GTM org is in hyper growth. As it grows and matures, the needs of the GTM stack get more sophisticated with scale — and this team exists to stay ahead of those needs. Our GTM Engineering team plays a critical role in building and maintaining the connective tissue across Baseten’s GTM tools, processes, and user experience for the field.

The GTM tooling landscape is changing fast, and the teams that win are the ones that adapt and iterate the fastest. This role exists to make sure Baseten is one of them.

You'll design, build, and ship AI-powered workflows that scale our GTM functions as a competitive advantage. We want someone who can walk in, audit what we have, identify what we're missing, and start shipping fast.

You know when to reach for Clay and when to build something custom in Claude Code. You think two to three steps ahead about how the thing you build today fits into the broader systems architecture tomorrow. And you bring a point of view — on our stack, on what we should be building, and on where AI can do something low-code tooling simply can't.

* Ship AI-powered workflows for the field — build the agents and automations that give reps and managers real leverage, off-loading the manual and repetitive work. Reach for AI where it does something low-code can't.

* Get insights in front of reps — turn Salesforce, warehouse, and usage data into the dashboards, scores, and alerts reps actually act on. A build isn't done until the field is using it.

* Audit the stack and generate your own backlog — we have a lot of tools, some overlap, and real gaps. Walk in with a point of view, identify what's missing or broken, and prioritize without waiting to be handed a roadmap.

* Ship rep-productivity workflows fast — triage asks from the field, find the low-hanging fruit, and build it. A good week looks like a VP of Sales asking for something Monday and having it live by Wednesday.

* Know when to go custom — not everything belongs in a point-and-click tool. Spin up bespoke AI-powered solutions in Claude Code when the problem calls for it, and make that call with judgment, not default.

* Think in systems, not solutions — every workflow you build has upstream and downstream implications. Anticipate them, design for them, and don't create technical debt that someone else has to unwind six months later.