Snr Product Manager (GTM, Web)
- Hiring from
- South Africa
- Work type
- Remote
- Posted
- Sep 29, 2026
Is this job info correct?
Job Description
Senior Product Manager, GTM & Web Platform
Senior Product Manager, GTM & Web Platform — Remote, South Africa preferred. Full-time. Reports to CTO.
About Us
We are 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. We're in the middle of a reset: new ownership, a leaner operating model, and a strategy that repositions the company around helping enterprises through the human side of AI adoption. The website is the front door for all of it, and it's being rebuilt from the ground up.
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.
What you'll own
• 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.
• 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.
• 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.
• SEO and migration. Consolidating a dozen sites into one is a redirect, canonical, and crawl mapping problem before it is anything else. You own the migration plan, the redirect map, structured data and schema markup, content pruning to the pages that earn traffic and revenue, and the organic performance through and after cutover.
• Internationalization. Language, currency, VAT, regional content variation, and the governance model for who controls what across markets.
• Partner management. Run scoping, sequencing, acceptance criteria, and delivery dates with the design and engineering partners. Document decisions. Escalate early.
• GTM operating model, once the site ships. Own the handoff of leads and signals from the site into CRM scoring and routing. Help define the shared operating model with Sales and Marketing — ICP, buying groups, lead definitions, and decision rights.
• AI-driven orchestration, done safely. Own next-best-action, propensity/risk scoring, and agent-assisted routing or content — always with named human checkpoints, clear evaluation, and an off switch. This is a governed product surface, not an unreviewed chatbot.
What we're looking for
• An engineering background. You've written production code or run production systems. You can sit in an architecture discussion with the engineering partner, ask the right question, and make a call without escalating every technical decision.
• You've built a marketing and sales stack yourself. CRM, marketing automation, lead routing, the integrations between them. You owned the wiring, not just the requirements document.
• You've built revenue attribution. A model that traced marketing activity to closed deals through a CRM, and changed how money was spent as a result. Be ready to walk through the specific one.
• Deep content marketing and SEO experience. You've designed web schemas and structured data, owned organic traffic as a number you were accountable for, and run at least one large site migration without losing rankings.
• You've delivered a replatform through an external agency. Feature work inside an in-house product team is good experience but it's not this. The failure modes on this program are vendor failure modes: unclear scope, slipping dates, work that technically meets the spec but misses the point. You've seen them and you know how to prevent them.
• Multi-country or multi-language sites. You understand what localization actually requires beyond translation.
• Strong written communication. This program runs across several time zones and most of the work happens asynchronously in writing. You write clearly, decide in writing, and don't need a meeting to move something forward.
• Speed over ceremony. We're targeting a build-to-cutover window measured in weeks, not a year-long enterprise migration. You're comfortable with that pace and with using AI tooling to move faster.
• Comfortable owning AI-assisted capability as a governed product surface. You know the difference between shipping a feature and shipping something that needs human checkpoints, evaluation, and a kill switch.
Nice to have
Ecommerce and checkout optimization. Headless CMS experience (Payload, Sanity, Storyblok, Contentful, or similar). Experience replacing a legacy enterprise CMS. Familiarity with usage-priced or open-source CRM alternatives to the enterprise incumbents (e.g. Twenty). Background in education, training, or certification businesses. Exposure to AI agent orchestration or evaluation tooling.
How we work
Written and asynchronous by default. Results over activities. Clear owners, clear measures, and a bias toward shipping. We use AI tools heavily across the company and expect you to as well. You'll report into a small leadership group that moves fast and gives direct feedback.
How to apply
Send a short note covering three things. The attribution model you built and what decision it changed. A site migration you ran and what you lost. An agency or employee that missed a date and what you did about it. Skip the cover letter.