Principal Product Manager - Console

Lambda, The Superintelligence Cloud, is a leader in AI cloud infrastructure serving tens of thousands of customers. Our customers range from AI researchers to enterprises and hyperscalers. Lambda's mission is to make compute as ubiquitous as electricity and give everyone the power of superintelligence. One person, one GPU.

If you'd like to build the world's best AI cloud, join us. This role owns the console as a single surface, with one navigation model, one identity and permissions story, one set of interaction patterns, and one vocabulary, across On-Demand GPU Instances, reserved capacity, 1-Click Clusters, bare metal, storage, networking, Managed Kubernetes, billing, and support.

Your job is to make the whole thing feel like it was designed on purpose, which means writing the standards down, reviewing the work against them, and being the person who says no when a service wants to solve a problem in a way that only makes sense from inside that team.

Responsibilities:

• Own the Whole Surface: Hold the product definition for the console as one product, decide what belongs in it and what does not, rank and sequence the work, and be honest about what Lambda is not doing this year and why.
• Set the Patterns and Hold Them: Define the navigation, identity, permissions presentation, resource naming, states, errors, and empty screens that every service uses, write them down clearly enough that a team can build to them without asking you, then establish and run the review that console work passes before it ships.
• Keep the Console Honest With the API: Make sure the console, the API, the command line, and infrastructure as code describe the same resources with the same names and the same rules, and treat a console-only capability as a problem to be fixed rather than a feature.
• Fix the First Hour, Then Serve the Expert: Own what happens between signing up and running a first workload, instrument it well enough to know exactly where people stop, and keep the paths that operators and platform teams live in, like bulk actions, filtering, deep links, quotas, spend visibility, and access control, first class rather than an afterthought behind a wizard.
• Find the Real Problem: Get close to customers, support tickets, escalations, and session data, and work out what is actually blocking people rather than what they asked for.
• Write the Definition: Produce requirements, user stories, and acceptance criteria precise enough that engineering and design build from them without a translation layer.
• Work as a Group: Partner with the product managers who own each service so their launches land inside your surface as one product, and agree the seams early rather than at launch review.
• Land the Launch: Set launch criteria that include documentation, in-product guidance, support readiness, and accessibility, and get them met before the surface goes live rather than after.
• Measure and Iterate: Define success before you ship, then go find out whether it happened, using completion rates, time to first result, and support load rather than opinion.
• Make the Call Stick: Take a position on contested tradeoffs, write it down well enough that people can disagree with it precisely, and keep owning the decision after it is made.

Requirements:

• Have 10+ years of product management experience, including owning a customer-facing console, dashboard, or developer surface for a cloud, infrastructure, or developer platform.
• Have shipped interaction patterns, a design system, or a surface standard that teams you did not manage adopted and kept using after you stopped pushing, and can describe how you actually got them to.
• Have taken a set of separately built product surfaces and made them behave like one product, and can say what you consolidated, what you left alone, and why.
• Understand cloud infrastructure well enough to reason with engineers about identity, permissions, quotas, regions, capacity, telemetry, and billing, and about what should and should not be exposed to a customer.
• Understand access control models for organizations, teams, projects, roles, and API keys well enough to design how they are presented, because this is where a console either works for a platform team or does not.
• Able to define iterative plans that move an organization from the current state towards the desired outcome.
• Have made one product serve both a first-time user and a daily operator without turning it into two products.
• Have used research and instrumentation to settle a disagreement about a user experience, and are comfortable being the person who brings evidence to a room full of strong opinions.
• Can turn ambiguous customer, technical, and commercial inputs into product definition that multiple teams execute against.
• Communicate plainly, write well, say no clearly, and make decisions easier for people who do not all share the same context.

Nice to Have:

• Experience with machine learning or data platform surfaces, like notebooks, training jobs, model endpoints, or experiment tracking.
• Experience with the self-serve funnel from signup to first paid usage, including conversion and activation work.
• Experience partnering closely with a front-end platform team on a component library, design tokens, or a shared application shell.
• Experience owning documentation or in-product guidance as part of the product rather than as a handoff.
• Experience with accessibility standards and with making an infrastructure product usable under them.
• Experience with a console that had to serve both a human and an automated caller, and opinions about what that costs.