Technical Product Manager

Descripción del puesto

This role starts on the content platform, and the platform surface it serves is growing. The foundations of the company, identity and access, developer platform, data and the infrastructure everything runs on, are being invested in over the coming year. We are looking for someone whose curiosity does not stop at the edge of their own team, because the interesting problems here sit exactly where those layers meet.  There is genuine ambiguity in this space right now, and a decision or two you would inherit that we have not finished making. We would rather tell you that than have you discover it in month two. The upside is that very little here is set, so the person who takes this shapes the layer everything else in the product is built on for the next several years.  Requirements Own the content services every surface depends on. The services and APIs that serve content to the learner surface, the admin surface and everything we build next, plus the delivery path including CDN and video, and file and asset storage.  Own the structural contract. How content is stored, versioned and served so it can be reused and assembled differently for different customers. This is a schema and interface problem before it is a tooling problem, and your measure is whether the contract other teams build against is clear, stable and safe to change.  Own multi tenant separation. Making sure one customer’s content and branding stay theirs. The tenancy model needs a decision and an owner, and that will be one of your first real pieces of work.  Own access, entitlements and data residency. Who can reach what, where data lives, and what we are able to commit to contractually.  Own performance and cost per tenant. If this layer is slow, everything is slow. If it is expensive, it is expensive everywhere.  Carry the platform half of a migration already in flight. We are moving off an incumbent content tool while the current system keeps earning. Sequencing that