Clay CEO Kareem Amin to Present the Case for the GTM Engineer at TechCrunch Disrupt 2026
Clay CEO Kareem Amin will outline how AI is creating GTM engineering roles that turn prospect research, data, and outreach into automated growth systems.
Clay co-founder and CEO Kareem Amin is scheduled to speak at TechCrunch Disrupt 2026 about the emergence of the “GTM engineer,” a role built around using AI, data, and automation to construct revenue workflows. The session reflects a broader shift in how startups are approaching sales and marketing: instead of adding people to carry out fragmented manual tasks, companies are increasingly looking for operators who can build systems that perform those tasks repeatedly.
Amin’s appearance is scheduled for the AI Stage under the title “The GTM Engineer: How AI Created Tech’s Next Big Job Category.” TechCrunch says the session will examine how AI is changing the traditional go-to-market stack and what that means for the teams responsible for finding, qualifying, and reaching customers.
The event is set for October 13-15 at Moscone West in San Francisco. The available reporting describes an upcoming conference session, not a completed product announcement or a new research finding from Amin.
From manual GTM work to engineered workflows
Traditional go-to-market operations often require separate people and tools for account research, data cleaning, lead qualification, message preparation, and campaign execution. Information then moves between customer relationship management systems, data providers, spreadsheets, sales engagement software, and marketing platforms.
The GTM engineer concept treats that chain as a system to be designed. In this model, a practitioner may connect data sources, define targeting rules, build enrichment workflows, and use AI to produce personalized outreach. The role is not simply an automated version of a salesperson or marketer. It sits between revenue operations, software development, and growth strategy.
According to TechCrunch, Clay coined the term in 2023. The company’s own guide describes GTM engineers as people who build automated revenue workflows rather than completing each go-to-market task manually. That distinction matters for small companies in particular: a well-designed workflow could allow a compact sales or growth team to handle more research and experimentation without creating a separate internal engineering project for every process.
The underlying work is not new. Companies have long automated lead routing, email campaigns, account scoring, and data enrichment. What has changed is the range of tasks that AI can support inside those workflows, including unstructured research and the creation of more individualized messaging.
What Clay is building around the category
Clay began as a spreadsheet-style product for connecting information and automating work without requiring users to write code. TechCrunch reports that salespeople, growth teams, and agencies later became a significant user group, leading the company deeper into go-to-market infrastructure.
Today, Clay provides tools for accessing data, running agentic workflows, and launching campaigns. Its OpenAI-powered agent, Claygent, is positioned by the company as a way to automate research and outreach for sales, marketing, and recruiting teams.
That product history helps explain why Amin is advocating for the GTM engineer role. Clay is not an outside commentator describing a labor-market trend; it sells software that supports the workflows associated with the role. Its interpretation is therefore relevant to the category, but it is also commercially interested in making GTM engineering a recognized discipline and expanding the market for its platform.
Clay has also announced a $1 million scholarship fund to train GTM engineers, according to TechCrunch. The initiative suggests the company sees skills and staffing—not only software—as constraints on adoption. If the role spreads, companies will need people who understand revenue goals as well as data quality, workflow design, model behavior, and system maintenance.
Evidence behind the adoption claims
The strongest labor-market signal cited in the report comes from Clay itself. The company says roughly 100 GTM engineering job listings appear each month, with examples at Cursor, Lovable, and Webflow. That figure is vendor-reported and is not independently verified in the available evidence. It may indicate growing interest, but it does not establish that 100 fully standardized jobs are being created monthly or that employers use the title consistently.
Clay’s business growth is also reported by TechCrunch rather than independently documented here. The company reportedly tripled annual recurring revenue to $100 million in one year, announced an employee tender offer at a $5 billion valuation, and later announced a $115 million Series D at a $7.1 billion valuation in September. Those figures describe company announcements and reported financing events; they are not evidence that every organization using AI for go-to-market has adopted a GTM engineer structure.
The available sources provide no independent benchmark comparing GTM engineers with conventional sales development, marketing operations, or revenue operations teams. They also do not establish how much revenue, headcount, or time companies save through these workflows. Those questions will matter to buyers deciding whether to purchase software, hire a specialist, or redesign an existing process.
Why the role matters to builders and enterprises
For founders, the practical question is not whether the title becomes popular. It is whether a dedicated operator can create a repeatable growth system that is more productive and more controllable than adding another layer of disconnected tools.
A GTM engineer could be valuable when a company has enough customer and market data to support targeting, but lacks the technical capacity to connect systems and maintain automations. The role may be especially relevant to startups that need to test many segments or messaging strategies without building a large sales operations function.
The model also introduces operational risks. Automated prospect research can produce inaccurate or outdated information. Personalization systems can generate messages that are irrelevant, overly invasive, or noncompliant with company policies. Data enrichment may create privacy and governance issues, while agentic workflows can make errors at a scale that is difficult to review manually.
For enterprise buyers, deployment questions are likely to be as important as the productivity case. Teams will need controls over data access, approval steps, audit trails, outbound volume, and model-generated content. A workflow that saves time but damages deliverability or customer trust is not an improvement. The role therefore requires more than prompt-writing ability; it demands ownership of reliability, measurement, and safeguards across the revenue stack.
What to watch next
The first signal will be what Amin presents at Disrupt: specific workflow examples, measurable outcomes, and the boundaries between GTM engineering and established revenue operations roles. Concrete implementation details will be more useful than a new title alone.
The market should also watch whether companies continue to use the term in job descriptions and whether responsibilities converge across employers. Evidence of hiring, retention, and reporting lines will show whether GTM engineer becomes a durable function or remains a label for existing sales operations work.
Other signals include independent performance studies, customer disclosures, and evidence that AI-supported outreach can improve qualified pipeline without increasing spam, inaccurate claims, or compliance exposure. For Clay, the scholarship program, hiring demand, product adoption, and the company’s ability to support larger enterprise deployments will indicate whether it is helping define a category or primarily promoting its own platform.
Creati.ai perspective
Clay’s Amin is bringing attention to a real organizational change: AI is moving some go-to-market work from manual execution toward workflow design. But the evidence currently supports an emerging category, not a settled profession or proven replacement for conventional sales and marketing teams.
The important test will be operational. Builders and enterprise leaders should evaluate GTM engineering through data quality, conversion impact, review requirements, and total system cost—not the novelty of the title. If those measures hold up across independent companies, the role could become a practical bridge between AI tools and revenue operations. If not, it may remain useful mainly as Clay’s framing of the market it serves.
