Human-First: The GTM Hiring Show
Here's how to tell if you need a GTM Engineer and what to fix first. Lauren Hughes is VP of Revenue Effectiveness at JustWorks, where she rebuilt the entire function from the ground up by merging rev ops and enablement, introducing GTM engineering roles, and hiring AI enablement specialists. Roughly 75% of her team is either new or in a completely different seat than before. From this episode of Human-First, you'll walk away knowing exactly how to diagnose whether you need a GTM engineer or a Salesforce admin, how to assess builder mindset in interviews when no one has "10 years of GTM engineering experience" on their resume, and what foundation you need in place before any of it matters. This one's for founders, revenue leaders, and rev ops professionals trying to figure out what their team should actually look like right now and what it needs to become. We cover GTM hiring for technical roles, AI fluency as a hiring bar, case studies in the age of AI, and why your operating maturity determines your next hire. Key Takeaways >> If your pain is "Salesforce hygiene is bad and routing rules need fixing," you need an admin. GTM engineers are for inventing capabilities that don't exist yet, not maintaining what does. >> The strongest GTM engineer candidates deconstructed the problem from a data perspective and came with a complete system redesign, while average ones just talked about process improvements. >> Case studies are more critical than ever precisely because of AI with the real test is whether candidates can defend and explain what they built when questioned live. >> Before hiring a GTM engineer, get your data foundation right with clean infrastructure, clear ownership, and system discipline. AI and builders can't fix what's fundamentally broken underneath. Chapter Markers 00:00 - What a GTM engineer actually does 01:54 - Why JustWorks rebuilt revenue effectiveness from scratch 05:17 - How the rebuild played out: roles added, removed, and renamed 08:51 - GTM engineers vs. Salesforce admins: where the confusion comes from 14:58 - How to interview for builder mindset with no job title precedent 18:05 - Case studies in the age of AI: what's changed and what still works 21:02 - The AI fluency bar: what Lauren asks every candidate 24:08 - AI enablement roles and just-in-time personalized learning 29:52 - The flattening org: why middle management layers are thinning 33:44 - Career paths in rev ops: skills-based, not tenure-based 35:34 - What early-stage founders should do before hiring a GTM engineer 38:35 - Rev ops as the entry point for AI across the org 41:07 - Where Lauren learns: podcasts, communities, and vendor dinners 45:32 - The one thing to get right before writing a job description Useful Links & Resources * Lauren Hughes on LinkedIn: https://www.linkedin.com/in/laurenehughes10023/ [https://www.linkedin.com/in/laurenehughes10023/] * Captivate Talent: https://www.captivatetalent.com [https://www.captivatetalent.com/] Connect With the Show * Captivate Talent on LinkedIn: https://www.linkedin.com/company/captivate-talent/ [https://www.linkedin.com/company/captivate-talent/] * Danielle Parker on LinkedIn: https://www.linkedin.com/in/daniellemessler/ [https://www.linkedin.com/in/daniellemessler/] What's your take? Is the GTM engineer title getting ahead of what most teams actually need? Drop your thoughts in the comments, or tell us what your rev ops team looks like right now. We'd love to hear how you're navigating this shift. Visit captivatetalent.com to learn how we help B2B tech companies hire exceptional GTM talent. If this episode was useful, like, subscribe, and share it with someone building out their rev ops function.
8 episodios
Comentarios
0Sé la primera persona en comentar
¡Regístrate ahora y únete a la comunidad de Human-First: The GTM Hiring Show!