Good Morning.
Ramp engineer Sandra Yang gave coding agent Devin a company card, named it BugBasher, and told it to make money. Four weeks later: about $3,000 spent, $75 earned, and thousands of calls. She called it the first public cold-start B2B sales case for an agent. The agent was great at chasing a concrete goal. It was useless when the destination was vague. Peak 2026.
Now, let's get into today's Circuit. 🫡
The feed this week. CRO eyes Applied AI Engineer.
In this Circuit:
🛠️ Operator Tip of the Week
📖 Anthropic's GTM Claudification hire
🗳️ Poll: what is your next GTM hire actually for?
📡 Across The Wire
🧪 What I'm testing + rating
🛠️ Operator Tip of the Week
Before you ask anyone to "build an agent for outbound," write the human layer first. Approval gate. Handoff. Escalation. Who owns the miss when the agent is wrong. Put those three lines in a doc. Then scope the agent. Most GTM agent projects fail the boring way: great demo, no owner when it hits a real CRM record.
📖 Anthropic is hiring engineers to run GTM
Everybody in GTM Slack is circulating the same Anthropic posting this week. The live Greenhouse title is Staff Software Engineer, GTM AI Engineering. Same URL still gets shared as AI Engineer, GTM Claudification. Comp band on the page: $320,000-$405,000.
Read the responsibilities: a staff software role whose product is Anthropic's own go-to-market.
Core of the JD:
- Build autonomous agents for inbound, outbound, pipeline, customer engagement
- Design human oversight: approval gates, handoffs, escalations
- Ship eval frameworks in dev and production
- Tie agent actions to pipeline and revenue with observability
- Ship MCP servers, agent skills, CRM/comms/warehouse apps
Preferred profile: 8+ years SWE / ML / FDE. Python or TypeScript. Production LLMs, agents, MCP, evals. Claude Code / Agent SDK. Real GTM systems experience. Former technical founders encouraged.
The market conversation sounds like Applied AI is eating classic GTM Engineer. Anthropic's actual title is Staff SWE / AI Engineer on a GTM Claudification team. They are hiring engineers to run GTM, not classic GTM engineers with a new label. The seat is engineering, the scoreboard is pipeline.
Adam Schoenfeld's take: agent builder with revenue goals, real engineering inside GTM, heavy human enablement. Same pattern at Gusto, Customer.io, Vanta.
My take: this is not necessarily how the whole GTM engineering space moves next. If you are a major company with budget for a ~$500k hire to build these systems in-house, why not. If you mostly need someone semi-technical who can connect the tools and ship ops glue, you will probably still land on a GTM engineer. Different companies, different jobs.
Either way: pick one motion. Write the approval gate. Write the escalation. Only then ask what an agent should draft or do.
🗳️ Poll
📡 Across The Wire
🔗 Anthropic GTM Claudification JD - the $320k-$405k posting
🔗 What everyone is missing about Claudeforce - The Signal Club
🔗 Vanta Sr. AI GTM Engineer - Linkedin
🔗 How Anthropic uses Claude for GTM Engineering - Linkedin
🧪 What I'm Testing
- Writing approval gates before scoping any agent workflow
- CRM skill vs chat loop for lead routing
- JD language audit - what "GTM Engineer" actually means across 20 postings
Written by Manuel Bourel, Founder @ Altus Revenue.