Principal Product Manager - Console

Lambda•Bellevue, WA

21h•$338,000 - $500,000•Hybrid

About The Position

Lambda is hiring a Principal Product Manager to own its customer-facing console as one coherent product across its cloud services, including On-Demand GPU Instances, reserved capacity, 1-Click Clusters, bare metal, storage, networking, Managed Kubernetes, billing, and support. The role sets and maintains shared standards for navigation, identity and permissions, interaction patterns, resource naming, and customer workflows, and ensures service teams build consistently within the console. The position also keeps the console aligned with Lambda’s API, command line, and infrastructure-as-code interfaces. The product serves machine learning researchers seeking a quick path to a GPU, infrastructure engineers operating large clusters, and platform engineers building services for their own users. The role balances their needs while establishing standards and partnerships with design and front-end engineering. It includes improving onboarding and first-workload activation while keeping advanced operator workflows such as bulk actions, filtering, deep links, quotas, spend visibility, and access control first class. The Principal Product Manager works closely with customers, support, engineering, design, service product managers, executives, and partners. They define product requirements and launch criteria, make and document tradeoff decisions, measure outcomes, and iterate based on evidence. The role is based in the Bellevue or San Francisco office four days per week; Tuesday is currently Lambda’s designated work-from-home day.

Requirements

10+ years of product management experience, including ownership of a customer-facing console, dashboard, or developer surface for a cloud, infrastructure, or developer platform.
Experience shipping interaction patterns, a design system, or surface standards adopted and maintained by teams the candidate did not manage.
Experience consolidating separately built product surfaces so they behave like one product, and the ability to explain what was consolidated and what was not.
Sufficient understanding of cloud infrastructure to reason with engineers about identity, permissions, quotas, regions, capacity, telemetry, billing, and customer-facing exposure.
Understanding of access-control models for organizations, teams, projects, roles, and API keys, and how to present them for platform teams.
Ability to define iterative plans that move an organization from its current state toward a desired outcome.
Experience serving first-time users and daily operators within one product.
Experience using research and instrumentation to resolve user-experience disagreements, and comfort presenting evidence amid strong opinions.
Ability to turn ambiguous customer, technical, and commercial inputs into product definitions that multiple teams can execute.
Clear communication and strong writing; ability to say no clearly and make decisions easier for people with differing context.

Nice To Haves

Experience with machine learning or data platform surfaces, such as 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.
Experience with accessibility standards and making an infrastructure product usable under them.
Experience with a console serving both human users and automated callers, and an understanding of the tradeoffs involved.

Responsibilities

Own the console’s product definition, scope, prioritization, and sequencing across Lambda services.
Define and document shared console patterns and standards for navigation, identity, permissions, resource naming, states, errors, and empty screens; establish and run reviews before console work ships.
Keep the console’s resource descriptions, names, and rules consistent with the API, command line, and infrastructure-as-code interfaces.
Own and instrument the customer journey from signup to first workload, and maintain first-class workflows for operators and platform teams, including bulk actions, filtering, deep links, quotas, spend visibility, and access control.
Investigate customer needs and blockers using customer conversations, support tickets, escalations, and session data.
Produce requirements, user stories, and acceptance criteria that engineering and design teams can execute against.
Partner with service product managers to integrate their launches into the console as one product and agree on integration points early.
Set and ensure launch criteria covering documentation, in-product guidance, support readiness, and accessibility.
Define success measures before launch and evaluate outcomes using measures such as completion rates, time to first result, and support load; iterate based on findings.
Make and document decisions on contested tradeoffs, communicate them clearly, and continue owning them after they are made.
Build the design and front-end engineering partnership needed to establish and sustain console standards.