• Lead a team of Product Managers working on complex, high-impact AI solutions for enterprise customers • Work closely with customers to find the right problem to solve (the use case with the clearest ROI) and define the success metrics before building • Operate in high ambiguity, shaping opportunities where requirements are not clearly defined • Drive the delivery of new solutions from early stages to production, making key product and trade-off decisions across speed, stability, and scope • Own a portfolio of solutions across one or more enterprise customers, setting priorities across multiple parallel engagements • Support your PMs in the day-to-day of running their solutions across different customers: help them prioritize, make trade-offs, and unblock them so product implementations and solutions push forward • Balance speed of execution with long-term quality, reuse, and product thinking • Identify patterns across solutions and push for reuse and productization, working closely with the Platform team • Mentor and develop your PMs, growing their product judgment and helping them operate effectively in a fast-paced, ambiguous environment

• Owning the architecture: auth and identity flows, multi-tenancy, how data moves and where it's allowed to live, performance, and what happens in production • Running what you build. You'll be on-call for your own work from early on, before there's a dedicated platform to lean on, which means owning the infrastructure, CI, deployment, and observability behind it • Working on top of external platforms you can't change, and being straight about which risks are yours to manage and which aren't • Partnering closely with the internal teams whose services you depend on: asking clearly, agreeing on interfaces, and finding ways to keep moving instead of waiting around to be unblocked

• You'll own an integration end to end: the design, the code, and the production system that keeps running after launch. • Owning the architecture: auth and identity flows, multi-tenancy, how data moves and where it's allowed to live, performance, and what happens in production • Running what you build. You'll be on-call for your own work from early on, before there's a dedicated platform to lean on, which means owning the infrastructure, CI, deployment, and observability behind it • Working on top of external platforms you can't change, and being straight about which risks are yours to manage and which aren't • Partnering closely with the internal teams whose services you depend on: asking clearly, agreeing on interfaces, and finding ways to keep moving instead of waiting around to be unblocked • We'd also expect you to have opinions about where this should go, and to write them down. A lot of what shapes the team's direction starts as a doc.

• You'll own an integration end to end: the design, the code, and the production system that keeps running after launch. You're setting the technical defaults a growing team will inherit, so the early decisions matter. • Day to day, that looks like: • Owning the architecture: auth and identity flows, multi-tenancy, how data moves and where it's allowed to live, performance, and what happens in production • Running what you build. You'll be on-call for your own work from early on, before there's a dedicated platform to lean on, which means owning the infrastructure, CI, deployment, and observability behind it • Working on top of external platforms you can't change, and being straight about which risks are yours to manage and which aren't • Partnering closely with the internal teams whose services you depend on: asking clearly, agreeing on interfaces, and finding ways to keep moving instead of waiting around to be unblocked • We'd also expect you to have opinions about where this should go, and to write them down. A lot of what shapes the team's direction starts as a doc.