GTM Product Manager

Role:GTM Product Manager

Location:South Africa

Working Hours:Full time, 40hrs/week in SA/EMEA business hours

Target Start Date:ASAP (Urgent Hiring)

About the Company

One of the world's largest IT and professional training providers, serving enterprise customers and individual learners across a dozen countries through authorised courses from the major technology vendors and our own instructor-led programs.

About the Role

We currently run a dozen separate country websites on a legacy enterprise CMS. Content barely differs between them, maintenance eats engineering time, and almost nothing about the customer journey is measured. We're consolidating all of it onto one global platform — a single site, headless CMS, localised by language and currency rather than by separate builds, with a rebuilt course catalog, checkout, lead capture, and a CRM and attribution layer that ties marketing spend to closed revenue.

You will own that program day to day, and beyond it. The design and engineering work is delivered by external partners, alongside a dedicated internal lead engineer who owns the technical build. Internal leadership sets direction and makes the big calls. You are the person in the middle who turns direction into scope, scope into sequenced delivery, and delivery into measured commercial outcomes. Once the site ships, the same ownership extends into how leads and signals from the site feed sales, and how AI-assisted routing and recommendations get built safely. If the site ships on time but leads don't route and revenue can't be attributed, the job wasn't done.

This is a senior individual contributor role with real ownership. You will not have a team of PMs under you. You will have direct access to the decision makers and the authority to hold vendors to dates.

Core Responsibilities
* Customer journey and information architecture:Map how a prospect moves from anonymous traffic to qualified lead to enrolled learner, including the fork between buyers training a team (routed to sales) and individuals enrolling themselves (routed straight to checkout). Define the structured content model and IA that a dozen markets share.
Customer journey and information architecture:Map how a prospect moves from anonymous traffic to qualified lead to enrolled learner, including the fork between buyers training a team (routed to sales) and individuals enrolling themselves (routed straight to checkout). Define the structured content model and IA that a dozen markets share.
* CMS and marketing site:Deliver the headless CMS build with the engineering partner. Define the editorial workflow so regional marketing teams publish locally without breaking the global template, and so marketing can ship pages without engineers.
CMS and marketing site:Deliver the headless CMS build with the engineering partner. Define the editorial workflow so regional marketing teams publish locally without breaking the global template, and so marketing can ship pages without engineers.
* Course catalog and product pages:Course data lives in an internal operational system. You own the product pages built on top of it, including real-time scheduling and availability, pricing display, filtering by language and region, and personalized recommendations for authenticated users.
Course catalog and product pages:Course data lives in an internal operational system. You own the product pages built on top of it, including real-time scheduling and availability, pricing display, filtering by language and region, and personalized recommendations for authenticated users.
* Commerce and checkout:Redesign the open enrollment checkout for conversion, with regional tax and currency handled correctly.
Commerce and checkout:Redesign the open enrollment checkout for conversion, with regional tax and currency handled correctly.
* CRM and lead capture:Scope and implement the CRM layer for the new site. Define the lead object, capture rules, scoring, and routing to account executives. This is a core part of the role, not a handoff to another team.
CRM and lead capture:Scope and implement the CRM layer for the new site. Define the lead object, capture rules, scoring, and routing to account executives. This is a core part of the role, not a handoff to another team.
* Analytics and attribution:Design the analytics schema from scratch. First and last touch stored on the user record and carried through the CRM so closed revenue attributes back to channel and campaign. Our current analytics are not trustworthy and you will be rebuilding them, not inheriting them.
Analytics and attribution:Design the analytics schema from scratch. First and last touch stored on the user record and carried through the CRM so closed revenue attributes back to channel and campaign. Our current analytics are not trustworthy and you will be rebuilding them, not inheriting them.
* SEO and migration:Consolidating a dozen sites into one is a redirect, canonical, and crawl mapping problem before it i