About the role
Company Overview: k-ID is building the age aware internet, where kids and teens can access technology in ways that are safer, more private, and appropriate for their age, while platforms and games can meet complex age related
requirements across global markets. Our platform helps developers understand user age, configure age appropriate experiences, manage parental consent, and stay aligned with fast changing global laws and regulations. We are building compliance infrastructure for the internet: developer first, privacy preserving, and designed to make complex regulatory obligations easier to operationalize at scale. Job Summary: CDK is k-ID's compliance engine. It turns regulation into developer primitives – age assurance, parental consent, permissions, jurisdictional rule resolution, entitlements – that any platform can configure in Compliance Studio, power with our regulatory intelligence engine (neimo), and enforce at runtime through clean APIs and drop-in widgets. Today CDK is pointed at the fastest-moving regulatory category on earth: child safety and online safety law. But the engine is regulation-agnostic by design. The same machinery that resolves what a 13-year-old can do in Brazil resolves an age-restricted purchase, an AI-companion safeguard, or a rule that doesn't exist yet. That's the premise – and it's why platforms across gaming, social, AI, and commerce build on CDK, and why compliance is becoming infrastructure the way payments became an API. We're hiring a Product Lead – a principal-level role – to own CDK end-to-end and run it like its own business. There is no playbook for this product; you will write it. You treat CDK as a platform, not a feature: you see the pattern across enterprise requests and build the abstraction, not the one-off, and you make global regulatory complexity disappear for the developer integrating you in an afternoon. This is not a backlog-grooming role. You'll be simultaneously in the weeds on product behavior intricacies and driving overall business strategy and direction. Key
Responsibilities: You run CDK like its own business. You're measured on outcomes, not output – adoption, conversion, expansion, and reliability, not specs written or features shipped – and you're the single point of accountability for those numbers across Legal, Engineering, Design, GTM, and Customer Success. Grow CDK as a product line. Own its arc from configuration tool to the compliance platform others build on, and the adoption, revenue, and expansion that prove it. What you build, defer, and kill is judged against that outcome, not a feature backlog. Land new verticals. Turn the regulation-agnostic engine into shipped revenue in new categories – AI, regulated commerce, whatever's next – by building primitives that generalize instead of one-offs per customer. Define the primitive . Identify the core abstractions that make CDK genuinely differentiated (permission strings, jurisdictional rule engines, consent orchestration) and partner with engineering to build them. Run the pod, not just the roadmap. You own the "what" and the "why," then you own the build – the cadence, the unblocking, the in-the-weeds calls with engineering, not a deck you hand off. Pure strategists who delegate execution won't last here; neither will pure executors who don't want to own the bet. Keep it unbreakable at scale. CDK enforces compliance for tens of millions of users; staying correct as the law shifts underneath is an outcome you own with engineering, not a problem you hand to them. Minimum