Technical Product Manager - Behavioural Analytics

<p> </p> <p><strong><span data-contrast="none"><span data-ccp-parastyle="heading 2">Here's</span><span data-ccp-parastyle="heading 2"> a summary of

the role</span></span></strong><span data-ccp-props="{"335559738":280,"335559739":140}"> </span></p> <p><span data-contrast="auto">Data is only powerful when everyone agrees what it means.  This is your chance to build a world class product behavioural data system and process from the ground up.</span><span data-ccp-props="{"335559739":140}"> </span></p> <p><span data-contrast="auto">We're rebuilding the internal product our teams use to measure product success and end-user value across all our 24+ products in four business units. </span> <br> <br><span data-contrast="auto">You'll design the single source of truth: the metric definitions, the telemetry standards, the data contract engineering instruments against, the change governance processes and tooling, and the models that turn behaviour into portfolio insight.</span><span data-ccp-props="{"335559739":140}"> </span></p> <p><span data-contrast="auto">You'll educate and support the teams using this internal behavioural data product to set expectations and and plot a rational roadmap for the maturing of this product, helping our user to use the data honestly and wisely. </span> <br> <br><span data-contrast="auto">Usage tells you what happened, not why, or whether it mattered. We want someone who sets quantitative behaviour against qualitative evidence and treats the disagreement as the interesting part.</span><span data-ccp-props="{"335559739":140}"> </span></p> <p><span data-contrast="auto">AWS/Snowflake is our spine; capture and BI are open decisions you'll help make. Your models feed the business reviews our executive team, CTO and investors use to run the portfolio, and engineering is committed to instrument against your contract.</span><span data-ccp-props="{"335559739":140}"> </span></p> <p><strong><span data-contrast="none"><span data-ccp-parastyle="heading 2">Here's</span><span data-ccp-parastyle="heading 2"> what your first twelve months should look like</span></span></strong><span data-ccp-props="{"335559738":280,"335559739":140}"> </span></p> <ul> <li data-leveltext="•" data-font="" data-listid="2" data-list-defn-props="{"335552541":1,"335559685":431,"335559991":259,"469769242":[8226],"469777803":"left","469777804":"•","469777815":"hybridMultilevel"}" data-aria-posinset="1" data-aria-level="1"><strong><span data-contrast="auto">First 90 days. </span></strong><span data-contrast="auto">Learn the estate, meet the engineers who instrument it, and agree the measurement model for one product end to end — with a defensible adoption number and the qualitative read on what it means.</span><span data-ccp-props="{"335559739":120}"> </span></li> </ul> <ul> <li data-leveltext="•" data-font="" data-listid="2" data-list-defn-props="{"335552541":1,"335559685":431,"335559991":259,"469769242":[8226],"469777803":"left","469777804":"•","469777815":"hybridMultilevel"}" data-aria-posinset="2" data-aria-level="1"><strong><span data-contrast="auto">Three to six months. </span></strong><span data-contrast="auto">Data contract published, instrumentation spec landed with engineering, first business unit building against it. Definitions, naming and versioned change control governed.</span><span data-ccp-props="{"335559739":120}"> </span></li> </ul> <ul> <li data-leveltext="•" data-font="" data-listid="2" data-list-defn-props="{"335552541":1,"335559685":431,"335559991":259,"469769242":[8226],"469777803":"left","469777804":"•","469777815":"hybridMultilevel"}" data-aria-posinset="3" data-aria-level="1"><strong><span data-contrast="auto">Six to twelve months. </span></strong><span data-contrast="auto">Rolling out across the remaining business units through the BU-aligned analysts, portfolio reporting running on your numbers.</span><span data-ccp-props="{"335559739":120}"> </span></li> </ul> <p><strong><span data-contrast="none"><span data-ccp-parastyle="heading 2">Here's</span><span data-ccp-parastyle="heading 2"> a breakdown of what </span><span data-ccp-parastyle="heading 2">you'll</span><span data-ccp-parastyle="heading 2"> do (not all of it, just the important stuff)</span></span></strong><span data-ccp-props="{"335559738":280,"335559739":140}"> </span></p> <ul> <li data-leveltext="•" data-font="" data-listid="2" data-list-defn-props="{"335552541":1,"335559685":431,"335559991":259,"469769242":[8226],"469777803":"left","469777804":"•","469777815":"hybridMultilevel"}" data-aria-posinset="4" data-aria-level="1"><strong><span data-contrast="auto">Design the behavioural telemetry</span></strong><span data-contrast="auto"> — event and entity-state schemas at a grain that supports both portfolio roll-up and feature-level decisions — and write the instrumentation specification engineering builds against. Then assure what comes back: coverage, freshness, reconciliation.</span><span data-ccp-props="{"335559739":120}"> </span></li> </ul> <ul> <li data-leveltext="•" data-font="" data-listid="2" data-list-defn-props="{"335552541":1,"335559685":431,"335559991":259,"469769242":[8226],"469777803":"left","469777804":"•","469777815":"hybridMultilevel"}" data-aria-posinset="5" data-aria-level="1"><strong><span data-contrast="auto">Own the measurement standard</span></strong><span data-contrast="auto"> — canonical definitions, naming, field ownership, versioned change control — across every business unit.</span><span data-ccp-props="{"335559739":120}"> </span></li> </ul> <ul> <li data-leveltext="•" data-font="" data-listid="2" data-list-defn-props="{"335552541":1,"335559685":431,"335559991":259,"469769242":[8226],"469777803":"left","469777804":"•","469777815":"hybridMultilevel"}" data-aria-posinset="6" data-aria-level="1"><strong><span data-contrast="auto">Build the models</span></strong><span data-contrast="auto"> — SQL, BI and roll-up logic turning behaviour into insight on adoption, time-to-value and value realisation.</span><span data-ccp-props="{"335559739":120}"> </span></li> </ul> <ul> <li data-leveltext="•" data-font="" data-listid="2" data-list-defn-props="{"335552541":1,"335559685":431,"335559991":259,"469769242":[8226],"469777803":"left","469777804":"•","469777815":"hybridMultilevel"}" data-aria-posinset="7" data-aria-level="1"><strong><span data-contrast="auto">Triangulate.</span></strong><span data-contrast="auto"> Pair behavioural data with qualitative evidence from design research and VoC, segment by user role and account, and say so publicly when the two disagree.</span><span data-ccp-props="{"335559739":120}"> </span></li> </ul> <ul> <li data-leveltext="•" data-font="" data-listid="2" data-list-defn-props="{"335552541":1,"335559685":431,"335559991":259,"469769242":[8226],"469777803":"left","469777804":"•","469777815":"hybridMultilevel"}" data-aria-posinset="8" data-aria-level="1"><strong><span data-contrast="auto">Partner on the product, customer and user taxonomies</span></strong><span data-contrast="auto">, set the technical standard for the BU-aligned analysts, and help shape the analytics stack as we revamp it.</span><span data-ccp-props="{"335559739":120}"> </span></li> </ul> <p><strong><span data-contrast="none"><span data-ccp-parastyle="heading 2">These are the essentials </span><span data-ccp-parastyle="heading 2">you'll</span><span data-ccp-parastyle="heading 2"> need to get an interview</span></span></strong><span data-ccp-props="{"335559738":280,"335559739":140}"> </span></p> <ul> <li data-leveltext="•" data-font="" data-listid="2" data-list-defn-props="{"335552541":1,"335559685":431,"335559991":259,"469769242":[8226],"469777803":"left","469777804":"•","469777815":"hybridMultilevel"}" data-aria-posinset="9" data-aria-level="1"><strong><span data-contrast="auto">Direct experience building mixed-method behavioural insight systems</span></strong><span data-contrast="auto"> — you've built the layer where quantitative behaviour and qualitative evidence come together, not just consumed the output. You've worked alongside design or UX researchers, and can name a time the qualitative read changed what you measured.</span><span data-ccp-props="{"335559739":120}"> </span></li> </ul> <ul> <li data-leveltext="•" data-font="" data-listid="2" data-list-defn-props="{"335552541":1,"335559685":431,"335559991":259,"469769242":[8226],"469777803":"left","469777804":"•","469777815":"hybridMultilevel"}" data-aria-posinset="10" data-aria-level="1"><strong><span data-contrast="auto">Hands-on event and telemetry schema design</span></strong><span data-contrast="auto"> — Pendo, Amplitude, Segment, Mixpanel or equivalent. You designed the schema and wrote the spec, not used dashboards someone else built.</span><span data-ccp-props="{"335559739":120}"> </span></li> </ul> <ul> <li data-leveltext="•" data-font="" data-listid="2" data-list-defn-props="{"335552541":1,"335559685":431,"335559991":259,"469769242":[8226],"469777803":"left","469777804":"•","469777815":"hybridMultilevel"}" data-aria-posinset="11" data-aria-level="1"><strong><span data-contrast="auto">Designing and governing product data models and taxonomies</span></strong><span data-contrast="auto"> — canonical metrics and naming taken into a multi-product estate and made to stick, including acquired products.</span><span data-ccp-props="{"335559739":120}"> </span></li> </ul> <ul> <li data-leveltext="•" data-font="" data-listid="2" data-list-defn-props="{"335552541":1,"335559685":431,"335559991":259,"469769242":[8226],"469777803":"left","469777804":"•","469777815":"hybridMultilevel"}" data-aria-posinset="12" data-aria-level="1"><strong><span data-contrast="auto">Data governance practice</span></strong><span data-contrast="auto">: schema and field ownership, versioned change control, standards adoption across teams you don't own.</span><span data-ccp-props="{"335559739":120}"> </span></li> </ul> <ul> <li data-leveltext="•" data-font="" data-listid="2" data-list-defn-props="{"335552541":1,"335559685":431,"335559991":259,"469769242":[8226],"469777803":"left","469777804":"•","469777815":"hybridMultilevel"}" data-aria-posinset="13" data-aria-level="1"><strong><span data-contrast="auto">Fluency in SQL and the BI / warehouse layer</span></strong><span data-contrast="auto"> — you build and validate roll-up logic yourself.</span><span data-ccp-props="{"335559739":120}"> </span></li> </ul> <ul> <li data-leveltext="•" data-font="" data-listid="2" data-list-defn-props="{"335552541":1,"335559685":431,"335559991":259,"469769242":[8226],"469777803":"left","469777804":"•","469777815":"hybridMultilevel"}" data-aria-posinset="14" data-aria-level="1"><strong><span data-contrast="auto">Behavioural segmentation judgement</span></strong><span data-contrast="auto"> — you know why a B2B account is a mix of people with different motivations, and why averaging them produces confident, wrong conclusions.</span><span data-ccp-props="{"335559739":120}"> </span></li> </ul> <ul> <li data-leveltext="•" data-font="" data-listid="2" data-list-defn-props="{"335552541":1,"335559685":431,"335559991":259,"469769242":[8226],"469777803":"left","469777804":"•","469777815":"hybridMultilevel"}" data-aria-posinset="15" data-aria-level="1"><strong><span data-contrast="auto">The credibility to influence without authority</span></strong><span data-contrast="auto"> — you can hold a standard with teams you don't line-manage.</span><span data-ccp-props="{"335559739":120}"> </span></li> </ul> <p><strong><span data-contrast="none"><span data-ccp-parastyle="heading 2">It would be great if you had these too, but </span><span data-ccp-parastyle="heading 2">we'll</span><span data-ccp-parastyle="heading 2"> support you if you </span><span data-ccp-parastyle="heading 2">don't</span></span></strong><span data-ccp-props="{"335559738":280,"335559739":140}"> </span></p> <ul> <li data-leveltext="•" data-font="" data-listid="2" data-list-defn-props="{"335552541":1,"335559685":431,"335559991":259,"469769242":[8226],"469777803":"left","469777804":"•","469777815":"hybridMultilevel"}" data-aria-posinset="16" data-aria-level="1"><strong><span data-contrast="auto">Hands-on behavioural analytics and synthesis practice</span></strong><span data-contrast="auto"> — running the analysis yourself, not only building what enables it.</span><span data-ccp-props="{"335559739":120}"> </span></li> </ul> <ul> <li data-leveltext="•" data-font="" data-listid="2" data-list-defn-props="{"335552541":1,"335559685":431,"335559991":259,"469769242":[8226],"469777803":"left","469777804":"•","469777815":"hybridMultilevel"}" data-aria-posinset="17" data-aria-level="1"><strong><span data-contrast="auto">Privacy and lawful basis as live design constraints</span></strong><span data-contrast="auto"> — pseudonymisation, residency, re-identification controls.</span><span data-ccp-props="{"335559739":120}"> </span></li> </ul> <ul> <li data-leveltext="•" data-font="" data-listid="2" data-list-defn-props="{"335552541":1,"335559685":431,"335559991":259,"469769242":[8226],"469777803":"left","469777804":"•","469777815":"hybridMultilevel"}" data-aria-posinset="18" data-aria-level="1"><strong><span data-contrast="auto">GRC, governance or regulated-software domains.</span></strong><span data-ccp-props="{"335559739":120}"> </span></li> </ul> <ul> <li data-leveltext="•" data-font="" data-listid="2" data-list-defn-props="{"335552541":1,"335559685":431,"335559991":259,"469769242":[8226],"469777803":"left","469777804":"•","469777815":"hybridMultilevel"}" data-aria-posinset="19" data-aria-level="1"><strong><span data-contrast="auto">Salesforce, Jira Product Discovery, Pendo</span></strong><span data-contrast="auto">, and consolidating fragmented tooling into one system of record.</span><span data-ccp-props="{"335559739":120}"> </span></li> </ul> <ul> <li data-leveltext="•" data-font="" data-listid="2" data-list-defn-props="{"335552541":1,"335559685":431,"335559991":259,"469769242":[8226],"469777803":"left","469777804":"•","469777815":"hybridMultilevel"}" data-aria-posinset="20" data-aria-level="1"><strong><span data-contrast="auto">Product value / ROI measurement</span></strong><span data-contrast="auto"> — connecting behaviour to commercial outcomes.</span><span data-ccp-props="{"335559739":120}"> </span></li> </ul> <p><strong><span data-contrast="none"><span data-ccp-parastyle="heading 2">How </span><span data-ccp-parastyle="heading 2">we'll</span><span data-ccp-parastyle="heading 2"> assess this</span></span></strong><span data-ccp-props="{"335559738":280,"335559739":140}"> </span></p> <p><span data-contrast="auto">We ask everyone to write SQL and design an event schema, and to talk us through a time qualitative evidence contradicted their numbers. No take-home longer than an hour.</span><span data-ccp-props="{"335559739":140}"> </span></p> <p><strong><span data-contrast="none"><span data-ccp-parastyle="heading 2">Here's</span><span data-ccp-parastyle="heading 2"> where this role goes next</span></span></strong><span data-ccp-props="{"335559738":280,"335559739":140}"> </span></p> <p><span data-contrast="auto">We're building this function, not maintaining it. You set the standard the BU-aligned analysts land across the business — technical leadership from day one, without a management line.</span><span data-ccp-props="{"335559739":140}"> </span></p> <p><span data-contrast="auto">As