Principal Product Manager - Console
Principal Product Manager owning Lambda's customer-facing cloud console as one unified surface — setting navigation, identity/permissions, and interaction-pattern standards across GPU instances, clusters, bare metal, storage, networking, and billing. Day to day: writing standards, reviewing service teams' work, and partnering with design and front-end engineering. Requires 4 days/week in the Belle
- Compensation
- $338K–$450K / yr
- Location
- Bellevue Office
- Work setup
- Hybrid
- Seniority
- Principal
- Employment
- Not specified
- Experience
- 10+ years
- Category
- Product
- Posted
Skills
Must have
- 10+ years of product management experience, including owning a customer-facing console, dashboard, or developer surface for a cloud, infrastructure, or developer platform
- Shipped interaction patterns, a design system, or a surface standard that teams you did not manage adopted and kept using
- Taken separately built product surfaces and made them behave like one product
- Understands cloud infrastructure well enough to reason about identity, permissions, quotas, regions, capacity, telemetry, and billing
- Understands access control models for organizations, teams, projects, roles, and API keys
- Able to define iterative plans that move an organization from current state to desired outcome
- Has made one product serve both a first-time user and a daily operator
- Has used research and instrumentation to settle disagreements about user experience
- Can turn ambiguous customer, technical, and commercial inputs into product definition multiple teams execute against
- Communicates plainly, writes well, says no clearly, and makes decisions easier
- Presence in Bellevue or San Francisco office 4 days per week
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
- 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
- Experience with accessibility standards and making an infrastructure product usable under them
- Experience with a console that had to serve both a human and an automated caller
Full description
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.
*Note: This position requires presence in our Bellevue or San Francisco office location 4 days per week; Lambda’s designated work from home day is currently Tuesday.
About the Role
The console is where every service Lambda sells meets the human user at the customer. It is the place where disparate products can come together to create a unified experience that solves a customer problem. Conversely, it is also the place where a cloud most easily becomes hard to use, because each service is built by a different team at a different time, and every one of them arrives with its own idea of what a resource is called, where it lives, who is allowed to touch it, and what a customer should do next. The customer does not experience a portfolio of services. They experience one product, and they judge us on whether it holds together.
This role owns that product. You own 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. Every service team ships into that surface, and the standards are yours to set. 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.
Three very different people have to succeed here. A machine learning researcher wants a graphics processing unit (GPU) in minutes and should never have to learn cloud vocabulary to get one. An infrastructure engineer runs large clusters, lives in the application programming interface (API) and the command line, and needs the console to agree exactly with both. A platform engineer is building their own service on top of Lambda for their own users, and needs the console to make clear what their teams can see, spend, and change. The hard part of the role is that these three pull in different directions, and the surface cannot be quietly bent toward whichever one showed up in the last customer meeting.
Great product managers at Lambda are defined by three things: insight, influence, and execution. Insight means you look at the data, determine what it means for customers and business, and then figure out what to do about it. But, a great idea doesn't mean anything in a vacuum. That is where influence comes in. Influence means you take that idea and get others to want to buy into it; you win over engineers, designers, executives, and partners without relying on authority. But a great idea that everyone is excited about doesn't matter unless it is delivered to customers. Execution means you work with the right people to get the idea launched, then measure and iterate. We hire product managers who learn new domains fast and reason rigorously from evidence. Deep experience owning a customer-facing console for a cloud or developer platform is highly desired.