Job Description & Details
This role puts you right at the intersection of product-led growth and core platform infrastructure, where you'll own the systems that drive self-serve user acquisition and engagement. If you like untangling messy data schemas, building experimentation engines, and enabling GTM teams with automated tooling, this is a solid gig with a massive global footprint.
What You'll Actually Be Doing
You will spend your days bridging the gap between raw data pipelines and actionable GTM workflows. Expect to drive CDP implementations, fix event taxonomy issues, and build out robust A/B testing infrastructure that other product teams can rely on. You'll act as the glue between engineering and business units, taking ownership of the growth tech stack and ensuring our data governance holds up under enterprise scale.
The Core Tech Stack
You need deep fluency in CDPs like Segment, RudderStack, or mParticle, alongside experimentation tools such as Amplitude, Mixpanel, or Optimizely. Since you'll be working closely with engineers on data pipelines, webhook integrations, and database architectures, you must be comfortable talking shop about REST APIs and event schemas without needing your hand held.
Interview Expectations
Expect the hiring panel to hit you with a tricky scenario on how you handle broken event taxonomies and conflicting data governance rules across multiple disparate product teams. They want to see if you can establish shared standards through pure influence and cross-functional leadership when you don't actually manage the engineering resources directly. Be ready to whiteboard a complete CDP migration strategy from legacy systems to a modern stack like Segment or Adobe Experience Platform, highlighting how you mitigate downstream reporting risks.
Application Advice
Make sure your resume leans hard into metrics-driven product management, specifically highlighting any experience you have with B2B SaaS growth, self-serve funnels, and PLM strategies. Drop exact keywords from the listing—like 'CDP implementation', 'event taxonomy', and 'experimentation infrastructure'—directly into your bullet points so you clear the ATS easily, but back them up with concrete examples of cross-functional alignment.