Clay’s Kareem Amin: The GTM engineer is the new growth stack

At TechCrunch Disrupt 2026, Clay co-founder and CEO Kareem Amin took the AI Stage to argue that the next critical hire for scaling startups isn’t another growth marketer or sales ops lead, but a “GTM engineer.” The pitch is simple: if revenue teams spend half their time stitching together tools, data, and workflows, the GTM engineer is the person who makes that stitching invisible.

Clay’s own pitch deck already reflects this shift. The startup, which raised $100M in seed funding to sell infrastructure for agentic GTM plays to Fortune 500 customers, describes its product as “build[ing] systems to grow revenue.” That framing—systems, not campaigns—is deliberate. Amin’s Disrupt talk doubled down on it, positioning the GTM engineer as the architect of those systems, someone who can write code, query data, and orchestrate workflows without needing a separate engineering team to translate every request.

The timing is telling. When we covered Anthropic, Gamma, and Clay’s AI Stage panel on deployment challenges four days ago, the conversation kept circling back to the same bottleneck: AI demos look great, but moving them into daily use inside large companies requires a layer of custom integration that most go-to-market teams aren’t staffed to handle. Amin’s GTM engineer is the answer to that bottleneck—a role that sits between product and revenue, with enough technical fluency to own the last mile of deployment.

This isn’t just Clay’s internal org chart; it’s a bet on how the entire GTM stack will evolve. The company’s directory listing describes its product as infrastructure to “get any data, run agentic workflows, and launch GTM plays.” That’s a mouthful, but it maps cleanly to the GTM engineer’s job description: pull data from anywhere, automate the workflows that turn it into pipeline, and launch plays without manual handoffs. If Amin is right, the GTM engineer isn’t a niche role—it’s the new center of gravity for revenue teams.

The question is whether companies will actually hire for it. Most startups still think of GTM as a function of sales and marketing, not engineering. But Amin’s argument is that the distinction is already obsolete: if your growth depends on automating workflows at scale, you’re already doing engineering, whether you call it that or not. The GTM engineer is just the person brave enough to admit it.

Clay’s own seed round suggests there may be appetite for this vision. The company’s $100M raise—unusually large for a seed-stage startup—targets enterprise customers, a market that doesn’t just want tools but wants to offload the entire integration layer. That’s a heavy lift, and it explains why Amin is evangelizing the role now: if Clay is selling infrastructure, its customers need someone who can actually operate it.

Look for two things next. First, whether other startups in the revenue automation space begin positioning similar roles as part of their value proposition. Second, whether job postings for hybrid technical-revenue titles start appearing more frequently. If they do, it could indicate the market is moving toward Amin’s vision.

Sources: techcrunch.com