Job Opportunities API

About Packt  Packt's mission is to help the world put software to work in new ways, through the delivery of effective learning and information services to IT professionals. We are a technical publisher and learning provider with over 400 staff based across the globe, primarily in India and the UK. Our products have global relevance, and our multimedia portfolio includes over 7,000 books, e-books, audiobooks, and video courses. For more details, visit www.packtpub.com.   Role Overview  This is a central function role — not a vertical execution role. The Central Growth & GTM Lead owns how events go to market across all of Packt's verticals. Where Growth Leads own GTM within their vertical, this role owns the operating system that sits above and across them: the frameworks, the floor standards, the content engine, and the community layer that compound over time.  The core problem this role solves: Packt's event distribution is over-indexed on email and borrowed speaker reach, with no durable owned audience that persists between events. This role builds and runs the infrastructure to change that — a central content layer, a cross-vertical community system, and the attribution scaffolding to make it all measurable.  This is a 0→1 build role. The system does not exist yet. The right candidate will design it, own it, and be held accountable for the outcomes.  What You'll Do  GTM Operating System  Own how events go to market end-to-end. This is not campaign execution — it's building and running the system that vertical teams execute within.  Define and enforce GTM floor standards across all verticals: positioning, sequencing, channel mix  Ensure consistency in how events are launched; eliminate one-off approaches  Work with vertical GLs to shape demand before events go live  Identify what should scale vs. what should be killed based on performance signals  Content Layer (Central Handles)  Build and run the central content engine that supports all events and compounds audience over time.  Operate central handles (LinkedIn, X, Discord, Circle etc.) as distribution surfaces, not just publishing feeds  Turn event themes into ongoing content series — not one-time promotion  Create repeatable content formats that build audience between events  Build AI-enabled workflows: clip extraction → thread generation → scheduling at 3x traditional output  Ensure content feeds pipeline, not just impressions  Community Layer (Central System)  Build the community structure that sits across events and verticals — making audiences persistent, not ephemeral.  Design and operate a two-tier model: open discovery layer (LinkedIn, Discord) + gated continuation layer (post-event cohorts, newsletters)  Drive engagement before, during, and after events  Ensure community is a source of qualified demand, not just a retention layer  Work with GLs to plug vertical events into the central system  Attribution & Measurement  Make the GTM system measurable in a way that informs decisions, not just reports on the past.  Build UTM discipline and traffic attribution across all content and community surfaces  Track qualified traffic delivery as the primary C&C success metric — not aggregate Eventbrite conversion  Enable comparison across events and verticals (what worked vs. what didn't)  Build dashboards for weekly GTM review; surface directional signal, not vanity metrics  Cross-functional GTM Partnership  This role operates as a strategic peer to Product and vertical PDs — not a downstream execution function.  Work directly with Head of Product to shape the GTM system, not just execute it  Push back wh