How to Become a GTM Engineer: A New Career Path for Developers
GTM (Go-To-Market) engineers are an emerging role combining coding, data analysis, and business acumen to directly impact revenue, offering developers a way to increase job security during corporate reorganizations. The episode discusses why this role is growing, how it differs from traditional development, and practical strategies for developers to transition into GTM engineering without restarting their careers.
Summary
The hosts explain that traditional engineering roles face vulnerability during corporate layoffs because they are often viewed as cost centers rather than revenue generators. In contrast, GTM engineers and similar revenue-adjacent roles (sales engineers, rev ops engineers, growth engineers) directly contribute to business metrics like pipeline growth, conversion rates, and customer retention. These engineers combine data from multiple sources—CRM systems, customer analytics, sales dashboards—to create automation and workflows that improve sales processes and increase revenue. For example, a GTM engineer might build a system that analyzes customer data to generate qualified leads for salespeople, directly demonstrating revenue impact.
The hosts emphasize that corporate decision-makers prioritize roles that demonstrably increase profits or metrics tied to company objectives. During economic downturns, roles two or more steps removed from revenue (like developer experience teams or internal IT) are more vulnerable to outsourcing or elimination. The episode notes that GTM engineering positions grew from 16 job listings in December 2024 to 402 in May 2026, indicating significant industry adoption.
For developers transitioning to GTM engineering, the hosts provide several strategies: (1) actively engage with sales teams by requesting to join sales calls to understand customer needs and product usage; (2) document and communicate revenue impacts from technical work, ensuring leadership knows the connection between your contributions and business results; (3) build portfolio projects around revenue problems like lead generation or customer acquisition; (4) even without a formal GTM role existing at your company, volunteer to work on revenue-impacting initiatives during downtime; (5) update resumes to highlight business outcomes, not just technical achievements. The hosts stress that this doesn't require expensive outside-work preparation—it leverages skills and opportunities available during regular work hours.
The episode also discusses the complexity and newness of GTM roles: job responsibilities vary significantly between companies, making cookie-cutter definitions difficult. AI tools are increasingly involved, accelerating development of workflows and automating lead qualification. The hosts acknowledge that these roles still carry risks—sales teams might claim credit for improvements, requiring clear communication about your contributions. However, the direct visibility into revenue impact and the satisfaction of seeing metrics improve make these roles appealing for problem-solving-oriented engineers.
About this episode
What does a GTM Engineer do, and why is the role growing? Matt and Mike explore how developers can use code, data, automation, APIs, and AI to drive measurable business outcomes - and how to transition into GTM Engineering without starting over.
Key Insights
- During corporate reorganizations, roles that directly correlate to revenue generation are significantly harder to cut than support roles, even if those support roles are functionally important to the organization.
- GTM engineers combine coding with data analysis from multiple sources (CRM, analytics, sales dashboards) to identify patterns and build systems that measurably increase sales, rather than building products for end users.
- Job postings for GTM engineers and adjacent roles grew from 16 listings in December 2024 to 402 in May 2026, indicating that companies are increasingly investing in revenue-engineering positions.
- The GTM engineer role remains loosely defined across companies—different organizations expect different responsibilities, and the role is still evolving as consulting firms pitch GTM departments to clients.
- Developers often fail to communicate their business impact to leadership, allowing sales or other teams to claim credit for revenue improvements that resulted from technical infrastructure or automation built by engineers.
- Developers can transition into GTM engineering without formal role creation by proactively identifying problems the sales team faces and volunteering to solve them during available work time, rather than waiting for a job posting.
- Problem-solving engineers who have felt bored by repetitive coding tasks may find GTM work satisfying because it requires puzzle-solving across multiple domains (sales processes, data patterns, customer needs) rather than isolated technical challenges.
- The traditional developer job search process requires unpaid side projects, portfolio building, and extensive interview preparation, whereas GTM work can be developed and demonstrated during paid work hours by talking to colleagues and solving internal business problems.
Topics
Transcript
Developer job titles are changing. One role I'm seeing more and more of is a GTM engineer, a job that combines code, automation, data, and AI with a very direct goal, help the company make more money. That direct connection to revenue really, really does matter these days. No role is layoff proof, but during a reorganization, it is much easier to defend work that can point to more pipeline, better conversion, stronger retention, or lower acquisition costs. So today we're breaking down what a GTM engineer actually does, why the role is growing, and how an existing developer can transition into it without restarting their career all from scratch. So Mike, you actually are the one that wrote this…
Full transcript available for MurmurCast members
Sign Up to AccessMore from HTML All The Things - Web Development, AI, and Developer Careers
How to Prepare for a Tech Layoff
This episode discusses how to prepare for tech layoffs by identifying warning signs, building an emergency fund, maintaining updated resumes and portfolios, and cultivating professional networks. The hosts emphasize that layoffs are increasingly common across the tech industry regardless of company profitability, and that proactive preparation is essential even when employment seems secure.
Don't Just Vibe Code, Learn While You Code
Matt and Mike discuss how junior developers can learn foundational coding skills while using AI to code, arguing that understanding core concepts remains valuable despite AI automation. They identify three learner camps (vibe coders, aspiring junior devs, and job-focused developers) and debate whether manual coding knowledge is necessary for future success in an AI-driven development landscape.
Does AGI Actually Matter to You?
The hosts discuss whether GPT-6 Astra represents AGI, concluding that AGI is a moving target with different meanings for different users. They argue that rather than a universal definition, AGI should be understood through practical application—whether an AI can perform tasks equivalent to a human professional in specific domains. The conversation emphasizes that consumer-level adoption depends more on practical capability and accessibility than on achieving theoretical AGI status.
AI Agent Skills Explained: What They Are and Which Ones to Use
Agent skills are reusable text instructions packaged in markdown files that teach AI agents how to perform specific tasks or follow processes, differing from prompts and GPTs by using progressive disclosure to avoid context bloat. The hosts discuss how skills like Grill with Docs, Wayfinder, and Code Review help structure AI workflows, emphasizing the importance of avoiding skill bloat while building reproducible processes across teams.
AI Lets Me Game More - and Work Better
Two hosts discuss how to productively spend time while AI agents run tasks, arguing that taking breaks to play retro games or relax actually improves work quality and employee satisfaction rather than cramming more work into available time. They advocate for a balanced approach that values employee wellbeing alongside productivity metrics.